| /linux-4.4.14/drivers/i2c/muxes/ |
| D | i2c-mux-pinctrl.c | 35 struct i2c_adapter **busses; member
169 mux->busses = devm_kzalloc(&pdev->dev, in i2c_mux_pinctrl_probe()
170 sizeof(*mux->busses) * mux->pdata->bus_count, in i2c_mux_pinctrl_probe()
172 if (!mux->busses) { in i2c_mux_pinctrl_probe()
223 mux->busses[i] = i2c_add_mux_adapter(mux->parent, &pdev->dev, in i2c_mux_pinctrl_probe()
227 if (!mux->busses[i]) { in i2c_mux_pinctrl_probe()
238 i2c_del_mux_adapter(mux->busses[i - 1]); in i2c_mux_pinctrl_probe()
250 i2c_del_mux_adapter(mux->busses[i]); in i2c_mux_pinctrl_remove()
|
| D | Kconfig | 27 I2C busses connected through a MUX, which is controlled
69 I2C busses connected through a MUX, which is controlled
|
| /linux-4.4.14/drivers/net/phy/ |
| D | Kconfig | 181 Supports GPIO lib-based MDIO busses.
192 busses. It is required by the Octeon and ThunderX ethernet device
215 multiplexers which connect one of several child MDIO busses
216 to a parent bus. Switching between child busses is done by
226 several child MDIO busses to a parent bus. Child bus
236 The multiplexer connects one of several child MDIO busses to a
246 This module provides a driver for the Broadcom UniMAC MDIO busses.
256 This module provides a driver for the MDIO busses found in the
|
| /linux-4.4.14/drivers/net/can/softing/ |
| D | Kconfig | 7 Softing Gmbh CAN cards come with 1 or 2 physical busses.
14 controls the 2 busses on the card together.
|
| /linux-4.4.14/Documentation/devicetree/bindings/media/ |
| D | video-interfaces.txt | 53 a device is partitioned into multiple data busses, e.g. 16-bit input port
54 divided into two separate ITU-R BT.656 8-bit busses. In such case bus-width
79 - bus-width: number of data lines actively used, valid for the parallel busses.
80 - data-shift: on the parallel data busses, if bus-width is used to specify the
97 This property is valid for serial busses only (e.g. MIPI CSI-2).
102 serial busses only (e.g. MIPI CSI-2). Note that for the MIPI CSI-2 bus this
114 as 0 (normal). This property is valid for serial busses only.
|
| D | samsung-s5c73m3.txt | 5 data busses. The I2C bus is the main control bus and additionally the SPI bus
60 For more details see description of the SPI busses bindings
|
| /linux-4.4.14/Documentation/w1/ |
| D | 00-INDEX | 6 - Individual chips providing 1-wire busses.
|
| /linux-4.4.14/Documentation/devicetree/bindings/i2c/ |
| D | i2c.txt | 1 Generic device tree bindings for I2C busses
5 busses in a device tree.
|
| D | i2c-mux.txt | 3 An i2c bus multiplexer/switch will have several child busses that are
|
| /linux-4.4.14/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
|
| /linux-4.4.14/Documentation/w1/masters/ |
| D | 00-INDEX | 4 - The Maxim/Dallas Semiconductor DS2482 provides 1-wire busses.
|
| D | ds2482 | 19 one (DS2482-100) or eight (DS2482-800) 1-wire busses.
|
| /linux-4.4.14/drivers/i2c/ |
| D | Makefile | 10 obj-y += algos/ busses/ muxes/
|
| D | Kconfig | 98 source drivers/i2c/busses/Kconfig
|
| /linux-4.4.14/sound/aoa/soundbus/ |
| D | Kconfig | 14 This option enables support for Apple I2S busses.
|
| /linux-4.4.14/Documentation/devicetree/bindings/net/ |
| D | mdio-mux.txt | 3 An MDIO bus multiplexer/switch will have several child busses that are
33 pair of GPIO lines. Child busses 2 and 3 populated with 4
|
| D | mdio-mux-gpio.txt | 24 pair of GPIO lines. Child busses 2 and 3 populated with 4
|
| /linux-4.4.14/arch/powerpc/boot/dts/ |
| D | currituck.dts | 144 /* This drives busses 0 to 0xf */
181 /* This drives busses 0 to 0xf */
218 /* This drives busses 0 to 0xf */
|
| 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 */
|
| 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 */
|
| D | redwood.dts | 260 /* This drives busses 10 to 0x1f */
301 /* This drives busses 10 to 0x1f */
342 /* This drives busses 10 to 0x1f */
|
| D | icon.dts | 310 /* This drives busses 0 to 0xf */
340 /* This drives busses 0x10 to 0x1f */
381 /* This drives busses 0x20 to 0x2f */
|
| D | makalu.dts | 293 /* This drives busses 0x00 to 0x3f */
334 /* This drives busses 0x40 to 0x7f */
|
| D | canyonlands.dts | 447 /* This drives busses 0 to 0x3f */
478 /* This drives busses 40 to 0x7f */
520 /* This drives busses 80 to 0xbf */
|
| D | glacier.dts | 484 /* This drives busses 0 to 0x3f */
515 /* This drives busses 40 to 0x7f */
557 /* This drives busses 80 to 0xbf */
|
| D | kilauea.dts | 347 /* This drives busses 0x00 to 0x3f */
388 /* This drives busses 0x40 to 0x7f */
|
| D | haleakala.dts | 262 /* This drives busses 0x00 to 0x3f */
|
| D | bluestone.dts | 366 /* This drives busses 40 to 0x7f */
|
| /linux-4.4.14/Documentation/devicetree/bindings/spi/ |
| D | spi-bus.txt | 1 SPI (Serial Peripheral Interface) busses
3 SPI busses can be described with a node for the SPI master device
|
| /linux-4.4.14/Documentation/ |
| D | eisa.txt | 7 status as other much more mainstream busses such as PCI or USB. This
9 abstractions to manage busses, devices and drivers.
183 care must be taken when ripping out the EISA code, so other busses
|
| D | zorro.txt | 14 There are two types of Zorro busses, Zorro II and Zorro III:
|
| D | DMA-attributes.txt | 13 strictly order DMA from a device across all intervening busses and
|
| D | kernel-parameters.txt | 2793 assign-busses [X86] Always assign all PCI bus
|
| /linux-4.4.14/Documentation/devicetree/bindings/c6x/ |
| D | emifa.txt | 5 SoCs. This interface provides external busses with a number of chip selects.
|
| /linux-4.4.14/arch/powerpc/sysdev/ |
| D | ppc4xx_pci.c | 1928 int primary = 0, busses; in ppc4xx_pciex_port_setup_hose() local
1959 busses = hose->last_busno - hose->first_busno; /* This is off by 1 */ in ppc4xx_pciex_port_setup_hose()
1960 if (busses > MAX_PCIE_BUS_MAPPED) { in ppc4xx_pciex_port_setup_hose()
1961 busses = MAX_PCIE_BUS_MAPPED; in ppc4xx_pciex_port_setup_hose()
1962 hose->last_busno = hose->first_busno + busses; in ppc4xx_pciex_port_setup_hose()
1971 busses * 0x100000); in ppc4xx_pciex_port_setup_hose()
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/ |
| D | mipi-dsi-bus.txt | 1 MIPI DSI (Display Serial Interface) busses
|
| /linux-4.4.14/Documentation/x86/x86_64/ |
| D | boot-options.txt | 180 pci=assign-busses Assign busses
182 pci=lastbus=NUMBER Scan up to NUMBER busses, no matter what the mptable says.
|
| /linux-4.4.14/Documentation/scsi/ |
| D | scsi-parameters.txt | 105 scsi_mod.scan= [SCSI] sync (default) scans SCSI busses as they are
|
| D | aic7xxx.txt | 39 busses.
257 Definition: Global tag depth for all targets on all busses.
|
| D | aic79xx.txt | 77 SCB corruption on some PCI-33 busses.
260 Definition: Global tag depth for all targets on all busses.
|
| /linux-4.4.14/Documentation/acpi/ |
| D | enumeration.txt | 17 o Devices behind real busses where there is a connector resource
19 (standard UARTs are not busses so there is no struct uart_device).
25 The ACPI implementation enumerates devices behind busses (platform, SPI and
|
| /linux-4.4.14/drivers/bus/ |
| D | Kconfig | 115 Driver for transparent busses that don't need a real driver, but
|
| /linux-4.4.14/drivers/w1/slaves/ |
| D | Kconfig | 33 This is slower but useful when debugging chips and/or busses.
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | via686a | 37 For the I2C bus driver, see <file:Documentation/i2c/busses/i2c-viapro>
|
| /linux-4.4.14/Documentation/networking/ |
| D | phy.txt | 22 Since the PHYs are devices, and the management busses through which they are
23 accessed are, in fact, busses, the PHY Abstraction Layer treats them as such.
37 Different devices use different busses (though some share common interfaces).
|
| /linux-4.4.14/ |
| D | MAINTAINERS | 563 F: Documentation/i2c/busses/i2c-ali1563
564 F: drivers/i2c/busses/i2c-ali1563.c
1244 F: drivers/i2c/busses/i2c-lpc2k.c
1345 F: drivers/i2c/busses/i2c-nomadik.c
1446 F: drivers/i2c/busses/i2c-rk3x.c
1565 F: drivers/i2c/busses/i2c-st.c
1628 F: drivers/i2c/busses/i2c-stu300.c
1645 F: drivers/i2c/busses/i2c-uniphier*
1710 F: drivers/i2c/busses/i2c-wmt.c
1750 F: drivers/i2c/busses/i2c-cadence.c
[all …]
|
| /linux-4.4.14/Documentation/driver-model/ |
| D | overview.txt | 23 model includes a set of common attributes which all busses carry, and a set
|
| D | platform.txt | 5 is used to connect devices on busses with minimal infrastructure,
|
| /linux-4.4.14/Documentation/i2c/ |
| D | upgrading-clients | 94 the busses. This means that the driver .attach_adapter and
|
| /linux-4.4.14/Documentation/gpio/ |
| D | drivers-on-gpio.txt | 51 - i2c-gpio: drivers/i2c/busses/i2c-gpio.c is used to drive an I2C bus
|
| D | gpio-legacy.txt | 24 also "GPIO Expander" chips that connect using the I2C or SPI serial busses.
197 Some GPIO controllers must be accessed using message based busses like I2C
|
| /linux-4.4.14/drivers/parisc/ |
| D | Kconfig | 7 The VSC, GSC and HSC busses were used from the earliest 700-series
|
| /linux-4.4.14/Documentation/usb/ |
| D | hotplug.txt | 3 In hotpluggable busses like USB (and Cardbus PCI), end-users plug devices
|
| D | WUSB-Design-overview.txt | 66 other, so you could consider them different "busses". Initially this
|
| /linux-4.4.14/drivers/staging/unisys/Documentation/ |
| D | overview.txt | 19 present the virtual busses involved. Drivers in the 'visor*' driver set are
59 The visorbus driver handles the virtual busses on which all of the virtual
|
| /linux-4.4.14/Documentation/power/ |
| D | devices.txt | 261 (Or at least the control bus, for devices which use multiple busses.)
274 for every device before the next phase begins. Not all busses or classes
458 PCMCIA, MMC, USB, Firewire, SCSI, and even IDE are common examples of busses
640 Some busses define rules about what different suspend states mean. PCI
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | v4l2-framework.txt | 19 more I2C busses, but other busses can also be used. Such devices are
165 pci_bus_type is a global. For USB busses use usb_bus_type. */
228 v4l2_subdev pointer, for other busses you may have to use other methods.
237 i2c_get_clientdata(). For other busses something similar needs to be done.
|
| /linux-4.4.14/Documentation/devicetree/ |
| D | usage-model.txt | 26 hardware characteristics including data busses, interrupt lines, GPIO
35 incompatible, bindings for i2c busses that came about because the new
|
| /linux-4.4.14/drivers/ata/ |
| D | Kconfig | 644 Most IDE capable PowerMacs have IDE busses driven by a variant
646 most PowerMac models. Some models have multiple busses using
|
| /linux-4.4.14/Documentation/spi/ |
| D | spi-summary | 27 Unlike serial busses like USB or SMBus, even low level protocols for
187 those /sys/class entries are only useful to quickly identify busses.
|
| /linux-4.4.14/arch/ia64/ |
| D | Kconfig | 569 Real IA-64 machines all have PCI/PCI-X/PCI Express busses. Say Y
|
| /linux-4.4.14/drivers/i2c/busses/ |
| D | Kconfig | 1034 Documentation/i2c/busses/i2c-parport for details.
1195 This exposes the PowerNV platform i2c busses to the linux i2c layer,
|
| /linux-4.4.14/Documentation/PCI/ |
| D | pci-error-recovery.txt | 14 busses, as well as SERR and PERR errors. Some of the more advanced
|
| D | MSI-HOWTO.txt | 541 Some PCI bridges are not able to route MSIs between busses properly.
|
| /linux-4.4.14/Documentation/networking/dsa/ |
| D | dsa.txt | 201 For Ethernet switches which have both external and internal MDIO busses, the
|
| /linux-4.4.14/Documentation/nvdimm/ |
| D | nvdimm.txt | 286 does not preclude it. The infrastructure supports multiple busses and
|
| /linux-4.4.14/drivers/watchdog/ |
| D | Kconfig | 345 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
|
| /linux-4.4.14/drivers/scsi/ |
| D | Kconfig | 243 busses in parallel, leading to a significant speed-up.
|