Searched full:mux (Results 1 – 25 of 326) sorted by relevance
12345678910>>...14
| /Documentation/devicetree/bindings/mux/ |
| D | mux-consumer.yaml | 4 $id: http://devicetree.org/schemas/mux/mux-consumer.yaml#
13 Mux controller consumers should specify a list of mux controllers that they
14 want to use with a property containing a 'mux-ctrl-list':
16 mux-ctrl-list ::= <single-mux-ctrl> [mux-ctrl-list]
17 single-mux-ctrl ::= <mux-ctrl-phandle> [mux-ctrl-specifier]
18 mux-ctrl-phandle : phandle to mux controller node
19 mux-ctrl-specifier : array of #mux-control-cells specifying the
20 given mux controller (controller specific)
22 Mux controller properties should be named "mux-controls". The exact meaning of
23 each mux controller property must be documented in the device tree binding for
[all …]
|
| D | mux-controller.yaml | 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' 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'.
[all …]
|
| D | reg-mux.yaml | 4 $id: http://devicetree.org/schemas/mux/reg-mux.yaml#
19 - reg-mux # parent device of mux controller is not syscon device
20 - mmio-mux # parent device of mux controller is syscon device
24 '#mux-control-cells':
27 mux-reg-masks:
33 description: Each entry pair describes a single mux control.
39 - mux-reg-masks
40 - '#mux-control-cells'
46 /* The parent device of mux controller is not a syscon device. */
48 #include <dt-bindings/mux/mux.h>
[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.yaml
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.yaml | 4 $id: http://devicetree.org/schemas/mux/gpio-mux.yaml#
22 const: gpio-mux
24 mux-gpios:
28 '#mux-control-cells':
31 '#mux-state-cells':
39 - mux-gpios
42 - "#mux-control-cells"
44 - "#mux-state-cells"
52 mux: mux-controller {
53 compatible = "gpio-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.yaml
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.yaml | 4 $id: http://devicetree.org/schemas/net/mdio-mux-multiplexer.yaml#
13 This is a special case of MDIO mux when MDIO mux is defined as a consumer
14 of a mux producer device. The mux producer can be of any type like mmio mux
15 producer, gpio mux producer or generic register based mux producer.
19 - $ref: /schemas/net/mdio-mux.yaml#
23 const: mdio-mux-multiplexer
25 mux-controls:
30 - mux-controls
36 mux: mux-controller { // Mux Producer
37 compatible = "reg-mux";
[all …]
|
| D | mdio-mux-mmioreg.yaml | 4 $id: http://devicetree.org/schemas/net/mdio-mux-mmioreg.yaml#
14 like an FPGA, is used to control which child bus is connected. The mdio-mux
19 - $ref: /schemas/net/mdio-mux.yaml#
24 - const: mdio-mux-mmioreg
25 - const: mdio-mux
33 mux-mask:
37 child mdio-mux node must be constrained by this mask.
42 - mux-mask
48 mdio-mux@9 {
49 compatible = "mdio-mux-mmioreg", "mdio-mux";
[all …]
|
| /Documentation/devicetree/bindings/iio/multiplexer/ |
| D | io-channel-mux.yaml | 4 $id: http://devicetree.org/schemas/iio/multiplexer/io-channel-mux.yaml#
18 of strings in the channels property, and also matches the mux controller
19 state. The mux controller state is described in
20 Documentation/devicetree/bindings/mux/mux-controller.yaml
25 const: io-channel-mux
34 mux-controls: true
35 mux-control-names: true
40 List of strings, labeling the mux controller states. An empty
55 - mux-controls
63 mux: mux-controller {
[all …]
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-mux-gpmux.yaml | 4 $id: http://devicetree.org/schemas/i2c/i2c-mux-gpmux.yaml#
7 title: General Purpose I2C Bus Mux
13 This binding describes an I2C bus multiplexer that uses a mux controller
14 from the mux subsystem to route the I2C signals.
21 | .------. | .------+ child bus A, on MUX value set to 0
22 | | I2C |-|--| Mux |
23 | '------' | '--+---+ child bus B, on MUX value set to 1
25 | | MUX- | | | | | |
32 - $ref: /schemas/i2c/i2c-mux.yaml#
36 const: i2c-mux
[all …]
|
| /Documentation/i2c/ |
| D | i2c-topology.rst | 10 1. A mux may be needed on the bus to prevent address collisions.
25 I2C transfers, and all adapters with a parent are part of an "i2c-mux"
28 Depending of the particular mux driver, something happens when there is
29 an I2C transfer on one of its child adapters. The mux driver can
30 obviously operate a mux, but it can also do arbitration with an external
31 bus master or open a gate. The mux driver has two operations for this,
40 mux-locked or parent-locked muxes.
43 Mux-locked muxes
46 Mux-locked muxes does not lock the entire parent adapter during the
48 adapter are locked. Mux-locked muxes are mostly interesting if the
[all …]
|
| D | i2c-sysfs.rst | 10 I2C topology can be complex because of the existence of I2C MUX
12 kernel abstracts the MUX channels into logical I2C bus numbers. However, there
13 is a gap of knowledge to map from the I2C bus physical number and MUX topology
32 2. General knowledge of I2C, I2C MUX and I2C topology.
85 an abstraction of a channel behind an I2C MUX. In case it is an abstraction of a
86 MUX channel, whenever we access an I2C device via a such logical bus, the kernel
87 will switch the I2C MUX for you to the proper channel as part of the
109 MUX fanouts. For the following examples, we will assume that the physical I2C
123 `-- 7-0071 (4-channel I2C MUX at 0x71)
127 | |-- 73-0070 (I2C MUX at 0x70, exists in DTS, but failed to probe)
[all …]
|
| /Documentation/devicetree/bindings/media/ |
| D | video-mux.yaml | 4 $id: http://devicetree.org/schemas/media/video-mux.yaml#
20 const: video-mux
22 mux-controls:
53 - mux-controls
69 mux: mux-controller {
70 compatible = "gpio-mux";
71 #mux-control-cells = <0>;
73 mux-gpios = <&gpio1 15 GPIO_ACTIVE_HIGH>;
76 video-mux {
77 compatible = "video-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/muxchip<N>/
15 A /sys/class/mux/muxchipN directory is created for each
16 probed MUX chip where N is a simple enumeration.
|
| /Documentation/devicetree/bindings/soc/microchip/ |
| D | microchip,sparx5-cpu-syscon.yaml | 22 mux-controller:
23 $ref: /schemas/mux/reg-mux.yaml#
28 - mux-controller
43 mux: mux-controller {
44 compatible = "mmio-mux";
45 #mux-control-cells = <1>;
46 mux-reg-masks = <0x88 0xf0>;
|
| /Documentation/devicetree/bindings/soc/ti/ |
| D | ti,am654-serdes-ctrl.yaml | 22 mux-controller:
23 $ref: /schemas/mux/reg-mux.yaml#
28 - mux-controller
38 mux-controller {
39 compatible = "mmio-mux";
40 #mux-control-cells = <1>;
41 mux-reg-masks = <0x0 0x3>; /* lane select */
|
| /Documentation/firmware-guide/acpi/ |
| D | intel-pmc-mux.rst | 4 Intel North Mux-Agent
10 North Mux-Agent is a function of the Intel PMC firmware that is supported on
13 platforms that allow the mux-agent to be configured from the operating system
16 The North Mux-Agent (aka. Intel PMC Mux Control, or just mux-agent) driver
19 Mux Class which allows the USB Type-C Controller and Interface drivers to
22 Device modes. The driver is located here: drivers/usb/typec/mux/intel_pmc_mux.c.
30 For every USB Type-C connector under the mux-agent control on the system, there
31 is a separate child node under the PMC mux-agent device node. Those nodes do not
32 represent the actual connectors, but instead the "channels" in the mux-agent
35 Scope (_SB.PCI0.PMC.MUX)
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | nxp,imx95-display-master-csr.yaml | 34 mux-controller:
36 $ref: /schemas/mux/reg-mux.yaml
42 - mux-controller
57 mux: mux-controller {
58 compatible = "mmio-mux";
59 #mux-control-cells = <1>;
60 mux-reg-masks = <0x4 0x00000001>; /* Pixel_link_sel */
|
| /Documentation/devicetree/bindings/sound/ |
| D | simple-audio-mux.yaml | 4 $id: http://devicetree.org/schemas/sound/simple-audio-mux.yaml#
21 const: simple-audio-mux
23 mux-gpios:
36 - mux-gpios
42 mux {
43 compatible = "simple-audio-mux";
44 mux-gpios = <&gpio 3 0>;
|
| D | mt8186-afe-pcm.yaml | 44 - description: audio top mux
45 - description: audio intbus mux
47 - description: faud1 mux
49 - description: faud2 mux
51 - description: audio engen1 mux
53 - description: audio engen2 mux
55 - description: i2s0 mclk mux
56 - description: i2s1 mclk mux
57 - description: i2s2 mclk mux
58 - description: i2s4 mclk mux
[all …]
|
| /Documentation/devicetree/bindings/clock/ti/ |
| D | mux.txt | 1 Binding for TI mux clock.
29 The binding must provide the register to control the mux. Optionally
37 - compatible : shall be "ti,mux-clock" or "ti,composite-mux-clock".
40 - reg : register offset for register controlling adjustable mux
49 not supported by the composite-mux-clock subtype
50 - ti,latch-bit : latch the mux value to HW, only needed if the register
58 compatible = "ti,mux-clock";
66 compatible = "ti,mux-clock";
74 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/spi/ |
| D | spi-mux.yaml | 4 $id: http://devicetree.org/schemas/spi/spi-mux.yaml#
13 setting of the multiplexer to a channel needs to be done by a specific SPI mux
24 | | SPI +-|-------+ Mux |\\ CS-0 | | | |
41 const: spi-mux
43 mux-controls:
50 - mux-controls
57 mux: mux-controller {
58 compatible = "gpio-mux";
59 #mux-control-cells = <0>;
61 mux-gpios = <&gpio0 3 GPIO_ACTIVE_HIGH>;
[all …]
|
| /Documentation/devicetree/bindings/soc/imx/ |
| D | fsl,imx-iomuxc-gpr.yaml | 49 mux-controller:
51 $ref: /schemas/mux/reg-mux.yaml
66 mux: mux-controller {
67 compatible = "mmio-mux";
68 #mux-control-cells = <1>;
69 mux-reg-masks = <0x34 0x00000004>; /* MIPI_MUX_SEL */
|
| /Documentation/devicetree/bindings/board/ |
| D | fsl,fpga-qixis-i2c.yaml | 32 mux-controller:
33 $ref: /schemas/mux/reg-mux.yaml
63 mux-controller {
64 compatible = "reg-mux";
65 #mux-control-cells = <1>;
66 mux-reg-masks = <0x54 0xf0>; /* 0: reg 0x54, bits 7:4 */
|
12345678910>>...14