lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 8 Jan 2017 10:25:04 +0000 From: Jonathan Cameron <jic23@...nel.org> To: Peter Rosin <peda@...ntia.se>, linux-kernel@...r.kernel.org Cc: Wolfram Sang <wsa@...-dreams.de>, Rob Herring <robh+dt@...nel.org>, Mark Rutland <mark.rutland@....com>, Hartmut Knaack <knaack.h@....de>, Lars-Peter Clausen <lars@...afoo.de>, Peter Meerwald-Stadler <pmeerw@...erw.net>, Jonathan Corbet <corbet@....net>, Arnd Bergmann <arnd@...db.de>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, linux-i2c@...r.kernel.org, devicetree@...r.kernel.org, linux-iio@...r.kernel.org, linux-doc@...r.kernel.org Subject: Re: [PATCH v7 04/12] dt-bindings: simplified bindings for single-user gpio mux On 04/01/17 12:16, Peter Rosin wrote: > Signed-off-by: Peter Rosin <peda@...ntia.se> Looks neat and tidy to me. Acked-by: Jonathan Cameron <jic23@...nel.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"; > + }; >
Powered by blists - more mailing lists