Home
last modified time | relevance | path

Searched refs:controllers (Results 1 – 200 of 369) sorted by relevance

12

/linux-4.1.27/arch/tile/kernel/
Dpci.c62 static struct pci_controller controllers[TILE_NUM_PCIE]; variable
195 controller = &controllers[i]; in tile_pci_init()
223 struct pci_controller *controller = &controllers[i]; in tile_pci_init()
295 if (pci_scan_flags[i] == 0 && controllers[i].ops != NULL) { in pcibios_init()
296 struct pci_controller *controller = &controllers[i]; in pcibios_init()
337 if (pci_scan_flags[i] == 0 && controllers[i].ops != NULL) { in pcibios_init()
338 struct pci_bus *root_bus = controllers[i].root_bus; in pcibios_init()
352 controllers[i].mem_resources[0] = in pcibios_init()
354 controllers[i].mem_resources[1] = in pcibios_init()
356 controllers[i].mem_resources[2] = in pcibios_init()
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/usb/
Dfsl-usb.txt1 Freescale SOC USB controllers
10 controllers, or "fsl-usb2-dr" for dual role USB controllers
11 or "fsl,mpc5121-usb2-dr" for dual role USB controllers of MPC5121.
14 - phy_type : For multi port host USB controllers, should be one of
15 "ulpi", or "serial". For dual role USB controllers, should be
19 fsl-usb2-mph compatible controllers. Either this property or
21 controllers.
23 fsl-usb2-mph compatible controllers. Either this property or
25 controllers.
27 controllers. Can be "host", "peripheral", or "otg". Default to
Dgeneric.txt4 - maximum-speed: tells USB controllers we want to work up to a certain
7 via DT, USB controllers should default to their maximum
9 - dr_mode: tells Dual-Role USB controllers that we want to work on a
12 passed via DT, USB DRD controllers should default to
Dbrcm,bcm3384-usb.txt1 * Broadcom USB controllers
11 - Figuring out which controllers are disabled on ASIC bondout variants
Dpxa-usb.txt1 PXA USB controllers
6 - compatible: Should be "marvell,pxa-ohci" for USB controllers
35 - compatible: Should be "marvell,pxa270-udc" for USB controllers
Datmel-usb.txt1 Atmel SOC USB controllers
6 - compatible: Should be "atmel,at91rm9200-ohci" for USB controllers
24 - compatible: Should be "atmel,at91sam9g45-ehci" for USB controllers
Dsamsung-usbphy.txt1 SAMSUNG USB-PHY controllers
7 usb controllers across Samsung SOCs.
70 controllers across Samsung SOCs.
Dci-hdrc-qcom.txt1 Qualcomm CI13xxx (Chipidea) USB controllers
Dusb-xhci.txt1 USB xHCI controllers
Dspear-usb.txt1 ST SPEAr SoC USB controllers:
Dusb-ohci.txt1 USB OHCI controllers
Dnvidia,tegra20-ehci.txt1 Tegra SOC USB controllers
Dci-hdrc-imx.txt1 * Freescale i.MX ci13xxx usb controllers
Dusb-ehci.txt1 USB EHCI controllers
/linux-4.1.27/Documentation/devicetree/bindings/rtc/
Ds3c-rtc.txt5 * "samsung,s3c2410-rtc" - for controllers compatible with s3c2410 rtc.
6 * "samsung,s3c2416-rtc" - for controllers compatible with s3c2416 rtc.
7 * "samsung,s3c2443-rtc" - for controllers compatible with s3c2443 rtc.
8 * "samsung,s3c6410-rtc" - for controllers compatible with s3c6410 rtc.
9 * "samsung,exynos3250-rtc" - for controllers compatible with exynos3250 rtc.
/linux-4.1.27/Documentation/cgroups/
Dunified-hierarchy.txt16 2-3. cgroup.controllers
34 can host any number of controllers. While this seems to provide a
38 type controllers such as freezer which can be useful in all
40 fact that controllers can't be moved around once hierarchies are
41 populated. Another issue is that all controllers bound to a hierarchy
45 In practice, these issues heavily limit which controllers can be put
48 the cpu and cpuacct controllers, make sense to put on the same
56 restricts how cgroup is used in general and what controllers can do.
62 of controllers which exist only to identify membership, which in turn
66 of hierarchies other controllers would be on, each controller has to
[all …]
/linux-4.1.27/Documentation/input/
Dxpad.txt1 xpad - Linux USB driver for Xbox compatible controllers
4 controllers. It has a long history and has enjoyed considerable usage
9 This only effects Original Xbox controllers. All later controller models
12 Rumble is supported on some models of Xbox 360 controllers but not of
13 Original Xbox controllers nor on Xbox One controllers. As of writing
35 unknown controllers.
93 All generations of Xbox controllers speak USB over the wire.
94 - Original Xbox controllers use a proprietary connector and require adapters.
95 - Wireless Xbox 360 controllers require a 'Xbox 360 Wireless Gaming Receiver
97 - Wired Xbox 360 controllers use standard USB connectors.
[all …]
/linux-4.1.27/drivers/dma/sh/
DKconfig21 Enable support for the Renesas SuperH DMA controllers.
31 Enable support for the Renesas SuperH DMA controllers.
46 Enable support for the Renesas SUDMAC controllers.
52 Enable support for the Renesas R-Car series DMA controllers.
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-bus-pci-drivers-ehci_hcd7 PCI-based EHCI USB controllers (i.e., high-speed USB-2.0
8 controllers) are often implemented along with a set of
9 "companion" full/low-speed USB-1.1 controllers. When a
35 Note: Some EHCI controllers do not have companions; they
38 mechanism will not work with such controllers. Also, it
Dsysfs-class-scsi_host7 Storage Control Unit embeds up to two 4-port controllers in
8 a single PCI device. The controllers are enumerated in order
19 feature of HP Smart Array RAID controllers using the hpsa
22 of a logical drive, bypassing the controllers firmware RAID
Dsysfs-class-uwb_rc7 Platform (UWB) radio controllers.
100 controllers beacon group.
107 The time (using the radio controllers internal 1 ms
/linux-4.1.27/drivers/ata/
DKconfig97 controllers.
195 This option adds support for ATA controllers with SFF
199 the dawn of time. Almost all PATA controllers have an
200 SFF interface. Many SATA controllers have an SFF interface
203 For users with exclusively modern controllers like AHCI,
211 comment "SFF controllers with custom DMA interface"
217 This option enables support for Pacific Digital ADMA controllers
250 This option adds support for SFF ATA controllers with BMDMA
252 de facto DMA interface for SFF controllers.
258 comment "SATA SFF controllers with BMDMA"
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/memory-controllers/
Drenesas-memory-controllers.txt1 DT bindings for Renesas R-Mobile and SH-Mobile memory controllers
4 Renesas R-Mobile and SH-Mobile SoCs contain one or more memory controllers.
5 These memory controllers differ from one SoC variant to another, and are called
13 As there exist no actual drivers for these controllers yet, these bindings
Dsynopsys.txt5 - reg: Base address and size of the controllers memory area
Dmvebu-sdram-controller.txt1 Device Tree bindings for MVEBU SDRAM controllers
/linux-4.1.27/Documentation/devicetree/bindings/serial/
Domap_serial.txt4 - compatible : should be "ti,omap2-uart" for OMAP2 controllers
5 - compatible : should be "ti,omap3-uart" for OMAP3 controllers
6 - compatible : should be "ti,omap4-uart" for OMAP4 controllers
/linux-4.1.27/drivers/net/can/spi/
DKconfig5 tristate "Microchip MCP251x SPI CAN controllers"
8 Driver for the Microchip MCP251x SPI CAN controllers.
/linux-4.1.27/Documentation/devicetree/bindings/gpio/
Dgpio-omap.txt5 - "ti,omap2-gpio" for OMAP2 controllers
6 - "ti,omap3-gpio" for OMAP3 controllers
7 - "ti,omap4-gpio" for OMAP4 controllers
D8xxx_gpio.txt1 GPIO controllers on MPC8xxx SoCs
3 This is for the non-QE/CPM/GUTs GPIO controllers as found on
Dgpio-msm.txt5 - "qcom,msm-gpio" for MSM controllers
Dgpio-sx150x.txt14 - interrupts: Interrupt specifier for the controllers interrupt.
Dgpio-adnp.txt7 - interrupts: Interrupt specifier for the controllers interrupt.
Dgpio-dsp-keystone.txt7 For example TCI6638K2K SoC has 8 DSP GPIO controllers:
Dgpio-max732x.txt34 - interrupts: Interrupt specifier for the controllers interrupt.
Drenesas,gpio-rcar.txt18 - interrupts: Interrupt specifier for the controllers interrupt.
/linux-4.1.27/Documentation/devicetree/bindings/mmc/
Dexynos-dw-mshc.txt13 - "samsung,exynos4210-dw-mshc": for controllers with Samsung Exynos4210
15 - "samsung,exynos4412-dw-mshc": for controllers with Samsung Exynos4412
17 - "samsung,exynos5250-dw-mshc": for controllers with Samsung Exynos5250
19 - "samsung,exynos5420-dw-mshc": for controllers with Samsung Exynos5420
21 - "samsung,exynos7-dw-mshc": for controllers with Samsung Exynos7
23 - "samsung,exynos7-dw-mshc-smu": for controllers with Samsung Exynos7
Dti-omap-hsmmc.txt11 Should be "ti,omap2-hsmmc", for OMAP2 controllers
12 Should be "ti,omap3-hsmmc", for OMAP3 controllers
13 Should be "ti,omap3-pre-es3-hsmmc" for OMAP3 controllers pre ES3.0
14 Should be "ti,omap4-hsmmc", for OMAP4 controllers
15 Should be "ti,am33xx-hsmmc", for AM335x controllers
Dsamsung-sdhci.txt10 - "samsung,s3c6410-sdhci": For controllers compatible with s3c6410 sdhci
12 - "samsung,exynos4210-sdhci": For controllers compatible with Exynos4 sdhci
Dti-omap.txt13 - compatible: Must be "ti,omap2420-mmc", for OMAP2420 controllers
40 - compatible: Must be "ti,omap2420-mmc", for OMAP2420 controllers
Dk3-dw-mshc.txt15 - "hisilicon,hi4511-dw-mshc": for controllers with hi4511 specific extensions.
Dmmc.txt1 These properties are common to multiple MMC host controllers. Any host
46 *NOTE* on CD and WP polarity. To use common for all SD/MMC host controllers line
/linux-4.1.27/drivers/scsi/megaraid/
DKconfig.megaraid12 RAID controllers.
21 List of supported controllers
73 RAID controllers
82 Module for LSI Logic's SAS based RAID controllers.
/linux-4.1.27/Documentation/devicetree/bindings/sound/
Dmxs-audio-sgtl5000.txt6 - saif-controllers: The phandle list of the MXS SAIF controller
15 saif-controllers = <&saif0 &saif1>;
/linux-4.1.27/drivers/hsi/controllers/
DKconfig2 # HSI controllers configuration
4 comment "HSI controllers"
/linux-4.1.27/Documentation/devicetree/bindings/input/
Dtwl4030-pwrbutton.txt10 - "ti,twl4030-pwrbutton": For controllers compatible with twl4030
12 - <8>: For controllers compatible with twl4030
Dtwl4030-keypad.txt16 - "ti,twl4030-keypad": For controllers compatible with twl4030 keypad
19 - <1>: For controllers compatible with twl4030 keypad controller.
Dtps65218-pwrbutton.txt8 - <3 IRQ_TYPE_EDGE_BOTH>: For controllers compatible with tps65218
Dsamsung-keypad.txt11 - "samsung,s3c6410-keypad": For controllers compatible with s3c6410 keypad
13 - "samsung,s5pv210-keypad": For controllers compatible with s5pv210 keypad
Domap-keypad.txt16 - "ti,omap4-keypad": For controllers compatible with omap4 keypad
/linux-4.1.27/drivers/pinctrl/bcm/
DKconfig33 The Broadcom Cygnus SoC has 3 GPIO controllers including the ASIU
35 the always-ON GPIO controller (CRMU/AON). All 3 GPIO controllers are
38 All 3 Cygnus GPIO controllers support basic PINCONF functions such
/linux-4.1.27/Documentation/devicetree/bindings/pci/
Dpci-rcar-gen2.txt4 This is the bridge used internally to connect the USB controllers to the
6 OHCI and EHCI controllers.
12 the operational registers for the OHCI/EHCI controllers and the
/linux-4.1.27/drivers/gpu/drm/armada/
DKconfig10 Support the "LCD" controllers found on the Marvell Armada 510
11 devices. There are two controllers on the device, each controller
/linux-4.1.27/arch/arm/mach-omap2/
Dhsmmc.c485 void __init omap_hsmmc_init(struct omap2_hsmmc_info *controllers) in omap_hsmmc_init() argument
500 for (; controllers->mmc; controllers++) in omap_hsmmc_init()
501 omap_hsmmc_init_one(controllers, controllers->mmc); in omap_hsmmc_init()
/linux-4.1.27/Documentation/devicetree/bindings/net/can/
Dgrcan.txt1 Aeroflex Gaisler GRCAN and GRHCAN CAN controllers.
3 The GRCAN and CRHCAN CAN controllers are available in the GRLIB VHDL IP core
Dxilinx_can.txt6 controllers and "xlnx,axi-can-1.00.a" for Axi CAN
7 controllers.
Dc_can.txt5 - compatible : Should be "bosch,c_can" for C_CAN controllers and
6 "bosch,d_can" for D_CAN controllers.
Dm_can.txt5 - compatible : Should be "bosch,m_can" for M_CAN controllers
/linux-4.1.27/drivers/usb/
DREADME14 * Chip specifications for USB controllers. Examples include
15 host controllers (on PCs, servers, and more); peripheral
16 controllers (in devices with Linux firmware, like printers or
/linux-4.1.27/Documentation/usb/
Dmtouchusb.txt18 All controllers have the Vendor: 0x0596 & Product: 0x0001
50 controllers.
71 A huge thank you to 3M Touch Systems for the EXII-5010UC controllers for
Dohci.txt9 hardware register protocols used to talk to USB 1.1 host controllers. As
11 Intel, it pushes more intelligence into the hardware. USB 1.1 controllers
/linux-4.1.27/drivers/uwb/
DKconfig19 Say Y here if your computer has UWB radio controllers (USB or PCI)
20 based. You will need to enable the radio controllers
51 radio/host controllers connected via memory mapping (eg:
/linux-4.1.27/Documentation/devicetree/bindings/interrupt-controller/
Dsamsung,s3c24xx-irq.txt3 The S3C24XX SoCs contain a custom set of interrupt controllers providing a
26 ignored in main controllers
Dmarvell,orion-intc.txt1 Marvell Orion SoC interrupt controllers
Dnvidia,tegra-ictlr.txt7 The HW block exposes a number of interrupt controllers, each
/linux-4.1.27/Documentation/devicetree/bindings/arm/
Dversatile-fpga-irq.txt3 One or more FPGA IRQ controllers can be synthesized in an ARM reference board
5 controllers are OR:ed together and fed to the CPU tile's IRQ input. Each
Dvic.txt4 system for interrupt routing. For multiple controllers they can either be
20 - interrupts : Interrupt source for parent controllers if the VIC is nested.
Dspear-misc.txt4 few properties of different peripheral controllers.
Dvexpress.txt77 The controllers are responsible for the platform initialization
83 The controllers are not mapped into normal memory address space
87 The nodes describing configuration controllers must define
144 - I2C controllers:
Dlpc32xx-mic.txt2 (MIC, including SIC1 and SIC2 secondary controllers)
Darm-boards10 FPGA type interrupt controllers, see the versatile-fpga-irq binding doc.
79 Interrupt controllers:
/linux-4.1.27/drivers/hsi/
DMakefile6 obj-y += controllers/
DKconfig17 source "drivers/hsi/controllers/Kconfig"
/linux-4.1.27/Documentation/devicetree/bindings/arm/samsung/
Dexynos-adc.txt14 for exynos4412/5250 and s5pv210 controllers.
16 future controllers.
18 controllers compatible with ADC of Exynos3250.
/linux-4.1.27/Documentation/scsi/
Dmegaraid.txt7 Different classes of controllers from LSI Logic accept and respond to the
10 the controllers uniformly. Hence it is logical to have a single module that
39 your new MPT-based RAID controllers and your existing megaraid driver,
DChangeLog.megaraid_sas50 6. Add support for MegaRAID Fury (device ID-0x005f) 12Gb/s controllers.
53 controllers.
121 7. Add support for MegaRAID 9360/9380 12GB/s controllers.
190 6. Add code to support MegaRAID 9265/9285 controllers device id (0x5b).
327 Those controllers are LSI's next generatation(gen2) SAS controllers.
399 (max_sectors_1, max_sectors_2). For certain controllers/FW,
602 xscale controllers.
622 i. New template defined to represent each family of controllers (identified by processor used).
623 …controllers. The template definition has four function pointers. During driver initialisation the …
Daic7xxx.txt40 2. Multi-function Twin Channel Device - Two controllers on one chip.
210 Definition: Do not probe for EISA/VLB controllers.
212 to not probe EISA/VLB controllers by default,
215 controllers by default, specifying "no_probe"
266 per controller basis. Both controllers and targets
306 Default Value: SCSI-Select setting on controllers with a SCSI Select
307 option for DV. Otherwise, on for controllers supporting
D00-INDEX38 - Driver supporting Adaptec RAID controllers
46 - info on driver for Adaptec controllers
Dncr53c8xx.txt74 16.1 Synchronous timings for 53C875 and 53C860 Ultra-SCSI controllers
75 16.2 Synchronous timings for fast SCSI-2 53C8XX controllers
602 For example, Tekram DC-390/U, DC-390/W and DC-390/F scsi controllers
680 Only apply to 810A, 825A, 860, 875 and 895 controllers.
690 Only apply to 860, 875, 895, 895a, 896, 1010 and 1010_66 controllers.
709 - all other logical units (all targets, all controllers) -> 10 commands.
720 controllers according to NCR53C8XX chip type.
810 nvram:y test controllers for onboard serial NVRAM
817 0x80 also attach controllers set to OFF in the NVRAM (sym53c8xx only)
927 Optimized PCI accesses may be broken for some PCI/memory controllers or
[all …]
Daacraid.txt6 RAID controllers. This is a major rewrite from the original
127 …ds (non-DASD support, PAE fibs and 64 bit, added new adaptec controllers
Dhpsa.txt5 This file describes the hpsa SCSI driver for HP Smart Array controllers.
7 Smart Array controllers. The hpsa driver is a SCSI driver, while the
/linux-4.1.27/Documentation/xtensa/
Datomctl.txt22 use the memory controllers RCW, thought non-MX controlers likely
26 Virtually all customers buy their memory controllers from vendors that
/linux-4.1.27/Documentation/devicetree/bindings/net/
Dhisilicon-hip04-net.txt22 Control rx & tx fifos of all ethernet controllers.
23 Have 2048 recv channels shared by all ethernet controllers, only if no overlap.
Dvia-rhine.txt5 Rhine controllers found in VIA VT8500, WonderMedia WM8950
Dmdio-gpio.txt6 MDC and MDIO lines connected to GPIO controllers are listed in the
Dmarvell-orion-net.txt14 Note: The above separation is only true for Discovery system controllers.
17 controllers. As Kirkwood has some issues with proper initialization after reset,
Dmarvell-orion-mdio.txt3 The Ethernet controllers of the Marvel Kirkwood, Dove, Orion5x,
Dgpmc-eth.txt5 such as ethernet controllers to processors using the TI GPMC as a data bus.
7 Ethernet controllers connected to TI GPMC are represented as child nodes of
Dethernet.txt1 The following properties are common to the Ethernet controllers:
/linux-4.1.27/drivers/message/fusion/
DKconfig21 List of supported controllers:
36 List of supported controllers:
55 List of supported controllers:
/linux-4.1.27/drivers/usb/dwc2/
DKconfig12 controllers directly connected to the CPU) will be called
58 controllers directly connected to the CPU.
67 The Designware USB2.0 PCI interface module for controllers
/linux-4.1.27/drivers/scsi/esas2r/
DKconfig5 This driver supports the ATTO ExpressSAS R6xx SAS/SATA RAID controllers.
/linux-4.1.27/drivers/usb/gadget/udc/
DKconfig10 # - Some systems have both kinds of controllers.
19 # The order here is alphabetical, except that integrated controllers go
21 # - integrated/SOC controllers first
23 # - discrete ones (including all PCI-only controllers)
29 # Integrated controllers
119 speed USB device controllers, with support for up to 30
121 controller in the OMAP 1611, and should work with controllers
248 # Controllers available only in discrete form (and all PCI controllers)
273 controllers having QE or CPM2, given minor tweaks.
327 The Toshiba TC86C001 is a PCI device which includes controllers
/linux-4.1.27/Documentation/mtd/
Dspi-nor.txt7 SPI bus controllers (drivers/spi/) only deal with streams of bytes; the bus
9 controllers (such as Freescale's QuadSPI controller) cannot easily handle
/linux-4.1.27/Documentation/
DIRQ-domain.txt6 systems with multiple interrupt controllers the kernel must ensure
10 The number of interrupt controllers registered as unique irqchips
12 such as GPIO controllers avoid reimplementing identical callback
14 handlers as irqchips, i.e. in effect cascading interrupt controllers.
133 supported. For example, ISA controllers would use the legacy map for
155 On some architectures, there may be multiple interrupt controllers
161 There are three interrupt controllers involved:
Dhsi.txt41 The hsi subsystem contains drivers for hsi controllers including support for
42 multi-port controllers and provides a generic API for using the HSI ports.
Ddebugging-via-ohci1394.txt2 Using physical DMA provided by OHCI-1394 FireWire controllers for debugging
8 Basically all FireWire controllers which are in use today are compliant
25 With most FireWire controllers, memory access is limited to the low 4 GB
30 At least LSI FW643e and FW643e2 controllers are known to support access to
DIRQ.txt17 controllers.
/linux-4.1.27/drivers/devfreq/
DKconfig77 It reads PPMU counters of memory controllers and adjusts
88 It reads PPMU counters of memory controllers and adjusts the
98 It reads ACTMON counters of memory controllers and adjusts the
/linux-4.1.27/Documentation/devicetree/bindings/clock/
Dpistachio-clock.txt1 Imagination Technologies Pistachio SoC clock controllers
4 Pistachio has four clock controllers (core clock, peripheral clock, peripheral
11 There are three external inputs to the clock controllers which should be
Dexynos7-clock.txt4 independently from the device-tree. These clock controllers
24 - compatible: clock controllers will use one of the following
Dhi3620-clock.txt4 controllers within the Hi3620 SoC.
Dmarvell,mmp2.txt4 controllers within the MMP2 SoC.
Dmarvell,pxa168.txt4 controllers within the PXA168 SoC.
Dhix5hd2-clock.txt4 controllers within the hix5hd2 SoC.
Dexynos5440-clock.txt4 controllers within the Exynos5440 SoC.
Dmarvell,pxa910.txt4 controllers within the PXA910 SoC.
Dexynos5250-clock.txt4 controllers within the Exynos5250 SoC.
Dexynos5410-clock.txt4 controllers within the Exynos5410 SoC.
Dexynos5420-clock.txt4 controllers within the Exynos5420 SoC and for the Exynos5800 SoC.
Dexynos5260-clock.txt3 Exynos5260 has 13 clock controllers which are instantiated
4 independently from the device-tree. These clock controllers
Dexynos4-clock.txt3 The Exynos4 clock controller generates and supplies clock to various controllers
Dexynos3250-clock.txt4 controllers within the Exynos3250 SoC.
Dsamsung,s3c2412-clock.txt3 The S3C2412 clock controller generates and supplies clock to various controllers
Dsamsung,s3c2410-clock.txt3 The S3C2410 clock controller generates and supplies clock to various controllers
Drockchip,rk3288-cru.txt4 controllers within the SoC and also implements a reset controller for SoC
Dsamsung,s3c2443-clock.txt3 The S3C2443 clock controller generates and supplies clock to various controllers
Drockchip,rk3188-cru.txt4 controllers within the SoC and also implements a reset controller for SoC
Dsamsung,s5pv210-clock.txt4 controller, which generates and supplies clock to various controllers
Dsamsung,s3c64xx-clock.txt3 The S3C64xx clock controller generates and supplies clock to various controllers
/linux-4.1.27/Documentation/devicetree/bindings/arm/omap/
Dcounter.txt4 - compatible: Must be "ti,omap-counter32k" for OMAP controllers
Ddmm.txt4 SDRAM controllers (called EMIFs on OMAP). DMM manages various aspects of memory
Dcrossbar.txt5 In such places a interrupt controllers are preceded by an CROSSBAR
/linux-4.1.27/Documentation/devicetree/bindings/spi/
Dspi-orion.txt6 - cell-index : Which of multiple SPI controllers is this.
Dspi-meson.txt1 Amlogic Meson SPI controllers
Dspi-bus.txt6 SPI master mode. This binding does not describe SPI controllers
65 Some SPI controllers and devices support Dual and Quad SPI transfer mode.
Dspi-rockchip.txt4 and display controllers using the SPI communication interface.
/linux-4.1.27/sound/usb/
DKconfig44 interfaces or controllers US-122, US-224 and US-428.
77 bool "enable input device for controllers"
81 Say Y here to support input controllers like buttons, knobs,
/linux-4.1.27/drivers/mmc/card/
DKconfig42 controllers, however, are restricted to continuous memory
65 in host controllers. The tests are executed by writing to the
/linux-4.1.27/Documentation/devicetree/bindings/input/touchscreen/
Dpixcir_i2c_ts.txt1 * Pixcir I2C touchscreen controllers
/linux-4.1.27/Documentation/devicetree/bindings/phy/
Dqcom-ipq806x-sata-phy.txt4 SATA PHY nodes are defined to describe on-chip SATA Physical layer controllers.
Dqcom-apq8064-sata-phy.txt4 SATA PHY nodes are defined to describe on-chip SATA Physical layer controllers.
Dsamsung-phy.txt87 SATA PHY nodes are defined to describe on-chip SATA Physical layer controllers.
168 - aliases: For SoCs like Exynos5420 having multiple USB 3.0 DRD PHY controllers,
171 controllers).
Dphy-stih407-usb.txt4 host controllers (when controlling usb2/1.1 devices) available on STiH407 SoC family from STMicroel…
Dqcom-dwc3-usb-phy.txt5 controllers. Each DWC3 PHY controller should have its own node.
Dphy-mvebu.txt29 features of both USB controllers.
/linux-4.1.27/Documentation/devicetree/bindings/timer/
Dsamsung,exynos4210-mct.txt51 interrupt controllers. Hence, an interrupt-map is created to map
52 the interrupts to the respective interrupt controllers.
/linux-4.1.27/Documentation/devicetree/bindings/power/
Dpower_domain.txt19 providing multiple PM domains (e.g. power controllers), but can be any value
58 The nodes above define two power controllers: 'parent' and 'child'.
/linux-4.1.27/drivers/pinctrl/
DKconfig10 menu "Pin controllers"
14 bool "Support pin multiplexing controllers" if COMPILE_TEST
17 bool "Support pin configuration controllers" if COMPILE_TEST
/linux-4.1.27/drivers/staging/i2o/
DKconfig33 loop. On all other controllers say Y.
41 Say Y for support of raidutils for Adaptec I2O controllers. You also
51 controllers.
/linux-4.1.27/drivers/ide/
DKconfig51 There are two drivers for Serial ATA controllers.
54 and supports most modern SATA controllers. In order to use it
59 a few first-generation SATA controllers.
64 supports SATA controllers, and this (IDE) driver supports
65 PATA controllers.
213 controllers sharing those IRQs which usually makes drivers
214 for those controllers fail. Generally, it's not a good idea
300 Normally, IDE controllers built into the motherboard (on-board
301 controllers) are assigned to ide0 and ide1 while those on add-in PCI
302 cards (off-board controllers) are relegated to ide2 and ide3.
[all …]
/linux-4.1.27/sound/oss/
Dsound_config.h95 unsigned char controllers[128]; member
Dsequencer.c564 synth_devs[dev]->chn_info[chn].controllers[p1] = w14 & 0x7f; in seq_chn_common_event()
567 synth_devs[dev]->chn_info[chn].controllers[p1 + 32] = 0; in seq_chn_common_event()
577 chn_info[chn].controllers[p1 & ~32] & 0x7f) << 7) in seq_chn_common_event()
579 chn_info[chn].controllers[p1 | 32] & 0x7f); in seq_chn_common_event()
933 synth_devs[dev]->chn_info[chn].controllers,0); in setup_mode2()
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/
Dserial.txt10 Modem control lines connected to GPIO controllers are listed in the gpios
/linux-4.1.27/arch/powerpc/sysdev/
DKconfig36 bool "Expose SCOM controllers via debugfs"
/linux-4.1.27/Documentation/devicetree/bindings/ata/
Dfsl-sata.txt3 SATA nodes are defined to describe on-chip Serial ATA controllers.
Dexynos-sata.txt3 SATA nodes are defined to describe on-chip Serial ATA controllers.
Dqcom-sata.txt3 SATA nodes are defined to describe on-chip Serial ATA controllers.
Dsata_highbank.txt3 SATA nodes are defined to describe on-chip Serial ATA controllers.
Dapm-xgene.txt4 controllers. Each SATA controller (pair of ports) have its own node.
Dahci-platform.txt3 SATA nodes are defined to describe on-chip Serial ATA controllers.
/linux-4.1.27/include/linux/
Dagpgart.h124 struct agp_controller *controllers; member
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/
Dsrio-rmu.txt3 For SRIO controllers that implement the message unit as part of the controller
36 correspond to the actual sub-controllers in the RMU. The manual for a given
37 SoC will detail which and how many of these sub-controllers are implemented.
Dpamu.txt17 physically present PAMU controllers. For example, for
57 be set to the size of this PAMU controllers's register space.
/linux-4.1.27/Documentation/i2c/busses/
Di2c-ismt29 The S12xx series of SOCs have a pair of integrated SMBus 2.0 controllers
Dscx200_acb11 Base addresses for the ACCESS.bus controllers on SCx200 and SC1100 devices
/linux-4.1.27/drivers/misc/c2port/
DKconfig12 If your board have no such micro controllers you don't need this
/linux-4.1.27/drivers/char/agp/
Dfrontend.c297 controller = agp_fe.controllers; in agp_find_controller_by_pid()
324 prev_controller = agp_fe.controllers; in agp_insert_controller()
330 agp_fe.controllers = controller; in agp_insert_controller()
389 agp_fe.controllers = next_controller; in agp_remove_controller()
477 controller = agp_fe.controllers; in agp_find_controller_for_client()
/linux-4.1.27/arch/arm/boot/dts/
Ds3c6400.dtsi10 * Note: This file does not include device nodes for all the controllers in
Dexynos4212.dtsi11 * Note: This file does not include device nodes for all the controllers in
Ds3c6410.dtsi10 * Note: This file does not include device nodes for all the controllers in
Dexynos4412.dtsi11 * Note: This file does not include device nodes for all the controllers in
/linux-4.1.27/Documentation/devicetree/bindings/pinctrl/
Dpinctrl-bindings.txt5 controllers. Each pin controller must be represented as a node in device tree,
12 For a client device to operate correctly, certain pin controllers must
24 Note that pin controllers themselves may also be client devices of themselves.
51 controllers may be configured, or so that a state may be built
/linux-4.1.27/Documentation/devicetree/bindings/c6x/
Dclocks.txt4 This is a first-cut support for the SoC clock controllers. This is still
/linux-4.1.27/Documentation/devicetree/bindings/dma/
Dnbpfaxi.txt1 * Renesas "Type-AXI" NBPFAXI* DMA controllers
Ddma.txt68 2. A single read-write channel with three alternative DMA controllers:
/linux-4.1.27/Documentation/devicetree/bindings/spmi/
Dspmi.txt3 This document defines a generic set of bindings for use by SPMI controllers. A
/linux-4.1.27/Documentation/hwmon/
Dadm103124 The ADM1030 and ADM1031 are digital temperature sensors and fan controllers.
Dzl610064 compatible digital DC-DC controllers.
99 Intersil/Zilker Labs DC-DC controllers require a minimum interval between I2C
Dltc426117 The LTC4261/LTC4261-2 negative voltage Hot Swap controllers allow a board
/linux-4.1.27/drivers/scsi/aic7xxx/
DKconfig.aic7xxx11 based SCSI controllers as well as the aic7770 based EISA and VLB
12 SCSI controllers (the 274x and 284x series). For AAA and ARO based
/linux-4.1.27/arch/mips/sgi-ip27/
DTODO5 Qlogic scsi controllers.
/linux-4.1.27/drivers/net/ethernet/sfc/
DKconfig12 controllers.
/linux-4.1.27/Documentation/devicetree/bindings/mfd/
Dsun6i-prcm.txt4 (like clks and reset controllers).
/linux-4.1.27/arch/mips/alchemy/
DKconfig1 # au1000-style gpio and interrupt controllers
/linux-4.1.27/Documentation/blockdev/
DREADME.DAC96020 controllers. Mylex Corporation is located at 34551 Ardenwood Blvd., Fremont,
30 driver supports all current Mylex PCI RAID controllers including the new
48 regarding installation and configuration of the controllers. This document
54 The DAC960 RAID controllers are supported solely as high performance RAID
55 controllers, not as interfaces to arbitrary SCSI devices. The Linux DAC960
57 drivers. Unlike other RAID controllers currently supported on Linux, the
67 The DAC960 driver is architected to support up to 8 controllers per system.
188 3.51-0-04 or above is required (for dual Flash ROM controllers), or firmware
189 version 2.73-0-00 or above is required (for single Flash ROM controllers)
192 controllers, and only particular firmware versions of any given model may
[all …]
Dcpqarray.txt37 controllers, in EISA slots 1 and 2 you'd give it a boot argument like
/linux-4.1.27/Documentation/block/
Ddata-integrity.txt21 Current storage controllers and devices implement various protective
35 controller and storage device. However, many controllers actually
39 controllers.
59 performance for a number of workloads. Some controllers allow a
82 to be pinned to I/Os and sent to/received from controllers that
/linux-4.1.27/drivers/usb/host/
DKconfig10 host/peripheral/OTG USB controllers.
63 EHCI controllers are packaged with "companion" host controllers (OHCI
218 found in NVIDIA Tegra SoCs. The controllers are EHCI compliant.
318 implement OTG nor USB device controllers.
326 The ISP1160 and ISP1161 chips are USB host controllers. Enable this
487 Enables support for big-endian USB controllers present on the
495 Enables support for little-endian USB controllers present on the
504 tristate "OHCI support for PCI-bus USB controllers"
644 For those PC cards that contain multiple OHCI controllers only the
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/qe/
Dpar_io.txt34 - gpio-controller : node to identify gpio controllers.
/linux-4.1.27/drivers/net/ethernet/arc/
DKconfig39 Support for Rockchip RK3066/RK3188 EMAC ethernet controllers.
/linux-4.1.27/drivers/net/ethernet/ibm/emac/
DKconfig6 This driver supports the IBM EMAC family of Ethernet controllers
/linux-4.1.27/Documentation/devicetree/bindings/reset/
Dst,sti-softreset.txt5 disable on-chip peripheral controllers such as USB and SATA, using
Dst,sti-powerdown.txt5 disable on-chip peripheral controllers such as USB and SATA, using
/linux-4.1.27/drivers/usb/phy/
DKconfig97 Provides simple GPIO VBUS sensing for controllers with an
214 controllers with a viewport register (e.g. Chipidea/ARC controllers).
/linux-4.1.27/drivers/mmc/host/
DKconfig44 and Toshiba(R). Most controllers found in laptops are of this type.
77 Most controllers found today are PCI devices.
98 tristate "SDHCI support for ACPI enumerated SDHCI controllers"
101 This selects support for ACPI enumerated SDHCI controllers,
121 tristate "SDHCI OF support for the Arasan SDHCI controllers"
145 tristate "SDHCI OF support for the Nintendo Wii SDHCI controllers"
452 SoC controllers.
482 controllers.
732 Note: These controllers only support SDIO cards and do not
/linux-4.1.27/Documentation/gpio/
Dgpio-legacy.txt37 cases (to support bidirectional signaling). GPIO controllers may have
105 uses numbers 0..63 with one set of GPIO controllers, 64-79 with another
121 Whether a platform supports multiple GPIO controllers is a platform-specific
123 of GPIO numbers, and whether new controllers can be added at runtime. Such issues
162 Most GPIO controllers can be accessed with memory read/write instructions.
197 Some GPIO controllers must be accessed using message based busses like I2C
423 Some GPIO controllers directly support open drain outputs; many don't. When
442 GPIO controllers and the pinctrl subsystem
522 will be found there. That will list all the controllers registered through
600 For external GPIO controllers -- such as I2C or SPI expanders, ASICs, multi
[all …]
/linux-4.1.27/Documentation/i2c/
Dslave-interface6 Linux can also be an I2C slave in case I2C controllers have slave support.
149 while the I2C specification is more loose on that. Most I2C controllers also
158 all I2C controllers have the possibility to report that event.
/linux-4.1.27/drivers/staging/nvec/
DKconfig38 nVidia compliant embedded controllers.
/linux-4.1.27/drivers/usb/misc/sisusbvga/
DKconfig11 work with USB 1.x controllers.
/linux-4.1.27/drivers/bluetooth/
DKconfig31 download support for Broadcom Bluetooth controllers.
123 port interface for Intel Bluetooth controllers.
134 port interface for Broadcom Bluetooth controllers.
/linux-4.1.27/drivers/scsi/
DKconfig376 driver. Anyone wishing to use HP Smart Array controllers who
497 This driver supports all of Adaptec's I2O based RAID controllers as
552 controllers.
667 signature. The addresses of all the PCI SCSI controllers reported
771 This is a driver for the old NCR 53c80 series of SCSI controllers
773 category, along with a large number of ISA 8bit controllers shipped
791 This is a driver for the old NCR 53c80 series of SCSI controllers
816 This is support for the IBM ServeRAID hardware RAID controllers.
1011 This driver supports Promise SuperTrak EX series storage controllers.
1014 controllers. Please visit <http://www.promise.com> to download.
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/memory-controllers/ti/
Demif.txt1 * EMIF family of TI SDRAM controllers
/linux-4.1.27/Documentation/devicetree/bindings/media/
Dexynos4-fimc-is.txt6 and SPI bus controllers, PWM and ADC.
/linux-4.1.27/arch/powerpc/boot/dts/
Dppa8548.dts102 * Use alias enet2 and enet3 for the remainig controllers,
/linux-4.1.27/Documentation/devicetree/bindings/iommu/
Darm,smmu.txt66 * Two DMA controllers, the first with two StreamIDs (0xd01d
/linux-4.1.27/drivers/net/phy/
DKconfig9 Ethernet controllers are usually attached to PHY
213 controllers as well as some Broadcom Ethernet switches such as the
/linux-4.1.27/drivers/net/can/
DKconfig48 get started. This works fine for the most common CAN controllers
84 Driver for the Analog Devices Blackfin on-chip CAN controllers
/linux-4.1.27/drivers/spi/
DKconfig27 work with most such devices and controllers.
246 tristate "Freescale i.MX SPI controllers"
250 This enables using the Freescale i.MX SPI controllers in master
297 This enables using the Freescale SPI controllers in master mode.
316 This enables using the Freescale eSPI controllers in master mode.
621 # Add new SPI master controllers in alphabetical order above this line
/linux-4.1.27/drivers/input/touchscreen/
DKconfig132 tristate "BU21013 based touch panel controllers"
204 Generation4 touchscreen controllers.
578 on the FocalTech FT5x06 family of controllers connected to
662 tristate "Support for WM831x touchscreen controllers"
672 tristate "Support for WM97xx AC97 touchscreen controllers"
766 - Zytronic controllers
947 tristate "Sitronix ST1232 touchscreen controllers"
963 STMPE touchscreen controllers.
/linux-4.1.27/Documentation/devicetree/bindings/ufs/
Dufshcd-pltfrm.txt3 UFSHC nodes are defined to describe on-chip UFS host controllers.

12