Some regulators don't have all states defined and in such cases regulator core should not assume anything. However in current implementation of of_get_regulation_constraints() DO_NOTHING_IN_SUSPEND enable value was set only for regulators which had suspend node defined, otherwise the default 0 value was used, what means DISABLE_IN_SUSPEND. This lead to broken system suspend/resume on boards, which had simple regulator constraints definition (without suspend state nodes). To avoid further mismatches between the default and uninitialized values of the suspend enabled/disabled states, change the values of the them, so default '0' means DO_NOTHING_IN_SUSPEND. Fixes: 72069f9957a1: regulator: leave one item to record whether regulator is enabled Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com> Signed-off-by: Mark Brown <broonie@kernel.org> Cc: stable@vger.kernel.org |
||
|---|---|---|
| .. | ||
| ab8500.h | ||
| act8865.h | ||
| arizona-ldo1.h | ||
| arizona-micsupp.h | ||
| consumer.h | ||
| da9211.h | ||
| db8500-prcmu.h | ||
| driver.h | ||
| fan53555.h | ||
| fixed.h | ||
| gpio-regulator.h | ||
| lp872x.h | ||
| lp3971.h | ||
| lp3972.h | ||
| machine.h | ||
| max1586.h | ||
| max8649.h | ||
| max8660.h | ||
| max8952.h | ||
| max8973-regulator.h | ||
| mt6311.h | ||
| mt6323-regulator.h | ||
| mt6380-regulator.h | ||
| mt6397-regulator.h | ||
| of_regulator.h | ||
| pfuze100.h | ||
| tps6507x.h | ||
| tps51632-regulator.h | ||
| tps62360.h | ||
| userspace-consumer.h | ||