Lines Matching full:controller

1 Common multiplexer controller bindings
4 A multiplexer (or mux) controller will have one, or several, consumer devices
5 that uses the mux controller. Thus, a mux controller can possibly control
7 multiplexer needed by each consumer, but a single mux controller can of course
10 A mux controller provides a number of states to its consumers, and the state
18 Mux controller consumers should specify a list of mux controllers that they
23 	mux-ctrl-phandle : phandle to mux controller node
25 			     given mux controller (controller specific)
27 Mux controller properties should be named "mux-controls". The exact meaning of
28 each mux controller property must be documented in the device tree binding for
33 Drivers for devices that use more than a single mux controller can use the
34 "mux-control-names" property to map the name of the requested mux controller
37 mux-ctrl-specifier typically encodes the chip-relative mux controller number.
38 If the mux controller chip only provides a single mux controller, the
43 	/* One consumer of a 2-way mux controller (one GPIO-line) */
44 	mux: mux-controller {
63 because there is only one mux controller in the list. However, if the driver
64 for the consumer node in fact asks for a named mux controller, that name is of
71 	mux: mux-controller {
120 Mux controller nodes
123 Mux controller nodes must specify the number of cells used for the
126 Optionally, mux controller nodes can also specify the state the mux should
128 idle-state is not present, the mux controller is typically left as is when
130 idle-state property is an array with one idle state for each mux controller.
134 mux controller chips with more than one mux controller, particularly when
135 there is a need to "step past" a mux controller and set some other idle
136 state for a mux controller with a higher index.
148 An example mux controller node look like this (the adg972a chip is a triple
151 	mux: mux-controller@50 {