A few of the regulators on BD71828 / BD71879 do have common voltage setting for some or all of the power states (RUN, IDLE, SUSPEND, LSPR). The driver supports setting voltages for low-power states via device-tree. At driver probe time the device-tree is read for these voltage settings, and found voltage is written to the hardware.
When this is done for a regulator where same voltage is used in all/many states, this will set voltage also for states which were not intended to be changed. It means the board device-tree writer needs to be aware of this behaviour or nasty problems may emerge when voltage configuration is accidentally changed. Problems may vary from changing the currently used voltage to some low-power state voltage (which may cause problems to the hardware) - to setting wrong voltage(s) for low-power states which can lead to increased power consumption or even hardware damage.
FIX:
The fix is to only allow power-state specific voltage setting for those regulators where it is supported per state. We can still allow using the special voltage values like '0' to mark regulator to be disabled at specific low-power state. This is supported for all states at least on all BUCK regulators.
PROBLEM:
A few of the regulators on BD71828 / BD71879 do have common voltage setting for some or all of the power states (RUN, IDLE, SUSPEND, LSPR). The driver supports setting voltages for low-power states via device-tree. At driver probe time the device-tree is read for these voltage settings, and found voltage is written to the hardware.
When this is done for a regulator where same voltage is used in all/many states, this will set voltage also for states which were not intended to be changed. It means the board device-tree writer needs to be aware of this behaviour or nasty problems may emerge when voltage configuration is accidentally changed. Problems may vary from changing the currently used voltage to some low-power state voltage (which may cause problems to the hardware) - to setting wrong voltage(s) for low-power states which can lead to increased power consumption or even hardware damage.
FIX:
The fix is to only allow power-state specific voltage setting for those regulators where it is supported per state. We can still allow using the special voltage values like '0' to mark regulator to be disabled at specific low-power state. This is supported for all states at least on all BUCK regulators.