Home
last modified time | relevance | path

Searched full:multiplexer (Results 1 – 25 of 226) sorted by relevance

12345678910

/Linux-v5.15/drivers/mux/
DKconfig3 # Multiplexer devices
6 config MULTIPLEXER config
9 menu "Multiplexer drivers"
10 depends on MULTIPLEXER
28 ADGS1408 8:1 multiplexer and ADGS1409 double 4:1 multiplexer
35 tristate "GPIO-controlled Multiplexer"
38 GPIO-controlled Multiplexer controller.
40 The driver builds a single multiplexer controller using a number
41 of gpio pins. For N pins, there will be 2^N possible multiplexer
49 tristate "MMIO/Regmap register bitfield-controlled Multiplexer"
[all …]
Dcore.c3 * Multiplexer subsystem
27 * as indication that the cached state of the multiplexer is unknown.
282 * mux_control_states() - Query the number of multiplexer states.
285 * Return: The number of multiplexer states.
318 * mux_control_select() - Select the given multiplexer state.
352 * mux_control_try_select() - Try to select the given multiplexer state.
383 * mux_control_deselect() - Deselect the previously selected multiplexer state.
539 MODULE_DESCRIPTION("Multiplexer subsystem");
/Linux-v5.15/drivers/i2c/muxes/
DKconfig3 # Multiplexer I2C chip drivers configuration
6 menu "Multiplexer I2C Chip support"
23 tristate "GPIO-based I2C multiplexer"
27 GPIO based I2C multiplexer. This driver provides access to
35 tristate "General Purpose I2C multiplexer"
36 select MULTIPLEXER
40 general purpose I2C multiplexer. This driver provides access to
48 tristate "LTC LTC4306/5 I2C multiplexer"
78 tristate "pinctrl-based I2C multiplexer"
83 multiplexer that uses the pinctrl subsystem, i.e. pin multiplexing.
[all …]
/Linux-v5.15/drivers/net/mdio/
DKconfig208 tristate "Amlogic G12a based MDIO bus multiplexer"
214 This module provides a driver for the MDIO multiplexer/glue of
225 BCM6368 based Broadcom SoCs. This multiplexer connects one of several
227 external and selection logic lies inside the same multiplexer.
236 iProc based Broadcom SoCs. This multiplexer connects one of several
238 external and selection logic lies inside the same multiplexer.
246 are controlled via GPIO lines. The multiplexer connects one of
251 tristate "MDIO bus multiplexer using kernel multiplexer subsystem"
253 select MULTIPLEXER
256 This module provides a driver for MDIO bus multiplexer
[all …]
Dmdio-mux-multiplexer.c2 /* MDIO bus multiplexer using kernel multiplexer subsystem
21 * multiplexer needs to switch.
104 { .compatible = "mdio-mux-multiplexer", },
111 .name = "mdio-mux-multiplexer",
120 MODULE_DESCRIPTION("MDIO bus multiplexer using kernel multiplexer subsystem");
/Linux-v5.15/Documentation/devicetree/bindings/mux/
Dmux-controller.yaml7 title: Common multiplexer controller provider bindings
13 A multiplexer (or mux) controller will have one, or several, consumer devices
16 multiplexer needed by each consumer, but a single mux controller can of course
20 space is a simple zero-based enumeration. I.e. 0-1 for a 2-way multiplexer,
21 0-7 for an 8-way multiplexer, etc.
33 it is idle. For multiplexer chips that expose several mux controllers, the
43 multiplexer. Using this disconnected high-impedance state as the idle state
53 4-way multiplexer):
86 left as is when it is idle. For multiplexer chips that expose several mux
97 multiplexer. Using this disconnected high-impedance state as the idle state
Dgpio-mux.yaml7 title: GPIO-based multiplexer controller bindings
13 Define what GPIO pins are used to control a multiplexer. Or several
14 multiplexers, if the same pins control more than one multiplexer.
16 The multiplexer state is defined as the number represented by the
17 multiplexer GPIO pins, where the first pin is the least significant
26 List of gpios used to control the multiplexer, least significant bit first.
Dreg-mux.yaml7 title: Generic register bitfield-based multiplexer controller bindings
55 compatible = "mdio-mux-multiplexer";
75 compatible = "mdio-mux-multiplexer";
/Linux-v5.15/Documentation/devicetree/bindings/i2c/
Di2c-mux-gpmux.yaml13 This binding describes an I2C bus multiplexer that uses a mux controller
42 The phandle of the I2C bus that this multiplexer's master-side port is
55 - during setup of the multiplexer
56 - between setup of the multiplexer and the child bus I2C transaction
57 - between the child bus I2C transaction and releasing of the multiplexer
58 - during releasing of the multiplexer
61 to the same parent adapter that this multiplexer is connected to are blocked
64 If mux-locked is not present, the multiplexer is assumed to be parent-locked.
Di2c-mux.yaml7 title: Common i2c bus multiplexer/switch properties.
13 An i2c bus multiplexer/switch will have several child busses that are numbered
15 multiplexer/switch will have one child node for each child bus.
47 * An NXP pca9548 8 channel I2C multiplexer at address 0x70
/Linux-v5.15/Documentation/devicetree/bindings/net/
Dmdio-mux-meson-g12a.txt1 Properties for the MDIO bus multiplexer/glue of Amlogic G12a SoC family.
3 This is a special case of a MDIO bus multiplexer. It allows to choose between
7 Required properties in addition to the generic multiplexer properties:
9 - reg: physical address and length of the multiplexer/glue registers
18 mdio_mux: mdio-multiplexer@4c000 {
Dbrcm,mdio-mux-iproc.txt1 Properties for an MDIO bus multiplexer found in Broadcom iProc based SoCs.
3 This MDIO bus multiplexer defines buses that could be internal as well as
8 Required properties in addition to the generic multiplexer properties:
10 MDIO multiplexer node:
19 Additional information regarding generic multiplexer properties can be found
Dmdio-mux-multiplexer.yaml4 $id: http://devicetree.org/schemas/net/mdio-mux-multiplexer.yaml#
7 title: Properties for an MDIO bus multiplexer consumer device
23 const: mdio-mux-multiplexer
44 compatible = "mdio-mux-multiplexer";
64 compatible = "mdio-mux-multiplexer";
Dmdio-mux.yaml7 title: Common MDIO bus multiplexer/switch properties.
13 An MDIO bus multiplexer/switch will have several child busses that are
15 bus multiplexer/switch will have one child node for each child bus.
24 The phandle of the MDIO bus that this multiplexer's master-side port is
Dmdio-mux-mmioreg.yaml7 title: Properties for an MDIO bus multiplexer controlled by a memory-mapped device
13 This is a special case of a MDIO bus multiplexer. A memory-mapped device,
29 multiplexer. The size field in the 'reg' property is the size of register,
36 register control the actual bus multiplexer. The 'reg' property of each
/Linux-v5.15/Documentation/devicetree/bindings/iio/adc/
Dxilinx-xadc.txt38 * "none": No external multiplexer is used, this is the default
40 * "single": External multiplexer mode is used with one
41 multiplexer.
42 * "dual": External multiplexer mode is used with two
46 Valid values for single external multiplexer mode are:
52 Valid values for dual external multiplexer mode are:
59 external multiplexer mode (either single or dual). If the device is
60 not using external multiplexer mode the property is ignored.
/Linux-v5.15/drivers/iio/multiplexer/
DKconfig3 # Multiplexer drivers
10 tristate "IIO multiplexer driver"
11 select MULTIPLEXER
14 Say yes here to build support for the IIO multiplexer.
/Linux-v5.15/include/dt-bindings/mux/
Dmux.h3 * This header provides constants for most Multiplexer bindings.
5 * Most Multiplexer bindings specify an idle state. In most cases, the
6 * multiplexer can be left as is when idle, and in some cases it can
7 * disconnect the input/output and leave the multiplexer in a high
/Linux-v5.15/Documentation/devicetree/bindings/display/imx/
Dfsl,imx6-hdmi.yaml45 phandle to the iomuxc-gpr region containing the HDMI multiplexer control
52 HDMI multiplexer. Each port shall have a single endpoint.
57 description: First input of the HDMI multiplexer
61 description: Second input of the HDMI multiplexer
65 description: Third input of the HDMI multiplexer
69 description: Fourth input of the HDMI multiplexer
/Linux-v5.15/Documentation/networking/device_drivers/cellular/qualcomm/
Drmnet.rst20 packets with MAP headers to rmnet. Based on the multiplexer id, rmnet
37 Function Command / Data Reserved Pad Multiplexer ID Payload length
51 Multiplexer ID is to indicate the PDN on which data has to be sent.
63 Function Command / Data Reserved Pad Multiplexer ID Payload length
77 Multiplexer ID is to indicate the PDN on which data has to be sent.
116 Function Command / Data Next header Pad Multiplexer ID Payload length
131 Multiplexer ID is to indicate the PDN on which data has to be sent.
160 Function Command Reserved Pad Multiplexer ID Payload length
/Linux-v5.15/drivers/usb/typec/
Dmux.c3 * USB Type-C Multiplexer/DeMultiplexer Switch support
253 * fwnode_typec_mux_get - Find USB Type-C Multiplexer
277 * typec_mux_put - Release handle to a Multiplexer
278 * @mux: USB Type-C Connector Multiplexer/DeMultiplexer
311 * typec_mux_register - Register Multiplexer routing USB Type-C pins
313 * @desc: Multiplexer description
318 * multiplexer switches routing the pins on the connector.
356 * typec_mux_unregister - Unregister Multiplexer Switch
357 * @mux: USB Type-C Connector Multiplexer/DeMultiplexer
/Linux-v5.15/Documentation/devicetree/bindings/iio/multiplexer/
Dio-channel-mux.yaml4 $id: http://devicetree.org/schemas/iio/multiplexer/io-channel-mux.yaml#
7 title: I/O channel multiplexer bindings
13 If a multiplexer is used to select which hardware signal is fed to
/Linux-v5.15/drivers/usb/typec/mux/
DKconfig3 menu "USB Type-C Multiplexer/DeMultiplexer Switch support"
19 control the USB role switch and also the multiplexer/demultiplexer
/Linux-v5.15/drivers/clk/meson/
Dclk-regmap.h88 * struct clk_regmap_mux_data - regmap backed multiplexer clock specific data
91 * @offset: offset of theregister controlling multiplexer
93 * @shift: shift to multiplexer bit field
/Linux-v5.15/Documentation/devicetree/bindings/sound/
Damlogic,axg-tdm-formatters.txt16 * "sclk_sel" : bit clock input multiplexer.
18 * "lrclk_sel": sample clock input multiplexer

12345678910