diff options
| author |   Krzysztof Kozlowski <k.kozlowski@samsung.com> | 2014-04-07 14:15:23 +0200 |
|---|---|---|
| committer |   Mark Brown <broonie@linaro.org> | 2014-04-07 13:39:58 +0100 |
| commit | f4fbb3ce342bc1c13455209cb9ea63b9f678d159 (patch) | |
| tree | e119d6af01c011051a9224493479173d1f004b5e /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | Merge remote-tracking branches 'regulator/topic/tps65218', 'regulator/topic/tps6524x', 'regulator/topic/tps6586x', 'regulator/topic/tps65910', 'regulator/topic/tps80031', 'regulator/topic/wm831x', 'regulator/topic/wm8350' and 'regulator/topic/wm8994' into regulator-next (diff) | |
| download | linux-dev-f4fbb3ce342bc1c13455209cb9ea63b9f678d159.tar.xz linux-dev-f4fbb3ce342bc1c13455209cb9ea63b9f678d159.zip | |
regulator: s5m8767: Fix carried over ena_gpio assignment
During registration of regulators if external control for regulator was
set in DTS the ena_gpio and ena_gpio_flags fields of regulator_config
were set to proper values.
However the same regulator_config was used in next iterations of loop so
the ena_gpio fields carried over to next regulators.
The issue was not observed as ena_gpio is supported only for Buck9
regulator which is often the last regulator parsed from DTS.
Be sure to clear ena_gpio config fields before registering the
regulator.
Fixes: ee1e0994ab1bd (regulator: s5m8767: Use GPIO for controlling Buck9/eMMC)
Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Signed-off-by: Mark Brown <broonie@linaro.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions