| /kernel/linux/linux-5.10/drivers/net/mdio/ |
| D | Kconfig | 47 This module provides a driver for the MDIO busses found in the
78 This module provides a driver for the MDIO busses found in the
85 This module provides a driver for the Broadcom UniMAC MDIO busses.
98 Supports GPIO lib-based MDIO busses.
107 This module provides a driver for the MDIO busses found in the
188 multiplexers which connect one of several child MDIO busses
189 to a parent bus. Switching between child busses is done by
221 several child MDIO busses to a parent bus. Child bus
232 bus multiplexer connects one of several child MDIO busses to
243 The multiplexer connects one of several child MDIO busses to a
|
| /kernel/linux/linux-6.6/drivers/net/mdio/ |
| D | Kconfig | 61 This module provides a driver for the MDIO busses found in the
93 This module provides a driver for the MDIO busses found in the
100 This module provides a driver for the Broadcom UniMAC MDIO busses.
113 Supports GPIO lib-based MDIO busses.
122 This module provides a driver for the MDIO busses found in the
217 multiplexers which connect one of several child MDIO busses
218 to a parent bus. Switching between child busses is done by
272 several child MDIO busses to a parent bus. Child bus
283 bus multiplexer connects one of several child MDIO busses to
294 The multiplexer connects one of several child MDIO busses to a
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/i2c/ |
| D | i2c-mux.txt | 3 An i2c bus multiplexer/switch will have several child busses that are
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'
19 child busses.
|
| D | i2c-fsi.txt | 1 Device-tree bindings for FSI-attached I2C master and busses
11 - child nodes : Nodes to describe busses off the I2C
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/i2c/ |
| D | i2c-mux.yaml | 13 An i2c bus multiplexer/switch will have several child busses that are numbered
18 i2c child busses and other child nodes, the 'i2c-mux' subnode can be used for
19 populating the i2c child busses. If an 'i2c-mux' subnode is present, only
20 subnodes of this will be considered as i2c child busses.
|
| D | i2c-fsi.txt | 1 Device-tree bindings for FSI-attached I2C master and busses
11 - child nodes : Nodes to describe busses off the I2C
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/media/ |
| D | video-interfaces.yaml | 61 a device is partitioned into multiple data busses, e.g. 16-bit input port
62 divided into two separate ITU-R BT.656 8-bit busses. In such case bus-width
104 Number of data lines actively used, valid for the parallel busses.
110 On the parallel data busses, if bus-width is used to specify the number of
173 lane. This property is valid for serial busses only (e.g. MIPI CSI-2).
183 clock lane on hardware lane 0. This property is valid for serial busses
210 (normal). This property is valid for serial busses only.
|
| /kernel/linux/linux-5.10/drivers/i2c/muxes/ |
| D | Kconfig | 28 I2C busses connected through a MUX, which is controlled
41 I2C busses connected through a MUX, which in turn is controlled
96 I2C busses connected through a MUX, which is controlled
116 I2C busses connected through a MUX, which is controlled
|
| /kernel/linux/linux-6.6/drivers/i2c/muxes/ |
| D | Kconfig | 28 I2C busses connected through a MUX, which is controlled
41 I2C busses connected through a MUX, which in turn is controlled
96 I2C busses connected through a MUX, which is controlled
116 I2C busses connected through a MUX, which is controlled
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/net/ |
| D | mctp-i2c-controller.yaml | 17 slave functionality. I2C busses (either directly or as subordinate mux
18 busses) are attached to the mctp-i2c-controller with a 'mctp-controller'
56 // Mux topology with multiple MCTP-handling busses under
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/w1/ |
| D | w1.txt | 1 Generic devicetree bindings for onewire (w1) busses
4 Onewire busses are described through nodes of their master bus controller.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/w1/ |
| D | w1.txt | 1 Generic devicetree bindings for onewire (w1) busses
4 Onewire busses are described through nodes of their master bus controller.
|
| /kernel/linux/linux-6.6/drivers/i2c/busses/ |
| D | i2c-amd-mp2-pci.c | 212 i2c_common = privdata->busses[bus_id]; in amd_mp2_irq_isr()
256 if (privdata->busses[i2c_common->bus_id]) { in amd_mp2_register_cb()
261 privdata->busses[i2c_common->bus_id] = i2c_common; in amd_mp2_register_cb()
271 privdata->busses[i2c_common->bus_id] = NULL; in amd_mp2_unregister_cb()
395 i2c_common = privdata->busses[bus_id]; in amd_mp2_pci_suspend()
426 i2c_common = privdata->busses[bus_id]; in amd_mp2_pci_resume()
|
| D | i2c-amd-mp2.h | 172 * @busses: MP2 devices may have up to two busses,
181 struct amd_i2c_common *busses[2]; member
|
| /kernel/linux/linux-5.10/drivers/i2c/busses/ |
| D | i2c-amd-mp2-pci.c | 218 i2c_common = privdata->busses[bus_id]; in amd_mp2_irq_isr()
262 if (privdata->busses[i2c_common->bus_id]) { in amd_mp2_register_cb()
268 privdata->busses[i2c_common->bus_id] = i2c_common; in amd_mp2_register_cb()
278 privdata->busses[i2c_common->bus_id] = NULL; in amd_mp2_unregister_cb()
393 i2c_common = privdata->busses[bus_id]; in amd_mp2_pci_suspend()
426 i2c_common = privdata->busses[bus_id]; in amd_mp2_pci_resume()
|
| D | i2c-amd-mp2.h | 172 * @busses: MP2 devices may have up to two busses,
181 struct amd_i2c_common *busses[2]; member
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/ |
| D | mipi-dsi-bus.txt | 1 MIPI DSI (Display Serial Interface) busses
35 supporting such a configuration generally requires the data on both the busses
76 busses. Each DSI bus/channel drives some portion of the pixel data (generally
78 The graph bindings should be used to represent the multiple DSI busses that are
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/display/ |
| D | mipi-dsi-bus.txt | 1 MIPI DSI (Display Serial Interface) busses
35 supporting such a configuration generally requires the data on both the busses
76 busses. Each DSI bus/channel drives some portion of the pixel data (generally
78 The graph bindings should be used to represent the multiple DSI busses that are
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/interrupt-controller/ |
| D | msi.txt | 8 used with other busses, and hence a mechanism is required to relate devices on
9 those busses to the MSI controllers which they are capable of using,
73 When #msi-cells is non-zero, busses with an msi-parent will require
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/interrupt-controller/ |
| D | msi.txt | 8 used with other busses, and hence a mechanism is required to relate devices on
9 those busses to the MSI controllers which they are capable of using,
73 When #msi-cells is non-zero, busses with an msi-parent will require
|
| /kernel/linux/linux-6.6/Documentation/driver-api/media/ |
| D | tx-rx.rst | 15 The following busses are the most common. This section discusses these two only.
28 `BT.601`_ and `BT.656`_ are the most common parallel busses.
38 bus. These are common for both busses.
|
| /kernel/linux/linux-6.6/arch/alpha/include/asm/ |
| D | pci.h | 13 * The following structure is used to manage multiple PCI busses.
19 /* A controller. Used to manage multiple PCI busses. */
|
| /kernel/linux/linux-5.10/arch/alpha/include/asm/ |
| D | pci.h | 13 * The following structure is used to manage multiple PCI busses.
19 /* A controller. Used to manage multiple PCI busses. */
|
| /kernel/linux/linux-5.10/arch/parisc/include/asm/ |
| D | pci.h | 13 ** Newer platforms number the busses across PCI bus adapters *sparsely*.
148 * But legacy platforms also need to renumber the busses below a Host
156 * the busses rather than treat each Dino as a separate PCI domain.
|
| /kernel/linux/linux-6.6/arch/parisc/include/asm/ |
| D | pci.h | 13 ** Newer platforms number the busses across PCI bus adapters *sparsely*.
148 * But legacy platforms also need to renumber the busses below a Host
156 * the busses rather than treat each Dino as a separate PCI domain.
|