summaryrefslogtreecommitdiffstats
path: root/drivers/regulator/max77650-regulator.c
diff options
context:
space:
mode:
authorChen-Yu Tsai <wens@csie.org>2020-07-20 15:28:09 +0200
committerMark Brown <broonie@kernel.org>2020-07-20 17:31:54 +0200
commit3acff11cef1dece31cd29956f19181895996a7c5 (patch)
tree74c27d021b304ccab63c87dd1110bdf506cc0ebc /drivers/regulator/max77650-regulator.c
parentregulator: Correct kernel-doc inconsistency (diff)
downloadlinux-3acff11cef1dece31cd29956f19181895996a7c5.tar.xz
linux-3acff11cef1dece31cd29956f19181895996a7c5.zip
regulator: gpio: Honor regulator-boot-on property
When requesting the enable GPIO, the driver should do so with the correct output level matching some expected state. This is especially important if the regulator is a critical one, such as a supply for the boot CPU. This is currently done by checking for the enable-at-boot property, but this is not documented in the device tree binding, nor does it match the common regulator properties. Honor the common regulator-boot-on property by checking the boot_on constraint setting within the DT probe path. This is the same as what is done in the fixed regulator driver. Also add a comment stating that the enable-at-boot property should not be used. Fixes: 006694d099e8 ("regulator: gpio-regulator: Allow use of GPIO controlled regulators though DT") Signed-off-by: Chen-Yu Tsai <wens@csie.org> Link: https://lore.kernel.org/r/20200720132809.26908-1-wens@kernel.org Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'drivers/regulator/max77650-regulator.c')
0 files changed, 0 insertions, 0 deletions