Lines Matching refs:mux

4 $id: http://devicetree.org/schemas/mux/mux-controller.yaml#
13   A multiplexer (or mux) controller will have one, or several, consumer devices
14   that uses the mux controller. Thus, a mux controller can possibly control
16   multiplexer needed by each consumer, but a single mux controller can of course
19   A mux controller provides a number of states to its consumers, and the state
28   specifier using the '#mux-control-cells' or '#mux-state-cells' property.
29   The value of '#mux-state-cells' will always be one greater than the value
30   of '#mux-control-cells'.
32   Optionally, mux controller nodes can also specify the state the mux should
34   idle-state is not present, the mux controller is typically left as is when
35   it is idle. For multiplexer chips that expose several mux controllers, the
36   idle-state property is an array with one idle state for each mux controller.
38   The special value (-1) may be used to indicate that the mux should be left
40   mux controller chips with more than one mux controller, particularly when
41   there is a need to "step past" a mux controller and set some other idle
42   state for a mux controller with a higher index.
44   Some mux controllers have the ability to disconnect the input/output of the
50         #include <dt-bindings/mux/mux.h>
54   An example mux controller node look like this (the adg972a chip is a triple
57     mux: mux-controller@50 {
60       #mux-control-cells = <1>;
69           pattern: '^mux-controller'
71         - '#mux-control-cells'
73         - '#mux-state-cells'
77     pattern: '^mux-controller(@.*|-[0-9a-f]+)?$'
79   '#mux-control-cells':
82   '#mux-state-cells':
91       Mux controller nodes can specify the state the mux should have when it is
92       idle. If the idle-state is not present, the mux controller is typically
93       left as is when it is idle. For multiplexer chips that expose several mux
95       each mux controller.
97       The special value (-1) may be used to indicate that the mux should be left
99       mux controller chips with more than one mux controller, particularly when
100       there is a need to "step past" a mux controller and set some other idle
101       state for a mux controller with a higher index.
103       Some mux controllers have the ability to disconnect the input/output of the
116     /* One consumer of a 2-way mux controller (one GPIO-line) */
117     mux: mux-controller {
118         compatible = "gpio-mux";
119         #mux-control-cells = <0>;
121         mux-gpios = <&pioA 0 GPIO_ACTIVE_HIGH>;
124     adc-mux {
125         compatible = "io-channel-mux";
129         mux-controls = <&mux>;
130         mux-control-names = "adc";
142     mux2: mux-controller {
143         compatible = "gpio-mux";
144         #mux-control-cells = <0>;
146         mux-gpios = <&pioA 0 GPIO_ACTIVE_HIGH>,
150     adc-mux {
151         compatible = "io-channel-mux";
155         mux-controls = <&mux2>;
160     i2c-mux {
161         compatible = "i2c-mux";
164         mux-controls = <&mux2>;
193     mux1: mux-controller {
194         compatible = "gpio-mux";
195         #mux-state-cells = <1>;
196         mux-gpios = <&exp_som 2 GPIO_ACTIVE_HIGH>;
204         mux-states = <&mux1 1>;