| /linux/drivers/net/mdio/ |
| H A D | Kconfig | 29 This module provides a driver for the MDIO busses found in the
44 This module provides a driver for the MDIO busses found in the
75 This module provides a driver for the MDIO busses found in the
82 This module provides a driver for the Broadcom UniMAC MDIO busses.
95 Supports GPIO lib-based MDIO busses.
104 This module provides a driver for the MDIO busses found in the
209 multiplexers which connect one of several child MDIO busses
210 to a parent bus. Switching between child busses is done by
264 several child MDIO busses to a parent bus. Child bus
275 bus multiplexer connects one of several child MDIO busses to
[all …]
|
| /linux/Documentation/devicetree/bindings/i2c/ |
| H A 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.
|
| /linux/drivers/i2c/muxes/ |
| H A 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
|
| /linux/Documentation/devicetree/bindings/net/ |
| H A 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
|
| H A D | mdio-mux.yaml | 13 An MDIO bus multiplexer/switch will have several child busses that are
|
| /linux/Documentation/devicetree/bindings/w1/ |
| H A D | w1.txt | 1 Generic devicetree bindings for onewire (w1) busses
4 Onewire busses are described through nodes of their master bus controller.
|
| /linux/Documentation/devicetree/bindings/display/ |
| H A 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
|
| /linux/Documentation/devicetree/bindings/interrupt-controller/ |
| H A 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
|
| /linux/drivers/i2c/busses/ |
| H A D | i2c-amd-mp2.h | 172 * @busses: MP2 devices may have up to two busses,
181 struct amd_i2c_common *busses[2]; member
|
| /linux/arch/alpha/include/asm/ |
| H A D | pci.h | 13 * The following structure is used to manage multiple PCI busses.
19 /* A controller. Used to manage multiple PCI busses. */
|
| /linux/arch/parisc/include/asm/ |
| H A 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.
|
| /linux/arch/powerpc/include/asm/ |
| H A D | pmac_low_i2c.h | 37 /* multibus : device node holds multiple busses, bus number is
43 /* i2c busses in the system */
|
| /linux/include/linux/ |
| H A D | of_platform.h | 75 /* Platform devices and busses creation */
95 /* Platform devices and busses creation */
|
| /linux/Documentation/i2c/ |
| H A D | i2c-address-translators.rst | 22 - the address on the parent and child busses can be different
50 A, B and C are three physical I2C busses, electrically independent from
|
| /linux/Documentation/devicetree/bindings/fpga/ |
| H A D | fpga-region.yaml | 52 * The busses within the FPGA are split such that each region gets its own
70 will be used to gate the busses. Traffic to other regions is not affected.
75 own bridge and its own split of the busses in the FPGA.
105 region (PRR0-2) gets its own split of the busses that is independently gated by
|
| /linux/arch/powerpc/boot/dts/ |
| H A D | currituck.dts | 144 /* This drives busses 0 to 0xf */
181 /* This drives busses 0 to 0xf */
218 /* This drives busses 0 to 0xf */
|
| H A D | akebono.dts | 272 /* This drives busses 0 to 0xf */
312 /* This drives busses 0 to 0xf */
352 /* This drives busses 0 to 0xf */
392 /* This drives busses 0 to 0xf */
|
| H A D | katmai.dts | 300 /* This drives busses 0 to 0xf */
344 /* This drives busses 0x10 to 0x1f */
385 /* This drives busses 0x20 to 0x2f */
426 /* This drives busses 0x30 to 0x3f */
|
| /linux/drivers/i2c/ |
| H A D | Kconfig | 71 An ATR allows accessing multiple I2C busses from a single
100 source "drivers/i2c/busses/Kconfig"
|
| H A D | Makefile | 18 obj-y += algos/ busses/ muxes/
|
| /linux/sound/aoa/soundbus/ |
| H A D | Kconfig | 15 This option enables support for Apple I2S busses.
|
| /linux/include/linux/spi/ |
| H A D | spi_gpio.h | 11 * Use spi_board_info with these busses in the usual way.
|
| /linux/include/linux/platform_data/ |
| H A D | i2c-mux-gpio.h | 20 * @n_values: Number of multiplexer positions (busses to instantiate)
|
| /linux/arch/microblaze/kernel/ |
| H A D | dma.c | 7 * directly mapped busses.
|
| /linux/drivers/greybus/ |
| H A D | Kconfig | 10 phones, and can be tunneled over other busses in order to
|