Searched full:mux (Results 1 – 25 of 234) sorted by relevance
12345678910
| /Documentation/devicetree/bindings/mux/ |
| D | mux-controller.txt | 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
19 want to use with a property containing a 'mux-ctrl-list':
21 mux-ctrl-list ::= <single-mux-ctrl> [mux-ctrl-list]
22 single-mux-ctrl ::= <mux-ctrl-phandle> [mux-ctrl-specifier]
23 mux-ctrl-phandle : phandle to mux controller node
24 mux-ctrl-specifier : array of #mux-control-cells specifying the
[all …]
|
| D | reg-mux.txt | 8 "reg-mux" : if parent device of mux controller is not syscon device
9 "mmio-mux" : if parent device of mux controller is syscon device
10 - #mux-control-cells : <1>
11 - mux-reg-masks : an array of register offset and pre-shifted bitfield mask
12 pairs, each describing a single mux control.
13 * Standard mux-controller bindings as decribed in mux-controller.txt
21 pair in the mux-reg-masks array.
24 The parent device of mux controller is not a syscon device.
32 mux: mux-controller {
33 compatible = "reg-mux";
[all …]
|
| D | adi,adg792a.txt | 5 - #mux-control-cells : <0> if parallel (the three muxes are bound together
6 with a single mux controller controlling all three muxes), or <1> if
7 not (one mux controller for each mux).
8 * Standard mux-controller bindings as described in mux-controller.txt
18 - idle-state : if present, array of states that the mux controllers will have
27 * Three independent mux controllers (of which one is used).
28 * Mux 0 is disconnected when idle, mux 1 idles in the previously
29 * selected state and mux 2 idles with signal B.
32 mux: mux-controller@50 {
35 #mux-control-cells = <1>;
[all …]
|
| D | gpio-mux.txt | 7 - compatible : "gpio-mux"
8 - mux-gpios : list of gpios used to control the multiplexer, least
10 - #mux-control-cells : <0>
11 * Standard mux-controller bindings as decribed in mux-controller.txt
14 - idle-state : if present, the state the mux will have when idle. The
23 mux: mux-controller {
24 compatible = "gpio-mux";
25 #mux-control-cells = <0>;
27 mux-gpios = <&pioA 0 GPIO_ACTIVE_HIGH>,
31 adc-mux {
[all …]
|
| D | adi,adgs1408.txt | 1 Bindings for Analog Devices ADGS1408/1409 8:1/Dual 4:1 Mux
7 * Standard mux-controller bindings as described in mux-controller.txt
18 - idle-state : if present, the state that the mux controller will have
28 * One mux controller.
29 * Mux state set to idle as is (no idle-state declared)
32 mux: mux-controller@0 {
36 #mux-control-cells = <0>;
40 adc-mux {
41 compatible = "io-channel-mux";
44 mux-controls = <&mux>;
|
| /Documentation/devicetree/bindings/net/ |
| D | mdio-mux-multiplexer.txt | 3 This is a special case of MDIO mux when MDIO mux is defined as a consumer
4 of a mux producer device. The mux producer can be of any type like mmio mux
5 producer, gpio mux producer or generic register based mux producer.
9 - compatible : should be "mmio-mux-multiplexer"
10 - mux-controls : mux controller node to use for operating the mux
17 Documentation/devicetree/bindings/mux/mux-controller.txt
18 and Documentation/devicetree/bindings/net/mdio-mux.txt
21 In below example the Mux producer and consumer are separate nodes.
29 mux: mux-controller { // Mux Producer
30 compatible = "reg-mux";
[all …]
|
| D | mdio-mux-mmioreg.txt | 4 like an FPGA, is used to control which child bus is connected. The mdio-mux
10 - compatible : string, must contain "mdio-mux-mmioreg"
16 - mux-mask : integer, contains an eight-bit mask that specifies which
18 'reg' property of each child mdio-mux node must be constrained by
24 For the "EMI2" MDIO bus, register 9 (BRDCFG1) controls the mux on that bus.
26 BRDCFG1 that control the actual mux.
36 mdio-mux-emi2 {
37 compatible = "mdio-mux-mmioreg", "mdio-mux";
42 mux-mask = <0x6>; // EMI2
|
| /Documentation/devicetree/bindings/iio/multiplexer/ |
| D | io-channel-mux.txt | 7 - compatible : "io-channel-mux"
13 - mux-controls : Mux controller node to use for operating the mux
14 - channels : List of strings, labeling the mux controller states.
18 the list of strings in the channels property, and also matches the mux
19 controller state. The mux controller state is described in
20 ../mux/mux-controller.txt
23 mux: mux-controller {
24 compatible = "mux-gpio";
25 #mux-control-cells = <0>;
27 mux-gpios = <&pioA 0 GPIO_ACTIVE_HIGH>,
[all …]
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-mux-gpmux.txt | 1 General Purpose I2C Bus Mux
3 This binding describes an I2C bus multiplexer that uses a mux controller
4 from the mux subsystem to route the I2C signals.
11 | .------. | .------+ child bus A, on MUX value set to 0
12 | | I2C |-|--| Mux |
13 | '------' | '--+---+ child bus B, on MUX value set to 1
15 | | MUX- | | | | | |
21 - compatible: i2c-mux
24 - mux-controls: The phandle of the mux controller to use for operating the
25 mux.
[all …]
|
| D | i2c-mux-reg.txt | 1 Register-based I2C Bus Mux
7 - compatible: i2c-mux-reg
10 * Standard I2C mux properties. See i2c-mux.txt in this directory.
11 * I2C child bus nodes. See i2c-mux.txt in this directory.
14 - reg: this pair of <offset size> specifies the register to control the mux.
36 Example of a mux on PCIe card, the host is a powerpc SoC (big endian):
38 i2c-mux {
46 compatible = "i2c-mux-reg";
|
| D | i2c-mux.txt | 9 This property is required if the i2c-mux child node does not exist.
12 This property is required if the i2c-mux child node does not exist.
14 - i2c-mux
16 of both i2c child busses and other child nodes, the 'i2c-mux' subnode
17 can be used for populating the i2c child busses. If an 'i2c-mux'
21 Required properties for the i2c-mux child node:
43 mux@70 {
|
| D | i2c-mux-gpio.txt | 1 GPIO-based I2C Bus Mux
12 | | I2C |-|--| Mux |
21 - compatible: i2c-mux-gpio
24 - mux-gpios: list of gpios used to control the muxer
25 * Standard I2C mux properties. See i2c-mux.txt in this directory.
26 * I2C child bus nodes. See i2c-mux.txt in this directory.
49 compatible = "i2c-mux-gpio";
52 mux-gpios = <&gpio1 22 0 &gpio1 23 0>;
|
| D | i2c-mux-ltc4306.txt | 11 - Standard I2C mux properties. See i2c-mux.txt in this directory.
12 - I2C child bus nodes. See i2c-mux.txt in this directory.
17 - i2c-mux-idle-disconnect: Boolean; if defined, forces mux to disconnect all
31 ltc4306: i2c-mux@4a {
|
| D | i2c-mux-pca954x.txt | 3 The driver supports NXP PCA954x and PCA984x I2C mux/switch devices.
22 - Standard I2C mux properties. See i2c-mux.txt in this directory.
23 - I2C child bus nodes. See i2c-mux.txt in this directory.
28 - i2c-mux-idle-disconnect: Boolean; if defined, forces mux to disconnect all
|
| /Documentation/devicetree/bindings/media/ |
| D | video-mux.txt | 7 the bindings in Documentation/devicetree/bindings/mux/mux-controller.txt
10 - compatible : should be "video-mux"
11 - mux-controls : mux controller node to use for operating the mux
23 mux: mux-controller {
24 compatible = "gpio-mux";
25 #mux-control-cells = <0>;
27 mux-gpios = <&gpio1 15 GPIO_ACTIVE_HIGH>;
30 video-mux {
31 compatible = "video-mux";
32 mux-controls = <&mux>;
|
| /Documentation/i2c/ |
| D | i2c-topology.rst | 8 1. A mux may be needed on the bus to prevent address collisions.
23 i2c transfers, and all adapters with a parent are part of an "i2c-mux"
26 Depending of the particular mux driver, something happens when there is
27 an i2c transfer on one of its child adapters. The mux driver can
28 obviously operate a mux, but it can also do arbitration with an external
29 bus master or open a gate. The mux driver has two operations for this,
38 mux-locked or parent-locked muxes. As is evident from below, it can be
39 useful to know if a mux is mux-locked or if it is parent-locked. The
46 i2c-mux-gpio Normally parent-locked, mux-locked iff
48 same i2c root adapter that they mux.
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-mux | 1 What: /sys/class/mux/
6 The mux/ class sub-directory belongs to the Generic MUX
7 Framework and provides a sysfs interface for using MUX
10 What: /sys/class/mux/muxchipN/
15 A /sys/class/mux/muxchipN directory is created for each
16 probed MUX chip where N is a simple enumeration.
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | mrvl,intc.txt | 5 "mrvl,mmp2-mux-intc"
8 of the whole interrupt controller. If the interrupt controller is mux-intc,
9 address and length means one register. Since address of mux-intc is in the
10 range of intc. mux-intc is secondary interrupt controller.
12 only required in mux-intc interrupt controller.
13 - interrupts : Should be the port interrupt shared by mux interrupts. It's
14 only required in mux-intc interrupt controller.
33 compatible = "mrvl,mmp2-mux-intc";
38 reg-names = "mux status", "mux mask";
|
| /Documentation/devicetree/bindings/clock/ti/ |
| D | mux.txt | 1 Binding for TI mux clock.
31 The binding must provide the register to control the mux. Optionally
39 - compatible : shall be "ti,mux-clock" or "ti,composite-mux-clock".
42 - reg : register offset for register controlling adjustable mux
50 not supported by the composite-mux-clock subtype
51 - ti,latch-bit : latch the mux value to HW, only needed if the register
59 compatible = "ti,mux-clock";
67 compatible = "ti,mux-clock";
75 compatible = "ti,composite-mux-clock";
|
| /Documentation/i2c/muxes/ |
| D | i2c-mux-gpio.rst | 2 Kernel driver i2c-mux-gpio
10 i2c-mux-gpio is an i2c mux driver providing access to I2C bus segments
11 from a master I2C bus and a hardware MUX controlled through GPIO pins.
19 | Linux | GPIO 1..N | MUX |--------------- Devices
31 i2c-mux-gpio uses the platform bus, so you need to provide a struct
35 to control it. See include/linux/platform_data/i2c-mux-gpio.h for details.
37 E.G. something like this for a MUX providing 4 bus segments
40 #include <linux/platform_data/i2c-mux-gpio.h>
62 .name = "i2c-mux-gpio",
71 numbers, and the i2c-mux-gpio driver will do the work for you,
[all …]
|
| /Documentation/devicetree/bindings/mtd/ |
| D | ti,am654-hbmc.txt | 13 - mux-controls : phandle to the multiplexer that controls selection of
16 See Documentation/devicetree/bindings/mux/reg-mux.txt
17 for mmio-mux binding details
29 compatible = "mmio-mux";
30 #mux-control-cells = <1>;
31 mux-reg-masks = <0x4 0x2>; /* 0: reg 0x4, bit 1 */
44 mux-controls = <&hbmc_mux 0>;
|
| /Documentation/devicetree/bindings/ |
| D | unittest.txt | 43 4) OF unittest i2c mux device
45 ** I2C unittest mux
48 - compatible: must be unittest-i2c-mux
53 unittest-i2c-mux {
54 compatible = "unittest-i2c-mux";
|
| /Documentation/devicetree/bindings/display/msm/ |
| D | hdmi.txt | 18 - hdmi-mux-supply: phandle to mux regulator
24 - qcom,hdmi-tx-mux-en-gpios: hdmi mux enable pin
25 - qcom,hdmi-tx-mux-sel-gpios: hdmi mux select pin
26 - qcom,hdmi-tx-mux-lpm-gpios: hdmi mux lpm pin
78 hdmi-mux-supply = <&ext_3p3v>;
|
| /Documentation/devicetree/bindings/sound/ |
| D | eukrea-tlv320.txt | 11 - fsl,mux-int-port : The internal port of the i.MX audio muxer (AUDMUX).
13 - fsl,mux-ext-port : The external port of the i.MX audio muxer.
24 fsl,mux-int-port = <2>;
25 fsl,mux-ext-port = <3>;
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | cortina,gemini-pinctrl.txt | 37 mux {
43 mux {
49 mux {
55 mux {
62 mux {
|
12345678910