| Message ID | 1483532187-28494-5-git-send-email-peda@axentia.se |
|---|---|
| State | Awaiting Upstream |
| Headers | show |
On 04/01/17 12:16, Peter Rosin wrote: > Signed-off-by: Peter Rosin <peda@axentia.se> Looks neat and tidy to me. Acked-by: Jonathan Cameron <jic23@kernel.org> > --- > .../devicetree/bindings/mux/mux-controller.txt | 26 ++++++++++++++++++++++ > 1 file changed, 26 insertions(+) > > diff --git a/Documentation/devicetree/bindings/mux/mux-controller.txt b/Documentation/devicetree/bindings/mux/mux-controller.txt > index 42b2177e5ae1..4e89df8b2392 100644 > --- a/Documentation/devicetree/bindings/mux/mux-controller.txt > +++ b/Documentation/devicetree/bindings/mux/mux-controller.txt > @@ -125,3 +125,29 @@ An example mux controller might look like this: > reg = <0x50>; > #mux-control-cells = <1>; > }; > + > + > +Combinded controller and consumer of a GPIO mux > +----------------------------------------------- > + > +For the common case of a single consumer of a GPIO controlled mux, there is > +a simplified binding which will instantiate an implicit mux controller. Just > +specify a mux-gpios property with the same interpretation as in mux-gpio.txt. > +Note that other properties described in mux-gpio.txt are not available in > +this simplified form and that the mux controller is unnamed. If you need > +more than one mux controller, a shared mux controller or if you need a > +specific idle-state, use the more flexible binding with the mux controller > +in its own node. > + > +Example: > + > + adc-mux { > + compatible = "io-channel-mux"; > + io-channels = <&adc 0>; > + io-channel-names = "parent"; > + > + mux-gpios = <&pioA 0 GPIO_ACTIVE_HIGH>, > + <&pioA 1 GPIO_ACTIVE_HIGH>; > + > + channels = "sync-1", "in", "out", "sync-2"; > + }; > -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/Documentation/devicetree/bindings/mux/mux-controller.txt b/Documentation/devicetree/bindings/mux/mux-controller.txt index 42b2177e5ae1..4e89df8b2392 100644 --- a/Documentation/devicetree/bindings/mux/mux-controller.txt +++ b/Documentation/devicetree/bindings/mux/mux-controller.txt @@ -125,3 +125,29 @@ An example mux controller might look like this: reg = <0x50>; #mux-control-cells = <1>; }; + + +Combinded controller and consumer of a GPIO mux +----------------------------------------------- + +For the common case of a single consumer of a GPIO controlled mux, there is +a simplified binding which will instantiate an implicit mux controller. Just +specify a mux-gpios property with the same interpretation as in mux-gpio.txt. +Note that other properties described in mux-gpio.txt are not available in +this simplified form and that the mux controller is unnamed. If you need +more than one mux controller, a shared mux controller or if you need a +specific idle-state, use the more flexible binding with the mux controller +in its own node. + +Example: + + adc-mux { + compatible = "io-channel-mux"; + io-channels = <&adc 0>; + io-channel-names = "parent"; + + mux-gpios = <&pioA 0 GPIO_ACTIVE_HIGH>, + <&pioA 1 GPIO_ACTIVE_HIGH>; + + channels = "sync-1", "in", "out", "sync-2"; + };
Signed-off-by: Peter Rosin <peda@axentia.se> --- .../devicetree/bindings/mux/mux-controller.txt | 26 ++++++++++++++++++++++ 1 file changed, 26 insertions(+)