Home
last modified time | relevance | path

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

12345678910

/kernel/linux/linux-5.10/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");
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-5.10/drivers/net/mdio/
DKconfig193 tristate "Amlogic G12a based MDIO bus multiplexer"
199 This module provides a driver for the MDIO multiplexer/glue of
210 iProc based Broadcom SoCs. This multiplexer connects one of several
212 external and selection logic lies inside the same multiplexer.
220 are controlled via GPIO lines. The multiplexer connects one of
225 tristate "MDIO bus multiplexer using kernel multiplexer subsystem"
227 select MULTIPLEXER
230 This module provides a driver for MDIO bus multiplexer
231 that is controlled via the kernel multiplexer subsystem. The
232 bus multiplexer connects one of several child MDIO busses to
[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");
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mux/
Dgpio-mux.txt1 GPIO-based multiplexer controller bindings
3 Define what GPIO pins are used to control a multiplexer. Or several
4 multiplexers, if the same pins control more than one multiplexer.
8 - mux-gpios : list of gpios used to control the multiplexer, least
17 The multiplexer state is defined as the number represented by the
18 multiplexer GPIO pins, where the first pin is the least significant
Dmux-controller.txt1 Common multiplexer controller bindings
4 A multiplexer (or mux) controller will have one, or several, consumer devices
7 multiplexer needed by each consumer, but a single mux controller can of course
11 space is a simple zero-based enumeration. I.e. 0-1 for a 2-way multiplexer,
12 0-7 for an 8-way multiplexer, etc.
129 it is idle. For multiplexer chips that expose several mux controllers, the
139 multiplexer. Using this disconnected high-impedance state as the idle state
149 4-way multiplexer):
Dreg-mux.txt1 Generic register bitfield-based multiplexer controller bindings
19 The multiplexer state of each multiplexer is defined as the value of the
42 compatible = "mdio-mux-multiplexer";
65 compatible = "mdio-mux-multiplexer";
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/adc/
Dxilinx-xadc.txt26 * "none": No external multiplexer is used, this is the default
28 * "single": External multiplexer mode is used with one
29 multiplexer.
30 * "dual": External multiplexer mode is used with two
34 Valid values for single external multiplexer mode are:
40 Valid values for dual external multiplexer mode are:
47 external multiplexer mode (either single or dual). If the device is
48 not using external multiplexer mode the property is ignored.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/i2c/
Di2c-mux-gpmux.txt3 This binding describes an I2C bus multiplexer that uses a mux controller
22 - i2c-parent: The phandle of the I2C bus that this multiplexer's master-side
33 + during setup of the multiplexer
34 + between setup of the multiplexer and the child bus I2C transaction
35 + between the child bus I2C transaction and releasing of the multiplexer
36 + during releasing of the multiplexer
38 to the same parent adapter that this multiplexer is connected to are blocked
41 If mux-locked is not present, the multiplexer is assumed to be parent-locked.
Di2c-mux.txt1 Common i2c bus multiplexer/switch properties.
3 An i2c bus multiplexer/switch will have several child busses that are
5 multiplexer/switch will have one child node for each child bus.
31 - Other properties specific to the multiplexer/switch hardware.
38 An NXP pca9548 8 channel I2C multiplexer at address 0x70
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/
Dmdio-mux-multiplexer.txt1 Properties for an MDIO bus multiplexer consumer device
7 Required properties in addition to the MDIO Bus multiplexer properties:
9 - compatible : should be "mmio-mux-multiplexer"
13 each child node of mdio bus multiplexer consumer device represent a mdio
39 compatible = "mdio-mux-multiplexer";
62 compatible = "mdio-mux-multiplexer";
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-mmioreg.txt1 Properties for an MDIO bus multiplexer controlled by a memory-mapped device
3 This is a special case of a MDIO bus multiplexer. A memory-mapped device,
8 Required properties in addition to the generic multiplexer properties:
13 multiplexer. The size field in the 'reg' property is the size of
17 bits in the register control the actual bus multiplexer. The
Dmdio-mux.txt1 Common MDIO bus multiplexer/switch properties.
3 An MDIO bus multiplexer/switch will have several child busses that are
5 bus multiplexer/switch will have one child node for each child bus.
14 - Other properties specific to the multiplexer/switch hardware.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/dma/
Drenesas,shdma.txt6 SHDMA DT nodes to be placed under a DMA multiplexer node. All such compatible
9 multiplexer node. Even if there is only one such DMAC instance on a system, it
10 still has to be placed under such a multiplexer node.
12 * DMA multiplexer
30 dmac: dma-multiplexer@0 {
76 - dmas: a list of <[DMA multiplexer phandle] [MID/RID value]> pairs,
/kernel/linux/linux-5.10/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.
/kernel/linux/linux-5.10/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
/kernel/linux/linux-5.10/drivers/usb/typec/
Dmux.c3 * USB Type-C Multiplexer/DeMultiplexer Switch support
246 * fwnode_typec_mux_get - Find USB Type-C Multiplexer
270 * typec_mux_put - Release handle to a Multiplexer
271 * @mux: USB Type-C Connector Multiplexer/DeMultiplexer
304 * typec_mux_register - Register Multiplexer routing USB Type-C pins
306 * @desc: Multiplexer description
311 * multiplexer switches routing the pins on the connector.
349 * typec_mux_unregister - Unregister Multiplexer Switch
350 * @mux: USB Type-C Connector Multiplexer/DeMultiplexer
/kernel/linux/linux-5.10/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
50 Multiplexer ID is to indicate the PDN on which data has to be sent.
58 Function Command Reserved Pad Multiplexer ID Payload length
/kernel/linux/linux-5.10/drivers/usb/typec/mux/
DKconfig3 menu "USB Type-C Multiplexer/DeMultiplexer Switch support"
19 control the USB role switch and also the multiplexer/demultiplexer
/kernel/linux/linux-5.10/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
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/
Damlogic,axg-tdm-formatters.txt16 * "sclk_sel" : bit clock input multiplexer.
18 * "lrclk_sel": sample clock input multiplexer
/kernel/linux/linux-5.10/include/linux/platform_data/
Di2c-mux-reg.h3 * I2C multiplexer using a single register
17 * @n_values: Number of multiplexer channels

12345678910