Home
last modified time | relevance | path

Searched full:mux (Results 1 – 25 of 1201) sorted by relevance

12345678910>>...49

/freebsd/sys/arm/freescale/vybrid/
H A Dvf_iomuxc.h31 #define IOMUXC_PTA6 0x000 /* Software MUX Pad Control Register 0 */
32 #define IOMUXC_PTA8 0x004 /* Software MUX Pad Control Register 1 */
33 #define IOMUXC_PTA9 0x008 /* Software MUX Pad Control Register 2 */
34 #define IOMUXC_PTA10 0x00C /* Software MUX Pad Control Register 3 */
35 #define IOMUXC_PTA11 0x010 /* Software MUX Pad Control Register 4 */
36 #define IOMUXC_PTA12 0x014 /* Software MUX Pad Control Register 5 */
37 #define IOMUXC_PTA16 0x018 /* Software MUX Pad Control Register 6 */
38 #define IOMUXC_PTA17 0x01C /* Software MUX Pad Control Register 7 */
39 #define IOMUXC_PTA18 0x020 /* Software MUX Pad Control Register 8 */
40 #define IOMUXC_PTA19 0x024 /* Software MUX Pad Control Register 9 */
[all …]
/freebsd/sys/contrib/device-tree/Bindings/mux/
H A Dmux-controller.txt4 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 …]
H A Dmux-controller.yaml4 $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 …]
H A Dmux-consumer.yaml4 $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 …]
H A Dreg-mux.txt8 "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 …]
H A Dreg-mux.yaml4 $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 …]
H A Dadi,adg792a.txt5 - #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 …]
H A Dgpio-mux.yaml4 $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 …]
H A Dgpio-mux.txt7 - 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 …]
/freebsd/sys/contrib/device-tree/src/arm/nuvoton/
H A Dnuvoton-wpcm450.dtsi172 smb3_pins: mux-smb3 {
177 smb4_pins: mux-smb4 {
182 smb5_pins: mux-smb5 {
187 scs1_pins: mux-scs1 {
192 scs2_pins: mux-scs2 {
197 scs3_pins: mux-scs3 {
202 smb0_pins: mux-smb0 {
207 smb1_pins: mux-smb1 {
212 smb2_pins: mux-smb2 {
217 bsp_pins: mux
[all...]
/freebsd/sys/contrib/device-tree/Bindings/net/
H A Dmdio-mux-multiplexer.txt3 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 …]
H A Dmdio-mux-multiplexer.yaml4 $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 …]
/freebsd/sys/contrib/device-tree/include/dt-bindings/clock/
H A Dtegra186-clock.h384 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_I2S2 */
386 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_I2S3 */
388 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_SPDF_IN */
392 /** @clkdesc{spi_clks, out, mux, CLK_RST_CONTROLLER_CLK_SOURCE_SPI3} */
394 /** @clkdesc{i2c_clks, out, mux, CLK_RST_CONTROLLER_CLK_SOURCE_I2C1} */
396 /** @clkdesc{i2c_clks, out, mux, CLK_RST_CONTROLLER_CLK_SOURCE_I2C5} */
398 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_SPI1 */
400 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_ISP */
402 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_VI */
404 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_SDMMC1 */
[all …]
H A Dtegra234-clock.h12 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_ACTMON */
18 /** output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_AHUB */
22 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_APE */
24 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_AUD_MCLK */
26 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_AXI_CBB */
28 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_CAN1 */
32 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_CAN2 */
38 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_DMIC1 */
40 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_DMIC2 */
42 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_DMIC3 */
[all …]
/freebsd/sys/contrib/device-tree/Bindings/i2c/
H A Di2c-mux-gpmux.txt1 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 …]
H A Di2c-mux-gpmux.yaml4 $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 …]
/freebsd/sys/contrib/device-tree/src/arm64/amlogic/
H A Dmeson-gxl.dtsi156 reg-names = "mux", "pull", "gpio";
163 mux {
171 mux {
180 mux {
188 mux {
196 mux {
205 mux {
213 mux {
222 mux {
230 mux {
[all …]
H A Dmeson-gxbb.dtsi98 reg-names = "mux", "pull", "gpio";
105 mux {
113 mux {
122 mux {
130 mux {
139 mux {
147 mux {
156 mux {
164 mux {
172 mux {
[all …]
H A Dmeson-g12-common.dtsi286 "mux",
294 mux {
302 mux {
310 mux-0 {
317 mux-1 {
326 mux-0 {
338 mux-0 {
354 mux {
363 mux {
372 mux {
[all …]
H A Dmeson-axg.dtsi343 reg-names = "mux", "pull", "pull-enable", "gpio";
350 mux {
359 mux {
368 mux {
377 mux {
386 mux {
395 mux {
404 mux {
413 mux {
422 mux-0 {
[all …]
/freebsd/sys/contrib/device-tree/Bindings/iio/multiplexer/
H A Dio-channel-mux.txt7 - 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 = "gpio-mux";
25 #mux-control-cells = <0>;
27 mux-gpios = <&pioA 0 GPIO_ACTIVE_HIGH>,
[all …]
H A Dio-channel-mux.yaml4 $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 …]
/freebsd/sys/contrib/device-tree/Bindings/media/
H A Dvideo-mux.txt7 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>;
/freebsd/share/man/man4/
H A Diicmux.450 the driver for the specific mux hardware in use.
55 I2C bus multiplexer (mux) hardware.
59 used by individual mux hardware drivers.
60 It will be loaded automatically when needed by a mux hardware driver.
61 This manual page provides an overview of the I2C mux framework and its
64 Generally speaking, an I2C mux is connected to an upstream I2C bus, and to
77 When there is no I/O in progress, the mux is said to be in the
80 Some mux hardware has the ability to disconnect all downstream buses
83 Individual mux hardware drivers typically provide a way to select which
88 When an I2C slave device on a bus downstream of a mux initiates I/O,
[all …]
/freebsd/sys/contrib/device-tree/src/arm/microchip/
H A Dat91-natte.dtsi11 mux: mux-controller { label
12 compatible = "gpio-mux";
13 #mux-control-cells = <0>;
15 mux-gpios = <&ioexp 0 GPIO_ACTIVE_HIGH>,
20 batntc-mux {
21 compatible = "io-channel-mux";
24 mux-controls = <&mux>;
31 batv-mux {
32 compatible = "io-channel-mux";
35 mux-controls = <&mux>;
[all …]

12345678910>>...49