Re: [RFC PATCH 4/7] dt-bindings: iio: iio-mux: document iio-mux bindings
From: Lars-Peter Clausen <lars@metafoo.de>
Date: 2016-11-17 11:40:26
Also in:
linux-i2c, linux-iio, lkml
On 11/17/2016 12:48 AM, Peter Rosin wrote:
quoted hunk ↗ jump to hunk
--- .../bindings/iio/multiplexer/iio-mux.txt | 59 ++++++++++++++++++++++ 1 file changed, 59 insertions(+) create mode 100644 Documentation/devicetree/bindings/iio/multiplexer/iio-mux.txtdiff --git a/Documentation/devicetree/bindings/iio/multiplexer/iio-mux.txt b/Documentation/devicetree/bindings/iio/multiplexer/iio-mux.txt new file mode 100644 index 000000000000..2f5c7fc35a42 --- /dev/null +++ b/Documentation/devicetree/bindings/iio/multiplexer/iio-mux.txt@@ -0,0 +1,59 @@ +IIO multiplexer bindings + +If a multiplexer is used to select when hardware signal is fed to +e.g. an ADC channel, these bindings describe that situation. + +Required properties: +- compatible : "iio-mux" +- io-channels : Channel node of the parent channel that has multiplexed + input. +- io-channel-names : Should be "parent". +- control-muxes : Node of the multiplexer that controls the input signal. +- control-mux-names : Should be "mux". +- #address-cells = <1>; +- #size-cells = <0>; + +Required properties for iio-mux child nodes: +- reg : The multiplexer number. + +Optional properties for iio-mux child nodes: +- iio-ext-info : Array of string pairs, the first item in each pair is the + iio ext_info attribute name, and the second item in each + pair is the iio ext_info value for that attribute. The + mux will write these ext_info values to the corresponding + ext_info attributes on every multiplexer switch.
This can't go into the devicetree in its current form as it exposes implementation details of the Linux kernel drivers.