Home
last modified time | relevance | path

Searched refs:busses (Results 1 – 64 of 64) sorted by relevance

/linux-4.1.27/drivers/i2c/muxes/
Di2c-mux-pinctrl.c35 struct i2c_adapter **busses; member
168 mux->busses = devm_kzalloc(&pdev->dev, in i2c_mux_pinctrl_probe()
169 sizeof(*mux->busses) * mux->pdata->bus_count, in i2c_mux_pinctrl_probe()
171 if (!mux->busses) { in i2c_mux_pinctrl_probe()
222 mux->busses[i] = i2c_add_mux_adapter(mux->parent, &pdev->dev, in i2c_mux_pinctrl_probe()
226 if (!mux->busses[i]) { in i2c_mux_pinctrl_probe()
237 i2c_del_mux_adapter(mux->busses[i - 1]); in i2c_mux_pinctrl_probe()
249 i2c_del_mux_adapter(mux->busses[i]); in i2c_mux_pinctrl_remove()
DKconfig26 I2C busses connected through a MUX, which is controlled
/linux-4.1.27/drivers/net/phy/
DKconfig144 Supports GPIO lib-based MDIO busses.
155 This module provides a driver for the Octeon MDIO busses.
180 multiplexers which connect one of several child MDIO busses
181 to a parent bus. Switching between child busses is done by
191 several child MDIO busses to a parent bus. Child bus
201 The multiplexer connects one of several child MDIO busses to a
211 This module provides a driver for the Broadcom UniMAC MDIO busses.
/linux-4.1.27/drivers/net/can/softing/
DKconfig7 Softing Gmbh CAN cards come with 1 or 2 physical busses.
14 controls the 2 busses on the card together.
/linux-4.1.27/Documentation/devicetree/bindings/media/
Dvideo-interfaces.txt53 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.
Dsamsung-s5c73m3.txt5 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.1.27/Documentation/w1/
D00-INDEX6 - Individual chips providing 1-wire busses.
/linux-4.1.27/sound/aoa/soundbus/
DKconfig14 This option enables support for Apple I2S busses.
/linux-4.1.27/Documentation/w1/masters/
D00-INDEX4 - The Maxim/Dallas Semiconductor DS2482 provides 1-wire busses.
Dds248219 one (DS2482-100) or eight (DS2482-800) 1-wire busses.
/linux-4.1.27/drivers/i2c/
DMakefile10 obj-y += algos/ busses/ muxes/
DKconfig98 source drivers/i2c/busses/Kconfig
/linux-4.1.27/Documentation/devicetree/bindings/net/
Dmdio-mux.txt3 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
Dmdio-mux-gpio.txt24 pair of GPIO lines. Child busses 2 and 3 populated with 4
/linux-4.1.27/Documentation/devicetree/bindings/i2c/
Di2c-mux.txt3 An i2c bus multiplexer/switch will have several child busses that are
/linux-4.1.27/arch/powerpc/boot/dts/
Dcurrituck.dts144 /* This drives busses 0 to 0xf */
181 /* This drives busses 0 to 0xf */
218 /* This drives busses 0 to 0xf */
Dakebono.dts272 /* 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 */
Dkatmai.dts300 /* 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 */
Dredwood.dts260 /* This drives busses 10 to 0x1f */
301 /* This drives busses 10 to 0x1f */
342 /* This drives busses 10 to 0x1f */
Dicon.dts310 /* This drives busses 0 to 0xf */
340 /* This drives busses 0x10 to 0x1f */
381 /* This drives busses 0x20 to 0x2f */
Dmakalu.dts293 /* This drives busses 0x00 to 0x3f */
334 /* This drives busses 0x40 to 0x7f */
Dglacier.dts484 /* This drives busses 0 to 0x3f */
515 /* This drives busses 40 to 0x7f */
557 /* This drives busses 80 to 0xbf */
Dcanyonlands.dts447 /* This drives busses 0 to 0x3f */
478 /* This drives busses 40 to 0x7f */
520 /* This drives busses 80 to 0xbf */
Dkilauea.dts347 /* This drives busses 0x00 to 0x3f */
388 /* This drives busses 0x40 to 0x7f */
Dhaleakala.dts262 /* This drives busses 0x00 to 0x3f */
Dbluestone.dts366 /* This drives busses 40 to 0x7f */
/linux-4.1.27/Documentation/devicetree/bindings/spi/
Dspi-bus.txt1 SPI (Serial Peripheral Interface) busses
3 SPI busses can be described with a node for the SPI master device
/linux-4.1.27/Documentation/
Deisa.txt7 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
Dzorro.txt14 There are two types of Zorro busses, Zorro II and Zorro III:
DDMA-attributes.txt13 strictly order DMA from a device across all intervening busses and
Dkernel-parameters.txt2716 assign-busses [X86] Always assign all PCI bus
/linux-4.1.27/Documentation/devicetree/bindings/c6x/
Demifa.txt5 SoCs. This interface provides external busses with a number of chip selects.
/linux-4.1.27/Documentation/acpi/
Denumeration.txt17 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.1.27/drivers/staging/i2o/
DREADME90 o Find the right way to associate drives/luns/busses
DKconfig79 provides access to the busses on the I2O controller. The main purpose
/linux-4.1.27/arch/powerpc/sysdev/
Dppc4xx_pci.c1928 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.1.27/Documentation/devicetree/bindings/mipi/dsi/
Dmipi-dsi-bus.txt1 MIPI DSI (Display Serial Interface) busses
/linux-4.1.27/Documentation/x86/x86_64/
Dboot-options.txt177 pci=assign-busses Assign busses
179 pci=lastbus=NUMBER Scan up to NUMBER busses, no matter what the mptable says.
/linux-4.1.27/drivers/bus/
DKconfig99 Driver for transparent busses that don't need a real driver, but
/linux-4.1.27/Documentation/scsi/
Dscsi-parameters.txt105 scsi_mod.scan= [SCSI] sync (default) scans SCSI busses as they are
Daic7xxx.txt39 busses.
257 Definition: Global tag depth for all targets on all busses.
Daic79xx.txt77 SCB corruption on some PCI-33 busses.
260 Definition: Global tag depth for all targets on all busses.
/linux-4.1.27/Documentation/hwmon/
Dvia686a37 For the I2C bus driver, see <file:Documentation/i2c/busses/i2c-viapro>
/linux-4.1.27/drivers/w1/slaves/
DKconfig33 This is slower but useful when debugging chips and/or busses.
/linux-4.1.27/
DMAINTAINERS555 F: Documentation/i2c/busses/i2c-ali1563
556 F: drivers/i2c/busses/i2c-ali1563.c
1273 F: drivers/i2c/busses/i2c-nomadik.c
1374 F: drivers/i2c/busses/i2c-rk3x.c
1482 F: drivers/i2c/busses/i2c-st.c
1534 F: drivers/i2c/busses/i2c-stu300.c
1602 F: drivers/i2c/busses/i2c-wmt.c
1633 F: drivers/i2c/busses/i2c-cadence.c
1805 F: drivers/i2c/busses/i2c-at91.c
2039 F: drivers/i2c/busses/i2c-bfin-twi.c
[all …]
/linux-4.1.27/Documentation/networking/
Dphy.txt22 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.1.27/Documentation/driver-model/
Doverview.txt23 model includes a set of common attributes which all busses carry, and a set
Dplatform.txt5 is used to connect devices on busses with minimal infrastructure,
/linux-4.1.27/Documentation/i2c/
Dupgrading-clients94 the busses. This means that the driver .attach_adapter and
/linux-4.1.27/Documentation/usb/
Dhotplug.txt3 In hotpluggable busses like USB (and Cardbus PCI), end-users plug devices
DWUSB-Design-overview.txt66 other, so you could consider them different "busses". Initially this
/linux-4.1.27/drivers/parisc/
DKconfig7 The VSC, GSC and HSC busses were used from the earliest 700-series
/linux-4.1.27/Documentation/power/
Ddevices.txt261 (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
451 PCMCIA, MMC, USB, Firewire, SCSI, and even IDE are common examples of busses
633 Some busses define rules about what different suspend states mean. PCI
/linux-4.1.27/Documentation/video4linux/
Dv4l2-framework.txt19 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.1.27/Documentation/devicetree/
Dusage-model.txt26 hardware characteristics including data busses, interrupt lines, GPIO
35 incompatible, bindings for i2c busses that came about because the new
/linux-4.1.27/drivers/ata/
DKconfig617 Most IDE capable PowerMacs have IDE busses driven by a variant
619 most PowerMac models. Some models have multiple busses using
/linux-4.1.27/Documentation/spi/
Dspi-summary27 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.1.27/arch/ia64/
DKconfig591 Real IA-64 machines all have PCI/PCI-X/PCI Express busses. Say Y
/linux-4.1.27/Documentation/gpio/
Dgpio-legacy.txt24 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.1.27/drivers/i2c/busses/
DKconfig978 Documentation/i2c/busses/i2c-parport for details.
1130 This exposes the PowerNV platform i2c busses to the linux i2c layer,
/linux-4.1.27/Documentation/PCI/
Dpci-error-recovery.txt14 busses, as well as SERR and PERR errors. Some of the more advanced
DMSI-HOWTO.txt541 Some PCI bridges are not able to route MSIs between busses properly.
/linux-4.1.27/drivers/watchdog/
DKconfig314 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
/linux-4.1.27/drivers/scsi/
DKconfig243 busses in parallel, leading to a significant speed-up.