diff options
| author |   Rob Herring <robh@kernel.org> | 2018-07-09 09:41:49 -0600 |
|---|---|---|
| committer |   Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2018-07-10 17:22:35 +0200 |
| commit | 7930eb919feb59b8c799cb3085d0e9f7b5ae34d1 (patch) | |
| tree | 5c517feb712a9ee41826d04c888abfdcb10909b0 /Documentation/devicetree/bindings/pinctrl | |
| parent | driver core: allow stopping deferred probe after init (diff) | |
| download | linux-dev-7930eb919feb59b8c799cb3085d0e9f7b5ae34d1.tar.xz linux-dev-7930eb919feb59b8c799cb3085d0e9f7b5ae34d1.zip | |
dt-bindings: pinctrl: add a 'pinctrl-use-default' property
Pin setup may be optional in some cases such as the reset default works
or the pin setup is done by the bootloader. In these cases, it is optional
for the OS to support managing the pin controller and pin setup. In order
to support this scenario, add a property 'pinctrl-use-default' to indicate
that the pin configuration is optional.
Signed-off-by: Rob Herring <robh@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Documentation/devicetree/bindings/pinctrl')
| -rw-r--r-- | Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt b/Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt index ad9bbbba36e9..cef2b5855d60 100644 --- a/Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt +++ b/Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt @@ -103,6 +103,12 @@ Optional properties: #pinctrl-cells: Number of pin control cells in addition to the index within the pin controller device instance +pinctrl-use-default: Boolean. Indicates that the OS can use the boot default + pin configuration. This allows using an OS that does not have a + driver for the pin controller. This property can be set either + globally for the pin controller or in child nodes for individual + pin group control. + Pin controller devices should contain the pin configuration nodes that client devices reference. |