/linux-4.4.14/arch/tile/kernel/ |
D | pci.c | 62 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.4.14/Documentation/devicetree/bindings/usb/ |
D | fsl-usb.txt | 1 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
|
D | generic.txt | 4 - 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 20 - hnp-disable: tells OTG controllers we want to disable OTG HNP, normally HNP 23 - srp-disable: tells OTG controllers we want to disable OTG SRP, SRP is 25 - adp-disable: tells OTG controllers we want to disable OTG ADP, ADP is
|
D | brcm,bcm3384-usb.txt | 1 * Broadcom USB controllers 11 - Figuring out which controllers are disabled on ASIC bondout variants
|
D | pxa-usb.txt | 1 PXA USB controllers 6 - compatible: Should be "marvell,pxa-ohci" for USB controllers 35 - compatible: Should be "marvell,pxa270-udc" for USB controllers
|
D | atmel-usb.txt | 1 Atmel SOC USB controllers 6 - compatible: Should be "atmel,at91rm9200-ohci" for USB controllers 33 - compatible: Should be "atmel,at91sam9g45-ehci" for USB controllers
|
D | usb-xhci.txt | 1 USB xHCI controllers
|
D | spear-usb.txt | 1 ST SPEAr SoC USB controllers:
|
D | usb-ohci.txt | 1 USB OHCI controllers
|
D | nvidia,tegra20-ehci.txt | 1 Tegra SOC USB controllers
|
D | usb-ehci.txt | 1 USB EHCI controllers
|
/linux-4.4.14/Documentation/devicetree/bindings/serial/ |
D | omap_serial.txt | 4 - 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 7 - compatible : should be "ti,am4372-uart" for AM437x controllers 8 - compatible : should be "ti,am3352-uart" for AM335x controllers 9 - compatible : should be "ti,dra742-uart" for DRA7x controllers
|
/linux-4.4.14/Documentation/devicetree/bindings/rtc/ |
D | s3c-rtc.txt | 5 * "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" - (deprecated) for controllers compatible with
|
/linux-4.4.14/Documentation/input/ |
D | xpad.txt | 1 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.4.14/drivers/dma/sh/ |
D | Kconfig | 21 Enable support for the Renesas SuperH DMA controllers. 31 Enable support for the Renesas SuperH DMA controllers. 54 Enable support for the Renesas R-Car series DMA controllers. 69 Enable support for the Renesas SUDMAC controllers.
|
/linux-4.4.14/Documentation/ABI/testing/ |
D | sysfs-bus-pci-drivers-ehci_hcd | 7 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
|
D | sysfs-class-scsi_host | 7 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
|
D | sysfs-class-uwb_rc | 7 Platform (UWB) radio controllers. 100 controllers beacon group. 107 The time (using the radio controllers internal 1 ms
|
/linux-4.4.14/Documentation/cgroups/ |
D | unified-hierarchy.txt | 16 2-3. cgroup.controllers 40 can host any number of controllers. While this seems to provide a 44 type controllers such as freezer which can be useful in all 46 fact that controllers can't be moved around once hierarchies are 47 populated. Another issue is that all controllers bound to a hierarchy 51 In practice, these issues heavily limit which controllers can be put 54 the cpu and cpuacct controllers, make sense to put on the same 62 restricts how cgroup is used in general and what controllers can do. 68 of controllers which exist only to identify membership, which in turn 72 of hierarchies other controllers would be on, each controller has to [all …]
|
/linux-4.4.14/drivers/ata/ |
D | Kconfig | 97 controllers. 222 This option adds support for ATA controllers with SFF 226 the dawn of time. Almost all PATA controllers have an 227 SFF interface. Many SATA controllers have an SFF interface 230 For users with exclusively modern controllers like AHCI, 238 comment "SFF controllers with custom DMA interface" 244 This option enables support for Pacific Digital ADMA controllers 277 This option adds support for SFF ATA controllers with BMDMA 279 de facto DMA interface for SFF controllers. 285 comment "SATA SFF controllers with BMDMA" [all …]
|
/linux-4.4.14/Documentation/devicetree/bindings/memory-controllers/ |
D | renesas-memory-controllers.txt | 1 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
|
D | synopsys.txt | 9 - reg: Base address and size of the controllers memory area
|
D | mvebu-sdram-controller.txt | 1 Device Tree bindings for MVEBU SDRAM controllers
|
D | ath79-ddr-controller.txt | 14 - reg: Base address and size of the controllers memory area
|
/linux-4.4.14/drivers/net/can/spi/ |
D | Kconfig | 5 tristate "Microchip MCP251x SPI CAN controllers" 8 Driver for the Microchip MCP251x SPI CAN controllers.
|
/linux-4.4.14/Documentation/devicetree/bindings/gpio/ |
D | gpio-omap.txt | 5 - "ti,omap2-gpio" for OMAP2 controllers 6 - "ti,omap3-gpio" for OMAP3 controllers 7 - "ti,omap4-gpio" for OMAP4 controllers
|
D | gpio-ath79.txt | 8 - reg: Base address and size of the controllers memory area 16 - interrupts: Interrupt specifier for the controllers interrupt.
|
D | 8xxx_gpio.txt | 1 GPIO controllers on MPC8xxx SoCs 3 This is for the non-QE/CPM/GUTs GPIO controllers as found on
|
D | gpio-sx150x.txt | 14 - interrupts: Interrupt specifier for the controllers interrupt.
|
D | gpio-adnp.txt | 7 - interrupts: Interrupt specifier for the controllers interrupt.
|
D | gpio-dsp-keystone.txt | 7 For example TCI6638K2K SoC has 8 DSP GPIO controllers:
|
/linux-4.4.14/Documentation/devicetree/bindings/mmc/ |
D | exynos-dw-mshc.txt | 13 - "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
|
D | ti-omap-hsmmc.txt | 11 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
|
D | samsung-sdhci.txt | 10 - "samsung,s3c6410-sdhci": For controllers compatible with s3c6410 sdhci 12 - "samsung,exynos4210-sdhci": For controllers compatible with Exynos4 sdhci
|
D | ti-omap.txt | 13 - compatible: Must be "ti,omap2420-mmc", for OMAP2420 controllers 40 - compatible: Must be "ti,omap2420-mmc", for OMAP2420 controllers
|
D | k3-dw-mshc.txt | 15 - "hisilicon,hi4511-dw-mshc": for controllers with hi4511 specific extensions. 16 - "hisilicon,hi6220-dw-mshc": for controllers with hi6220 specific extensions.
|
/linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/ |
D | msi.txt | 1 This document describes the generic device tree binding for MSI controllers and 9 those busses to the MSI controllers which they are capable of using, 22 MSI controllers may have restrictions on permitted payloads. 31 MSI controllers: 68 MSI controllers listed in the msi-parent property. 131 * Can generate MSIs to all of the MSI controllers.
|
D | qca,ath79-misc-intc.txt | 9 - reg: Base address and size of the controllers memory area 11 - interrupts: Interrupt specifier for the controllers interrupt.
|
D | samsung,s3c24xx-irq.txt | 3 The S3C24XX SoCs contain a custom set of interrupt controllers providing a 26 ignored in main controllers
|
D | arm,versatile-fpga-irq.txt | 3 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
|
D | arm,vic.txt | 4 system for interrupt routing. For multiple controllers they can either be 20 - interrupts : Interrupt source for parent controllers if the VIC is nested.
|
D | nxp,lpc3220-mic.txt | 2 (MIC, including SIC1 and SIC2 secondary controllers)
|
D | nvidia,tegra-ictlr.txt | 7 The HW block exposes a number of interrupt controllers, each
|
D | marvell,orion-intc.txt | 1 Marvell Orion SoC interrupt controllers
|
/linux-4.4.14/drivers/scsi/megaraid/ |
D | Kconfig.megaraid | 12 RAID controllers. 21 List of supported controllers 73 RAID controllers 82 Module for LSI Logic's SAS based RAID controllers.
|
/linux-4.4.14/Documentation/devicetree/bindings/sound/ |
D | mxs-audio-sgtl5000.txt | 6 - saif-controllers: The phandle list of the MXS SAIF controller 15 saif-controllers = <&saif0 &saif1>;
|
/linux-4.4.14/drivers/hsi/controllers/ |
D | Kconfig | 2 # HSI controllers configuration 4 comment "HSI controllers"
|
/linux-4.4.14/drivers/gpu/drm/armada/ |
D | Kconfig | 10 Support the "LCD" controllers found on the Marvell Armada 510 11 devices. There are two controllers on the device, each controller
|
/linux-4.4.14/Documentation/devicetree/bindings/input/ |
D | twl4030-pwrbutton.txt | 10 - "ti,twl4030-pwrbutton": For controllers compatible with twl4030 12 - <8>: For controllers compatible with twl4030
|
D | twl4030-keypad.txt | 16 - "ti,twl4030-keypad": For controllers compatible with twl4030 keypad 19 - <1>: For controllers compatible with twl4030 keypad controller.
|
D | tps65218-pwrbutton.txt | 8 - <3 IRQ_TYPE_EDGE_BOTH>: For controllers compatible with tps65218
|
D | samsung-keypad.txt | 11 - "samsung,s3c6410-keypad": For controllers compatible with s3c6410 keypad 13 - "samsung,s5pv210-keypad": For controllers compatible with s5pv210 keypad
|
D | omap-keypad.txt | 16 - "ti,omap4-keypad": For controllers compatible with omap4 keypad
|
/linux-4.4.14/drivers/pinctrl/bcm/ |
D | Kconfig | 33 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.4.14/Documentation/devicetree/bindings/pci/ |
D | pci-rcar-gen2.txt | 4 This is the bridge used internally to connect the USB controllers to the 6 OHCI and EHCI controllers. 13 the operational registers for the OHCI/EHCI controllers and the
|
D | pci-msi.txt | 2 relationship between PCI devices and MSI controllers. 19 controllers it can address, and the sideband data that will be associated with 20 its writes to those controllers.
|
/linux-4.4.14/Documentation/devicetree/bindings/dma/ |
D | adi,axi-dmac.txt | 5 - reg: Specification for the controllers memory mapped register map. 6 - interrupts: Specification for the controllers interrupt. 7 - clocks: Phandle and specifier to the controllers AXI interface clock
|
D | dma.txt | 42 the DMA controllers the router can direct the signal to. 96 2. A single read-write channel with three alternative DMA controllers:
|
D | nbpfaxi.txt | 1 * Renesas "Type-AXI" NBPFAXI* DMA controllers
|
/linux-4.4.14/arch/arm/mach-omap2/ |
D | hsmmc.c | 485 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.4.14/Documentation/devicetree/bindings/net/can/ |
D | grcan.txt | 1 Aeroflex Gaisler GRCAN and GRHCAN CAN controllers. 3 The GRCAN and CRHCAN CAN controllers are available in the GRLIB VHDL IP core
|
D | xilinx_can.txt | 6 controllers and "xlnx,axi-can-1.00.a" for Axi CAN 7 controllers.
|
D | c_can.txt | 5 - compatible : Should be "bosch,c_can" for C_CAN controllers and 6 "bosch,d_can" for D_CAN controllers.
|
/linux-4.4.14/drivers/usb/ |
D | README | 14 * 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.4.14/Documentation/devicetree/bindings/clock/ |
D | hi6220-clock.txt | 3 Clock control registers reside in different Hi6220 system controllers, 5 for these system controllers:
|
D | pistachio-clock.txt | 1 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
|
D | exynos7-clock.txt | 4 independently from the device-tree. These clock controllers 24 - compatible: clock controllers will use one of the following
|
D | hi3620-clock.txt | 4 controllers within the Hi3620 SoC.
|
D | marvell,pxa910.txt | 4 controllers within the PXA910 SoC.
|
D | hix5hd2-clock.txt | 4 controllers within the hix5hd2 SoC.
|
D | exynos5440-clock.txt | 4 controllers within the Exynos5440 SoC.
|
D | marvell,pxa168.txt | 4 controllers within the PXA168 SoC.
|
D | marvell,mmp2.txt | 4 controllers within the MMP2 SoC.
|
D | marvell,pxa1928.txt | 4 controllers within the PXA1928 SoC. The PXA1928 contains 3 clock controller
|
D | qca,ath79-pll.txt | 14 - reg: Base address and size of the controllers memory area
|
D | exynos5250-clock.txt | 4 controllers within the Exynos5250 SoC.
|
D | amlogic,meson8b-clkc.txt | 4 controllers within the SoC.
|
D | exynos5410-clock.txt | 4 controllers within the Exynos5410 SoC.
|
D | exynos5420-clock.txt | 4 controllers within the Exynos5420 SoC and for the Exynos5800 SoC.
|
D | exynos5260-clock.txt | 3 Exynos5260 has 13 clock controllers which are instantiated 4 independently from the device-tree. These clock controllers
|
D | exynos4-clock.txt | 3 The Exynos4 clock controller generates and supplies clock to various controllers
|
D | exynos3250-clock.txt | 4 controllers within the Exynos3250 SoC.
|
D | samsung,s3c2412-clock.txt | 3 The S3C2412 clock controller generates and supplies clock to various controllers
|
D | samsung,s3c2410-clock.txt | 3 The S3C2410 clock controller generates and supplies clock to various controllers
|
D | rockchip,rk3288-cru.txt | 4 controllers within the SoC and also implements a reset controller for SoC
|
D | samsung,s3c2443-clock.txt | 3 The S3C2443 clock controller generates and supplies clock to various controllers
|
D | rockchip,rk3188-cru.txt | 4 controllers within the SoC and also implements a reset controller for SoC
|
D | rockchip,rk3368-cru.txt | 4 controllers within the SoC and also implements a reset controller for SoC
|
D | samsung,s5pv210-clock.txt | 4 controller, which generates and supplies clock to various controllers
|
D | samsung,s3c64xx-clock.txt | 3 The S3C64xx clock controller generates and supplies clock to various controllers
|
/linux-4.4.14/Documentation/usb/ |
D | mtouchusb.txt | 18 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
|
D | ohci.txt | 9 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.4.14/drivers/uwb/ |
D | Kconfig | 19 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.4.14/Documentation/devicetree/bindings/leds/ |
D | common.txt | 36 For flash LED controllers with configurable current this 45 For controllers that have no configurable current the flash-max-microamp 47 For controllers that have no configurable timeout the flash-max-timeout-us
|
/linux-4.4.14/drivers/hsi/ |
D | Makefile | 6 obj-y += controllers/
|
D | Kconfig | 17 source "drivers/hsi/controllers/Kconfig"
|
/linux-4.4.14/Documentation/devicetree/bindings/net/ |
D | cpsw.txt | 7 "ti,am335x-cpsw" for AM335x controllers 8 "ti,am4372-cpsw" for AM437x controllers 9 "ti,dra7-cpsw" for DRA7x controllers
|
D | hisilicon-hip04-net.txt | 22 Control rx & tx fifos of all ethernet controllers. 23 Have 2048 recv channels shared by all ethernet controllers, only if no overlap.
|
D | mdio-gpio.txt | 6 MDC and MDIO lines connected to GPIO controllers are listed in the
|
D | via-rhine.txt | 5 Rhine controllers found in VIA VT8500, WonderMedia WM8950
|
D | marvell-orion-net.txt | 14 Note: The above separation is only true for Discovery system controllers. 17 controllers. As Kirkwood has some issues with proper initialization after reset,
|
D | marvell-orion-mdio.txt | 3 The Ethernet controllers of the Marvel Kirkwood, Dove, Orion5x,
|
D | gpmc-eth.txt | 5 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
|
/linux-4.4.14/Documentation/scsi/ |
D | megaraid.txt | 7 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,
|
D | ChangeLog.megaraid_sas | 50 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 …
|
D | aic7xxx.txt | 40 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
|
D | 00-INDEX | 38 - Driver supporting Adaptec RAID controllers 46 - info on driver for Adaptec controllers
|
D | ncr53c8xx.txt | 74 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 …]
|
D | aacraid.txt | 6 RAID controllers. This is a major rewrite from the original 127 …ds (non-DASD support, PAE fibs and 64 bit, added new adaptec controllers
|
D | hpsa.txt | 5 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.4.14/Documentation/devicetree/bindings/arm/samsung/ |
D | exynos-adc.txt | 14 for exynos4412/5250 and s5pv210 controllers. 16 future controllers. 18 controllers compatible with ADC of Exynos3250.
|
/linux-4.4.14/Documentation/xtensa/ |
D | atomctl.txt | 22 use the memory controllers RCW, thought non-MX controlers likely 26 Virtually all customers buy their memory controllers from vendors that
|
/linux-4.4.14/drivers/message/fusion/ |
D | Kconfig | 21 List of supported controllers: 36 List of supported controllers: 55 List of supported controllers:
|
/linux-4.4.14/drivers/scsi/esas2r/ |
D | Kconfig | 5 This driver supports the ATTO ExpressSAS R6xx SAS/SATA RAID controllers.
|
/linux-4.4.14/drivers/usb/gadget/udc/ |
D | Kconfig | 10 # - 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.4.14/Documentation/mtd/ |
D | spi-nor.txt | 7 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.4.14/drivers/devfreq/ |
D | Kconfig | 77 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.4.14/Documentation/devicetree/bindings/arm/ |
D | spear-misc.txt | 4 few properties of different peripheral controllers.
|
D | vexpress.txt | 77 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:
|
/linux-4.4.14/Documentation/ |
D | hsi.txt | 41 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.
|
D | IRQ-domain.txt | 6 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:
|
D | debugging-via-ohci1394.txt | 2 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
|
D | IRQ.txt | 17 controllers.
|
/linux-4.4.14/Documentation/devicetree/bindings/arm/bcm/ |
D | brcm,brcmstb.txt | 142 = Memory controllers 144 A Broadcom STB SoC typically has a number of independent memory controllers, 147 describing these controllers as a parent "memory controllers" block, which
|
D | brcm,nsp.txt | 9 SATA and several other IO controllers.
|
/linux-4.4.14/Documentation/devicetree/bindings/arm/omap/ |
D | counter.txt | 4 - compatible: Must be "ti,omap-counter32k" for OMAP controllers
|
D | dmm.txt | 4 SDRAM controllers (called EMIFs on OMAP). DMM manages various aspects of memory
|
/linux-4.4.14/sound/usb/ |
D | Kconfig | 44 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.4.14/drivers/mmc/card/ |
D | Kconfig | 42 controllers, however, are restricted to continuous memory 65 in host controllers. The tests are executed by writing to the
|
/linux-4.4.14/Documentation/devicetree/bindings/reset/ |
D | ath79-reset.txt | 9 - reg: Base address and size of the controllers memory area
|
D | st,sti-softreset.txt | 5 disable on-chip peripheral controllers such as USB and SATA, using
|
D | st,sti-powerdown.txt | 5 disable on-chip peripheral controllers such as USB and SATA, using
|
/linux-4.4.14/Documentation/devicetree/bindings/spi/ |
D | spi-meson.txt | 1 Amlogic Meson SPI controllers
|
D | spi-ath79.txt | 5 - reg: Base address and size of the controllers memory area
|
D | spi-orion.txt | 12 - cell-index : Which of multiple SPI controllers is this.
|
D | spi_atmel.txt | 15 capable SPI controllers.
|
D | spi-bus.txt | 6 SPI master mode. This binding does not describe SPI controllers 65 Some SPI controllers and devices support Dual and Quad SPI transfer mode.
|
D | spi-rockchip.txt | 4 and display controllers using the SPI communication interface.
|
/linux-4.4.14/Documentation/arm/stm32/ |
D | stm32f429-overview.txt | 11 - I2C, SPI, SAI, CAN, USB OTG, Ethernet controllers
|
/linux-4.4.14/Documentation/devicetree/bindings/phy/ |
D | qcom-ipq806x-sata-phy.txt | 4 SATA PHY nodes are defined to describe on-chip SATA Physical layer controllers.
|
D | qcom-apq8064-sata-phy.txt | 4 SATA PHY nodes are defined to describe on-chip SATA Physical layer controllers.
|
D | samsung-phy.txt | 90 SATA PHY nodes are defined to describe on-chip SATA Physical layer controllers. 171 - aliases: For SoCs like Exynos5420 having multiple USB 3.0 DRD PHY controllers, 174 controllers).
|
D | phy-stih407-usb.txt | 4 host controllers (when controlling usb2/1.1 devices) available on STiH407 SoC family from STMicroel…
|
D | qcom-dwc3-usb-phy.txt | 5 controllers. Each DWC3 PHY controller should have its own node.
|
D | phy-mvebu.txt | 29 features of both USB controllers.
|
/linux-4.4.14/Documentation/devicetree/bindings/input/touchscreen/ |
D | pixcir_i2c_ts.txt | 1 * Pixcir I2C touchscreen controllers
|
D | tsc2005.txt | 1 * Texas Instruments tsc2004 and tsc2005 touchscreen controllers
|
/linux-4.4.14/Documentation/devicetree/bindings/timer/ |
D | samsung,exynos4210-mct.txt | 51 interrupt controllers. Hence, an interrupt-map is created to map 52 the interrupts to the respective interrupt controllers.
|
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/ |
D | fsl,imx7d-pinctrl.txt | 3 iMX7D supports two iomuxc controllers, fsl,imx7d-iomuxc controller is similar 58 any of the iomux controllers. For example the I2C1 IP can use SCL pad from
|
D | pinctrl-bindings.txt | 5 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
|
D | img,pistachio-pinctrl.txt | 1 Imagination Technologies Pistachio SoC pin controllers 4 The pin controllers on Pistachio are a combined GPIO controller, (GPIO)
|
D | brcm,cygnus-gpio.txt | 30 Specifies the mapping between gpio controller and pin-controllers pins.
|
/linux-4.4.14/Documentation/devicetree/bindings/power/ |
D | power_domain.txt | 19 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.4.14/drivers/ide/ |
D | Kconfig | 51 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.4.14/arch/powerpc/sysdev/ |
D | Kconfig | 36 bool "Expose SCOM controllers via debugfs"
|
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/ |
D | serial.txt | 10 Modem control lines connected to GPIO controllers are listed in the gpios
|
/linux-4.4.14/sound/oss/ |
D | sound_config.h | 95 unsigned char controllers[128]; member
|
D | sequencer.c | 564 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.4.14/Documentation/devicetree/bindings/ata/ |
D | brcm,sata-brcmstb.txt | 3 SATA nodes are defined to describe on-chip Serial ATA controllers.
|
D | fsl-sata.txt | 3 SATA nodes are defined to describe on-chip Serial ATA controllers.
|
D | exynos-sata.txt | 3 SATA nodes are defined to describe on-chip Serial ATA controllers.
|
D | qcom-sata.txt | 3 SATA nodes are defined to describe on-chip Serial ATA controllers.
|
D | sata_highbank.txt | 3 SATA nodes are defined to describe on-chip Serial ATA controllers.
|
/linux-4.4.14/include/linux/ |
D | agpgart.h | 124 struct agp_controller *controllers; member
|
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/ |
D | srio-rmu.txt | 3 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.
|
D | pamu.txt | 17 physically present PAMU controllers. For example, for 57 be set to the size of this PAMU controllers's register space.
|
/linux-4.4.14/drivers/pinctrl/ |
D | Kconfig | 8 menu "Pin controllers" 12 bool "Support pin multiplexing controllers" if COMPILE_TEST 15 bool "Support pin configuration controllers" if COMPILE_TEST
|
/linux-4.4.14/arch/mips/alchemy/ |
D | Kconfig | 1 # au1000-style gpio and interrupt controllers
|
/linux-4.4.14/drivers/usb/dwc2/ |
D | Kconfig | 12 controllers directly connected to the CPU) will be called 59 The Designware USB2.0 PCI interface module for controllers
|
/linux-4.4.14/drivers/char/agp/ |
D | frontend.c | 297 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.4.14/drivers/misc/c2port/ |
D | Kconfig | 12 If your board have no such micro controllers you don't need this
|
/linux-4.4.14/Documentation/i2c/busses/ |
D | i2c-ismt | 29 The S12xx series of SOCs have a pair of integrated SMBus 2.0 controllers
|
D | scx200_acb | 11 Base addresses for the ACCESS.bus controllers on SCx200 and SC1100 devices
|
/linux-4.4.14/arch/arm/boot/dts/ |
D | s3c6400.dtsi | 10 * Note: This file does not include device nodes for all the controllers in
|
D | s3c6410.dtsi | 10 * Note: This file does not include device nodes for all the controllers in
|
/linux-4.4.14/Documentation/devicetree/bindings/c6x/ |
D | clocks.txt | 4 This is a first-cut support for the SoC clock controllers. This is still
|
/linux-4.4.14/Documentation/hwmon/ |
D | adm1031 | 24 The ADM1030 and ADM1031 are digital temperature sensors and fan controllers.
|
D | zl6100 | 64 compatible digital DC-DC controllers. 99 Intersil/Zilker Labs DC-DC controllers require a minimum interval between I2C
|
/linux-4.4.14/Documentation/devicetree/bindings/spmi/ |
D | spmi.txt | 3 This document defines a generic set of bindings for use by SPMI controllers. A
|
/linux-4.4.14/drivers/scsi/aic7xxx/ |
D | Kconfig.aic7xxx | 11 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.4.14/Documentation/devicetree/bindings/mfd/ |
D | sun6i-prcm.txt | 4 (like clks and reset controllers).
|
/linux-4.4.14/arch/mips/sgi-ip27/ |
D | TODO | 5 Qlogic scsi controllers.
|
/linux-4.4.14/drivers/net/ethernet/arc/ |
D | Kconfig | 37 Support for Rockchip RK3066/RK3188 EMAC ethernet controllers.
|
/linux-4.4.14/Documentation/blockdev/ |
D | README.DAC960 | 20 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 …]
|
D | cpqarray.txt | 37 controllers, in EISA slots 1 and 2 you'd give it a boot argument like
|
/linux-4.4.14/drivers/bluetooth/ |
D | Kconfig | 40 download support for Broadcom Bluetooth controllers. 51 download support for Realtek Bluetooth controllers. 144 port interface for Intel Bluetooth controllers. 155 port interface for Broadcom Bluetooth controllers.
|
/linux-4.4.14/Documentation/block/ |
D | data-integrity.txt | 21 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.4.14/drivers/usb/host/ |
D | Kconfig | 10 host/peripheral/OTG USB controllers. 70 EHCI controllers are packaged with "companion" host controllers (OHCI 225 found in NVIDIA Tegra SoCs. The controllers are EHCI compliant. 325 implement OTG nor USB device controllers. 333 The ISP1160 and ISP1161 chips are USB host controllers. Enable this 484 Enables support for big-endian USB controllers present on the 492 Enables support for little-endian USB controllers present on the 501 tristate "OHCI support for PCI-bus USB controllers" 641 For those PC cards that contain multiple OHCI controllers only the
|
/linux-4.4.14/drivers/net/ethernet/ibm/emac/ |
D | Kconfig | 6 This driver supports the IBM EMAC family of Ethernet controllers
|
/linux-4.4.14/Documentation/devicetree/bindings/i2c/ |
D | i2c-at91.txt | 19 capable I2C controllers.
|
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/qe/ |
D | par_io.txt | 34 - gpio-controller : node to identify gpio controllers.
|
/linux-4.4.14/drivers/usb/phy/ |
D | Kconfig | 96 Provides simple GPIO VBUS sensing for controllers with an 214 controllers with a viewport register (e.g. Chipidea/ARC controllers).
|
/linux-4.4.14/Documentation/gpio/ |
D | gpio-legacy.txt | 37 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.4.14/drivers/net/ethernet/sfc/ |
D | Kconfig | 12 controllers.
|
/linux-4.4.14/drivers/mmc/host/ |
D | Kconfig | 44 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" 153 tristate "SDHCI OF support for the Nintendo Wii SDHCI controllers" 461 SoC controllers. 492 controllers. 733 Note: These controllers only support SDIO cards and do not
|
/linux-4.4.14/drivers/usb/misc/sisusbvga/ |
D | Kconfig | 11 work with USB 1.x controllers.
|
/linux-4.4.14/drivers/staging/nvec/ |
D | Kconfig | 38 nVidia compliant embedded controllers.
|
/linux-4.4.14/Documentation/devicetree/bindings/soc/sunxi/ |
D | sram.txt | 1 Allwinnner SoC SRAM controllers
|
/linux-4.4.14/Documentation/devicetree/bindings/arm/hisilicon/ |
D | hisilicon.txt | 62 Hisilicon designs this controller as one of the system controllers, 180 The HiP05 PCIe-SAS system controller is shared by PCIe and SAS controllers in
|
/linux-4.4.14/drivers/scsi/ |
D | Kconfig | 371 driver. Anyone wishing to use HP Smart Array controllers who 492 This driver supports all of Adaptec's I2O based RAID controllers as 547 controllers. 679 signature. The addresses of all the PCI SCSI controllers reported 783 This is a driver for the old NCR 53c80 series of SCSI controllers 785 category, along with a large number of ISA 8bit controllers shipped 803 This is a driver for the old NCR 53c80 series of SCSI controllers 828 This is support for the IBM ServeRAID hardware RAID controllers. 1023 This driver supports Promise SuperTrak EX series storage controllers. 1026 controllers. Please visit <http://www.promise.com> to download. [all …]
|