| /linux/drivers/net/mdio/ |
| H A 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
|
| /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/Documentation/devicetree/bindings/media/ |
| H A 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
174 lane. This property is valid for serial busses only (e.g. MIPI CSI-2).
184 clock lane on hardware lane 0. This property is valid for serial busses
211 (normal). This property is valid for serial busses only.
|
| /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
|
| /linux/drivers/i2c/busses/ |
| H A 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()
|
| 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/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
|
| H A D | aspeed,ast2xxx-scu-ic.txt | 10 fires new interrupts for child busses
|
| /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/arch/powerpc/platforms/powermac/ |
| H A D | low_i2c.c | 12 * powermac that covers the various types of i2c busses used in Apple machines.
14 * banging busses found on older chipsets in earlier machines if we ever need
599 /* Probe keywest-i2c busses */ in kw_i2c_probe()
611 * nodes) might cause us to not create some busses that are in kw_i2c_probe()
613 * want to work around that by creating busses without a node in kw_i2c_probe()
915 * type as older device trees mix i2c busses and other things in smu_i2c_probe()
1453 * Initialize us: probe all i2c busses on the machine, instantiate
1454 * busses and platform functions as needed.
1465 /* Probe keywest-i2c busses */ in pmac_i2c_init()
1469 /* Probe PMU i2c busses */ in pmac_i2c_init()
[all …]
|
| /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/driver-api/ |
| H A D | eisa.rst | 11 status as other much more mainstream busses such as PCI or USB. This
13 abstractions to manage busses, devices and drivers.
208 care must be taken when ripping out the EISA code, so other busses
|
| /linux/Documentation/devicetree/bindings/fpga/ |
| H A D | fpga-region.yaml | 54 * The busses within the FPGA are split such that each region gets its own
72 will be used to gate the busses. Traffic to other regions is not affected.
77 own bridge and its own split of the busses in the FPGA.
107 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 */
|
| /linux/Documentation/arch/x86/x86_64/ |
| H A D | boot-options.rst | 205 pci=assign-busses
206 Assign busses
210 Scan up to NUMBER busses, no matter what the mptable says.
|
| /linux/drivers/i2c/ |
| H A D | Kconfig | 71 An ATR allows accessing multiple I2C busses from a single
100 source "drivers/i2c/busses/Kconfig"
|
| /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.
|