gpio: mention in DT binding doc that <name>-gpio is deprecated
The gpiolib supports parsing DT properties of the form <name>-gpio but it
was only added for compatibility with older DT bindings that got it wrong
and should not be used in newer bindings.
The commit that added support for this was:
dd34c37aa3
("gpio: of: Allow -gpio suffix for property names")
but didn't update the documentation to explain this so it's been a source
of confusion. So let's make this clear in the GPIO DT binding doc.
Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
Signed-off-by: Rob Herring <robh@kernel.org>
This commit is contained in:
parent
c8aa33a711
commit
e7ae65ced7
|
@ -16,7 +16,9 @@ properties, each containing a 'gpio-list':
|
||||||
GPIO properties should be named "[<name>-]gpios", with <name> being the purpose
|
GPIO properties should be named "[<name>-]gpios", with <name> being the purpose
|
||||||
of this GPIO for the device. While a non-existent <name> is considered valid
|
of this GPIO for the device. While a non-existent <name> is considered valid
|
||||||
for compatibility reasons (resolving to the "gpios" property), it is not allowed
|
for compatibility reasons (resolving to the "gpios" property), it is not allowed
|
||||||
for new bindings.
|
for new bindings. Also, GPIO properties named "[<name>-]gpio" are valid and old
|
||||||
|
bindings use it, but are only supported for compatibility reasons and should not
|
||||||
|
be used for newer bindings since it has been deprecated.
|
||||||
|
|
||||||
GPIO properties can contain one or more GPIO phandles, but only in exceptional
|
GPIO properties can contain one or more GPIO phandles, but only in exceptional
|
||||||
cases should they contain more than one. If your device uses several GPIOs with
|
cases should they contain more than one. If your device uses several GPIOs with
|
||||||
|
|
Loading…
Reference in New Issue