diff options
| author | Chen-Yu Tsai <[email protected]> | 2020-07-20 21:28:09 +0800 |
|---|---|---|
| committer | Mark Brown <[email protected]> | 2020-07-20 16:31:54 +0100 |
| commit | 3acff11cef1dece31cd29956f19181895996a7c5 (patch) | |
| tree | 74c27d021b304ccab63c87dd1110bdf506cc0ebc /tools/testing/selftests/bpf/prog_tests/autoload.c | |
| parent | a98bcaa92d3d7a7753e23b3363d90ffdb82e8edb (diff) | |
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 <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Mark Brown <[email protected]>
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/autoload.c')
0 files changed, 0 insertions, 0 deletions