| /Linux-v5.4/Documentation/input/devices/ |
| D | xpad.rst | 2 xpad - Linux USB driver for Xbox compatible controllers
6 controllers. It has a long history and has enjoyed considerable usage
11 This only effects Original Xbox controllers. All later controller models
14 Rumble is supported on some models of Xbox 360 controllers but not of
15 Original Xbox controllers nor on Xbox One controllers. As of writing
39 unknown controllers.
42 Normal Controllers
77 of buttons, see section 0.3 - Unknown Controllers
82 Unknown Controllers
95 All generations of Xbox controllers speak USB over the wire.
[all …]
|
| /Linux-v5.4/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
14 - phy_type: tells USB controllers that we want to configure the core to support
17 In case this isn't passed via DT, USB controllers should
26 - hnp-disable: tells OTG controllers we want to disable OTG HNP, normally HNP
29 - srp-disable: tells OTG controllers we want to disable OTG SRP, SRP is
31 - adp-disable: tells OTG controllers we want to disable OTG ADP, ADP is
|
| /Linux-v5.4/drivers/ata/ |
| D | Kconfig | 83 comment "Controllers with non-SFF native interface"
116 controllers.
291 This option adds support for ATA controllers with SFF
295 the dawn of time. Almost all PATA controllers have an
296 SFF interface. Many SATA controllers have an SFF interface
299 For users with exclusively modern controllers like AHCI,
307 comment "SFF controllers with custom DMA interface"
313 This option enables support for Pacific Digital ADMA controllers
347 This option adds support for SFF ATA controllers with BMDMA
349 de facto DMA interface for SFF controllers.
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/serial/ |
| D | omap_serial.txt | 4 - compatible : should be "ti,j721e-uart", "ti,am654-uart" for J721E controllers
5 - compatible : should be "ti,am654-uart" for AM654 controllers
6 - compatible : should be "ti,omap2-uart" for OMAP2 controllers
7 - compatible : should be "ti,omap3-uart" for OMAP3 controllers
8 - compatible : should be "ti,omap4-uart" for OMAP4 controllers
9 - compatible : should be "ti,am4372-uart" for AM437x controllers
10 - compatible : should be "ti,am3352-uart" for AM335x controllers
11 - compatible : should be "ti,dra742-uart" for DRA7x controllers
|
| /Linux-v5.4/include/linux/mux/ |
| D | driver.h | 53 * struct mux_chip - Represents a chip holding mux controllers.
54 * @controllers: Number of mux controllers handled by the chip.
55 * @mux: Array of mux controllers that are handled.
61 unsigned int controllers; member
79 return &mux_chip->mux[mux_chip->controllers]; in mux_chip_priv()
83 unsigned int controllers, size_t sizeof_priv);
89 unsigned int controllers,
|
| /Linux-v5.4/include/linux/mfd/ |
| D | tmio.h | 40 * Some controllers can support a 2-byte block size when the bus width
45 * Some controllers can support SDIO IRQ signalling.
53 * Some controllers require waiting for the SD bus to become
61 * Some controllers have CMD12 automatically
70 * Some controllers have a 32-bit wide data port register
75 * Some controllers allows to set SDx actual clock
79 /* Some controllers have a CBSY bit */
82 /* Some controllers that support HS400 use 4 taps while others use 8. */
|
| /Linux-v5.4/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-v5.4/drivers/mux/ |
| D | core.c | 66 * @controllers: The number of mux controllers to allocate for this chip.
69 * After allocating the mux-chip with the desired number of mux controllers
80 unsigned int controllers, size_t sizeof_priv) in mux_chip_alloc() argument
85 if (WARN_ON(!dev || !controllers)) in mux_chip_alloc()
89 controllers * sizeof(*mux_chip->mux) + in mux_chip_alloc()
111 mux_chip->controllers = controllers; in mux_chip_alloc()
112 for (i = 0; i < controllers; ++i) { in mux_chip_alloc()
137 * mux_chip_register() - Register a mux-chip, thus readying the controllers
152 for (i = 0; i < mux_chip->controllers; ++i) { in mux_chip_register()
212 * @controllers: The number of mux controllers to allocate for this chip.
[all …]
|
| /Linux-v5.4/Documentation/PCI/endpoint/ |
| D | pci-endpoint-cfs.rst | 25 The pci_ep configfs has two directories at its root: controllers and
27 the *controllers* directory and and every EPF driver present in the system
32 .. controllers/
38 Every registered EPF driver will be listed in controllers directory. The
75 Every registered EPC device will be listed in controllers directory. The
79 /sys/kernel/config/pci_ep/controllers/
99 | controllers/
|
| /Linux-v5.4/drivers/net/can/spi/ |
| D | Kconfig | 6 tristate "Holt HI311x SPI CAN controllers"
9 Driver for the Holt HI311x SPI CAN controllers.
12 tristate "Microchip MCP251x and MCP25625 SPI CAN controllers"
16 controllers.
|
| /Linux-v5.4/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
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | cgroup-v2.rst | 25 2-4. Controlling Controllers
44 5. Controllers
94 qualifier as in "cgroup controllers". When explicitly referring to
105 cgroup is largely composed of two parts - the core and controllers.
109 although there are utility controllers which serve purposes other than
119 Following certain structural constraints, controllers may be enabled or
141 controllers which support v2 and are not bound to a v1 hierarchy are
143 Controllers which are not in active use in the v2 hierarchy can be
149 controller states are destroyed asynchronously and controllers may
155 to inter-controller dependencies, other controllers may need to be
[all …]
|
| /Linux-v5.4/drivers/pinctrl/bcm/ |
| D | Kconfig | 44 The Broadcom Cygnus SoC has 3 GPIO controllers including the ASIU
46 the always-ON GPIO controller (CRMU/AON). All 3 GPIO controllers are
49 The Broadcom NSP has two GPIO controllers including the ChipcommonA
54 the ChipcommonG GPIO. Both controllers are supported by this driver.
56 The Broadcom Stingray GPIO controllers are supported by this driver.
58 All above SoCs GPIO controllers support basic PINCONF functions such
|
| /Linux-v5.4/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 | 12 Should be "ti,omap2-hsmmc", for OMAP2 controllers
13 Should be "ti,omap3-hsmmc", for OMAP3 controllers
14 Should be "ti,omap3-pre-es3-hsmmc" for OMAP3 controllers pre ES3.0
15 Should be "ti,omap4-hsmmc", for OMAP4 controllers
16 Should be "ti,am33xx-hsmmc", for AM335x controllers
17 Should be "ti,k2g-hsmmc", "ti,omap4-hsmmc" for 66AK2G controllers.
|
| D | k3-dw-mshc.txt | 15 - "hisilicon,hi3660-dw-mshc": for controllers with hi3660 specific extensions.
16 - "hisilicon,hi3670-dw-mshc", "hisilicon,hi3660-dw-mshc": for controllers
18 - "hisilicon,hi4511-dw-mshc": for controllers with hi4511 specific extensions.
19 - "hisilicon,hi6220-dw-mshc": for controllers with hi6220 specific extensions.
|
| /Linux-v5.4/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.
|
| /Linux-v5.4/drivers/usb/gadget/udc/ |
| D | Kconfig | 11 # - Some systems have both kinds of controllers.
20 # The order here is alphabetical, except that integrated controllers go
22 # - integrated/SOC controllers first
24 # - discrete ones (including all PCI-only controllers)
30 # Integrated controllers
135 speed USB device controllers, with support for up to 30
137 controller in the OMAP 1611, and should work with controllers
291 # Controllers available in both integrated and discrete versions
309 # Controllers available only in discrete form (and all PCI controllers)
338 controllers having QE or CPM2, given minor tweaks.
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/gpio/ |
| D | nvidia,tegra186-gpio.txt | 1 NVIDIA Tegra186 GPIO controllers
3 Tegra186 contains two GPIO controllers; a main controller and an "AON"
4 controller. This binding document applies to both controllers. The register
5 layouts for the controllers share many similarities, but also some significant
17 varies between the different GPIO controllers.
25 controllers, these registers are exposed via multiple "physical aliases" in
52 both the overall controller HW module and the sets-of-ports as "controllers".
|
| /Linux-v5.4/Documentation/devicetree/bindings/memory-controllers/ |
| D | renesas,dbsc.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
|
| /Linux-v5.4/drivers/mmc/host/ |
| D | Kconfig | 64 and Toshiba(R). Most controllers found in laptops are of this type.
100 Most controllers found today are PCI devices.
121 tristate "SDHCI support for ACPI enumerated SDHCI controllers"
125 This selects support for ACPI enumerated SDHCI controllers,
145 tristate "SDHCI OF support for the Arasan SDHCI controllers"
191 tristate "SDHCI OF support for the Nintendo Wii SDHCI controllers"
543 SoC controllers.
573 controllers.
663 tristate "DMA for SDHI SD/SDIO controllers using SYS-DMAC"
667 This provides DMA support for SDHI SD/SDIO controllers
[all …]
|
| /Linux-v5.4/arch/arm/mach-omap2/ |
| D | hsmmc.c | 151 void __init omap_hsmmc_init(struct omap2_hsmmc_info *controllers) in omap_hsmmc_init() argument
166 for (; controllers->mmc; controllers++) in omap_hsmmc_init()
167 omap_hsmmc_init_one(controllers, controllers->mmc); in omap_hsmmc_init()
|
| /Linux-v5.4/drivers/dma/sh/ |
| D | Kconfig | 22 Enable support for the Renesas SuperH DMA controllers.
25 # DMA Controllers
32 Enable support for the Renesas SuperH DMA controllers.
|
| /Linux-v5.4/Documentation/devicetree/bindings/net/can/ |
| D | xilinx_can.txt | 6 - "xlnx,zynq-can-1.0" for Zynq CAN controllers
7 - "xlnx,axi-can-1.00.a" for Axi CAN controllers
8 - "xlnx,canfd-1.0" for CAN FD controllers
9 - "xlnx,canfd-2.0" for CAN FD 2.0 controllers
|
