regulator: Document "regulator-boot-on" binding more thoroughly

Browse source

The description of "regulator-boot-on" was a little unclear, at least
to me.  Did this property mean that we should turn the regulator on at
boot?  Or perhaps it was intended only to be used for regulators where
we couldn't read the state at bootup to indicate what state we should
assume?  The answer, it turns out, is both [1].

Let's document this.

[1] https://lore.kernel.org/r/20190923181431.GU2036@sirena.org.uk

Signed-off-by: Douglas Anderson <dianders@chromium.org>
Link: https://lore.kernel.org/r/20191001124531.v2.1.Ice34ad5970a375c3c03cb15c3859b3ee501561bf@changeid
Signed-off-by: Mark Brown <broonie@kernel.org>

...

This commit is contained in:

Douglas Anderson 2019-10-01 12:45:54 -07:00 • committed by Mark Brown

parent 95bddd8bbf

commit 87fd0db6d7

No known key found for this signature in database

GPG key ID: 24D68B725D5487D0

1 changed files with 6 additions and 1 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

7

Documentation/devicetree/bindings/regulator/regulator.yaml

View file