| /Linux-v5.15/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.15/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 | usb-drd.yaml | 25 Tells Dual-Role USB controllers that we want to work on a particular
26 mode. In case this attribute isn't passed via DT, USB DRD controllers
33 Tells OTG controllers we want to disable OTG HNP. Normally HNP is the
40 Tells OTG controllers we want to disable OTG SRP. SRP is optional for OTG
46 Tells OTG controllers we want to disable OTG ADP. ADP is optional for OTG
|
| D | usb.yaml | 35 Tells USB controllers that we want to configure the core to support a
39 selected. In case this isn't passed via DT, USB controllers should
46 Tells USB controllers we want to work up to a certain speed. In case this
47 isn't passed via DT, USB controllers should default to their maximum HW
|
| /Linux-v5.15/drivers/ata/ |
| D | Kconfig | 107 comment "Controllers with non-SFF native interface"
142 controllers.
335 This option adds support for ATA controllers with SFF
339 the dawn of time. Almost all PATA controllers have an
340 SFF interface. Many SATA controllers have an SFF interface
343 For users with exclusively modern controllers like AHCI,
351 comment "SFF controllers with custom DMA interface"
357 This option enables support for Pacific Digital ADMA controllers
394 This option adds support for SFF ATA controllers with BMDMA
396 de facto DMA interface for SFF controllers.
[all …]
|
| /Linux-v5.15/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.15/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.15/drivers/net/can/spi/ |
| D | Kconfig | 6 tristate "Holt HI311x SPI CAN controllers"
8 Driver for the Holt HI311x SPI CAN controllers.
11 tristate "Microchip MCP251x and MCP25625 SPI CAN controllers"
14 controllers.
|
| /Linux-v5.15/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.15/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
66 * Some controllers have CMD12 automatically
75 * Some controllers have a 32-bit wide data port register
80 * Some controllers allows to set SDx actual clock
84 /* Some controllers have a CBSY bit */
|
| /Linux-v5.15/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 every EPF driver present in the system
32 .. controllers/
38 Every registered EPF driver will be listed in controllers directory. The
94 Every registered EPC device will be listed in controllers directory. The
98 /sys/kernel/config/pci_ep/controllers/
119 | controllers/
|
| D | pci-ntb-howto.rst | 31 # ls /sys/kernel/config/pci_ep/controllers
114 NTB function device should be attached to two PCI endpoint controllers
120 # ln -s controllers/2900000.pcie-ep/ functions/pci-epf-ntb/func1/primary
121 # ln -s controllers/2910000.pcie-ep/ functions/pci-epf-ntb/func1/secondary
123 Once the above step is completed, both the PCI endpoint controllers are ready to
131 field should be populated with '1'. For NTB, both the PCI endpoint controllers
134 # echo 1 > controllers/2900000.pcie-ep/start
135 # echo 1 > controllers/2910000.pcie-ep/start
|
| /Linux-v5.15/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.
|
| /Linux-v5.15/Documentation/admin-guide/ |
| D | cgroup-v2.rst | 27 2-4. Controlling Controllers
46 5. Controllers
102 qualifier as in "cgroup controllers". When explicitly referring to
113 cgroup is largely composed of two parts - the core and controllers.
117 although there are utility controllers which serve purposes other than
127 Following certain structural constraints, controllers may be enabled or
149 controllers which support v2 and are not bound to a v1 hierarchy are
151 Controllers which are not in active use in the v2 hierarchy can be
157 controller states are destroyed asynchronously and controllers may
163 to inter-controller dependencies, other controllers may need to be
[all …]
|
| /Linux-v5.15/Documentation/devicetree/bindings/memory-controllers/ |
| D | renesas,dbsc.yaml | 4 $id: "http://devicetree.org/schemas/memory-controllers/renesas,dbsc.yaml#"
7 title: Renesas DDR Bus Controllers
13 Renesas SoCs contain one or more memory controllers. These memory
14 controllers differ from one SoC variant to another, and are called by
|
| /Linux-v5.15/drivers/pinctrl/bcm/ |
| D | Kconfig | 107 The Broadcom Cygnus SoC has 3 GPIO controllers including the ASIU
109 the always-ON GPIO controller (CRMU/AON). All 3 GPIO controllers are
112 The Broadcom NSP has two GPIO controllers including the ChipcommonA
117 the ChipcommonG GPIO. Both controllers are supported by this driver.
119 The Broadcom Stingray GPIO controllers are supported by this driver.
121 All above SoCs GPIO controllers support basic PINCONF functions such
|
| /Linux-v5.15/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.15/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.15/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.15/include/linux/ |
| D | reset.h | 244 * multiple reset controllers.
283 * controllers.
304 * reset controllers.
352 * multiple reset controllers.
533 * Managed reset_control_get_exclusive(). For reset controllers returned
553 * Managed reset_control_bulk_get_exclusive(). For reset controllers returned
572 * Managed reset_control_get_exclusive_released(). For reset controllers
592 * Managed reset_control_bulk_get_exclusive_released(). For reset controllers
612 * reset controllers returned from this function, reset_control_put() is called
632 * controllers returned from this function, reset_control_put() is called
[all …]
|
| /Linux-v5.15/drivers/dma/lgm/ |
| D | Kconfig | 3 bool "Lightning Mountain centralized DMA controllers"
8 Enable support for Intel Lightning Mountain SOC DMA controllers.
9 These controllers provide DMA capabilities for a variety of on-chip
|
| /Linux-v5.15/drivers/pci/controller/ |
| D | pcie-iproc.h | 11 * @IPROC_PCIE_PAXB_BCMA: BCMA-based host controllers
12 * @IPROC_PCIE_PAXB: PAXB-based host controllers for
14 * @IPROC_PCIE_PAXB_V2: PAXB-based host controllers for Stingray SoCs
15 * @IPROC_PCIE_PAXC: PAXC-based host controllers
16 * @IPROC_PCIE_PAXC_V2: PAXC-based host controllers (second generation)
|
| /Linux-v5.15/drivers/pci/controller/dwc/ |
| D | Kconfig | 164 bool "HiSilicon Hip05 and Hip06 SoCs PCIe controllers"
269 bool "HiSilicon Kirin series SoCs PCIe controllers"
277 bool "HiSilicon STB SoCs PCIe controllers"
307 work in host mode. There are two instances of PCIe controllers in
322 work in endpoint mode. There are two instances of PCIe controllers in
329 bool "Toshiba Visconti PCIe controllers"
338 bool "Socionext UniPhier PCIe host controllers"
348 bool "Socionext UniPhier PCIe endpoint controllers"
|
| /Linux-v5.15/include/sound/ac97/ |
| D | controller.h | 20 * @controllers: linked list of all existing controllers.
29 * controllers themselves, excepting for using @dev.
33 struct list_head controllers; member
|
