Lines Matching full: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
24 Mux controller nodes
27 Mux controller nodes must specify the number of cells used for the
28 specifier using the '#mux-control-cells' property.
30 Optionally, mux controller nodes can also specify the state the mux should
32 idle-state is not present, the mux controller is typically left as is when
33 it is idle. For multiplexer chips that expose several mux controllers, the
34 idle-state property is an array with one idle state for each mux controller.
36 The special value (-1) may be used to indicate that the mux should be left
38 mux controller chips with more than one mux controller, particularly when
39 there is a need to "step past" a mux controller and set some other idle
40 state for a mux controller with a higher index.
42 Some mux controllers have the ability to disconnect the input/output of the
48 #include <dt-bindings/mux/mux.h>
52 An example mux controller node look like this (the adg972a chip is a triple
55 mux: mux-controller@50 {
58 #mux-control-cells = <1>;
67 pattern: '^mux-controller'
69 - '#mux-control-cells'
73 pattern: '^mux-controller(@.*|-[0-9a-f]+)?$'
75 '#mux-control-cells':
84 Mux controller nodes can specify the state the mux should have when it is
85 idle. If the idle-state is not present, the mux controller is typically
86 left as is when it is idle. For multiplexer chips that expose several mux
88 each mux controller.
90 The special value (-1) may be used to indicate that the mux should be left
92 mux controller chips with more than one mux controller, particularly when
93 there is a need to "step past" a mux controller and set some other idle
94 state for a mux controller with a higher index.
96 Some mux controllers have the ability to disconnect the input/output of the
109 /* One consumer of a 2-way mux controller (one GPIO-line) */
110 mux: mux-controller {
111 compatible = "gpio-mux";
112 #mux-control-cells = <0>;
114 mux-gpios = <&pioA 0 GPIO_ACTIVE_HIGH>;
117 adc-mux {
118 compatible = "io-channel-mux";
122 mux-controls = <&mux>;
123 mux-control-names = "adc";
135 mux2: mux-controller {
136 compatible = "gpio-mux";
137 #mux-control-cells = <0>;
139 mux-gpios = <&pioA 0 GPIO_ACTIVE_HIGH>,
143 adc-mux {
144 compatible = "io-channel-mux";
148 mux-controls = <&mux2>;
153 i2c-mux {
154 compatible = "i2c-mux";
157 mux-controls = <&mux2>;