| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-6.6/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 affects 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 …]
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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
8 controllers should default to their maximum HW
10 - dr_mode: tells Dual-Role USB controllers that we want to work on a
13 passed via DT, USB DRD controllers should default to
15 - phy_type: tells USB controllers that we want to configure the core to support
18 In case this isn't passed via DT, USB controllers should
27 - hnp-disable: tells OTG controllers we want to disable OTG HNP, normally HNP
30 - srp-disable: tells OTG controllers we want to disable OTG SRP, SRP is
32 - adp-disable: tells OTG controllers we want to disable OTG ADP, ADP is
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/drivers/ata/ |
| D | Kconfig | 107 comment "Controllers with non-SFF native interface"
144 controllers.
348 This option adds support for ATA controllers with SFF
352 the dawn of time. Almost all PATA controllers have an
353 SFF interface. Many SATA controllers have an SFF interface
356 For users with exclusively modern controllers like AHCI,
364 comment "SFF controllers with custom DMA interface"
370 This option enables support for Pacific Digital ADMA controllers
407 This option adds support for SFF ATA controllers with BMDMA
409 de facto DMA interface for SFF controllers.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/i2c/ |
| D | nvidia,tegra20-i2c.yaml | 39 Tegra114 has 5 generic I2C controllers. This controller is very much
52 Tegra124 has 6 generic I2C controllers. These controllers are very
57 Tegra210 has 6 generic I2C controllers. These controllers are very
66 the regular I2C controllers with a few exceptions. The I2C registers
72 Tegra186 has 9 generic I2C controllers, two of which are in the AON
73 (always-on) partition of the SoC. All of these controllers are very
77 Tegra194 has 8 generic I2C controllers, two of which are in the AON
78 (always-on) partition of the SoC. All of these controllers are very
79 similar to those found on Tegra186. However, these controllers have
107 Module reset. This property is optional for controllers in Tegra194,
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/mmc/ |
| D | sdhci-omap.txt | 8 - compatible: Should be "ti,omap2430-sdhci" for omap2430 controllers
9 Should be "ti,omap3-sdhci" for omap3 controllers
10 Should be "ti,omap4-sdhci" for omap4 and ti81 controllers
11 Should be "ti,omap5-sdhci" for omap5 controllers
12 Should be "ti,dra7-sdhci" for DRA7 and DRA72 controllers
14 Should be "ti,am335-sdhci" for am335x controllers
15 Should be "ti,am437-sdhci" for am437x controllers
|
| /kernel/linux/linux-6.6/include/linux/mux/ |
| D | driver.h | 57 * struct mux_chip - Represents a chip holding mux controllers.
58 * @controllers: Number of mux controllers handled by the chip.
59 * @mux: Array of mux controllers that are handled.
65 unsigned int controllers; member
83 return &mux_chip->mux[mux_chip->controllers]; in mux_chip_priv()
87 unsigned int controllers, size_t sizeof_priv);
93 unsigned int controllers,
|
| /kernel/linux/linux-5.10/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,
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/phy/ |
| D | realtek,usb2phy.yaml | 16 support multiple XHCI controllers. One PHY device node maps to one XHCI
20 The USB architecture includes three XHCI controllers.
22 controllers.
30 The USB architecture includes two XHCI controllers.
38 The USB architecture includes three XHCI controllers.
39 Each XHCI maps to one USB 2.0 PHY and map one USB 3.0 PHY on controllers#2.
46 The USB architecture includes three XHCI controllers.
47 Each xhci maps to one USB 2.0 PHY and map one USB 3.0 PHY on controllers#0.
54 The USB architecture includes three XHCI controllers.
|
| D | realtek,usb3phy.yaml | 16 support multiple XHCI controllers. One PHY device node maps to one XHCI
20 The USB architecture includes three XHCI controllers.
22 controllers.
30 The USB architecture includes three XHCI controllers.
31 Each XHCI maps to one USB 2.0 PHY and map one USB 3.0 PHY on controllers#2.
38 The USB architecture includes three XHCI controllers.
39 Each xhci maps to one USB 2.0 PHY and map one USB 3.0 PHY on controllers#0.
|
| /kernel/linux/linux-6.6/tools/testing/selftests/bpf/ |
| D | cgroup_helpers.c | 52 static int __enable_controllers(const char *cgroup_path, const char *controllers) in __enable_controllers() argument
60 /* If not controllers are passed, enable all available controllers */ in __enable_controllers()
61 if (!controllers) { in __enable_controllers()
62 snprintf(path, sizeof(path), "%s/cgroup.controllers", in __enable_controllers()
66 log_err("Opening cgroup.controllers: %s", path); in __enable_controllers()
72 log_err("Reading cgroup.controllers: %s", path); in __enable_controllers()
74 } else if (len == 0) { /* No controllers to enable */ in __enable_controllers()
81 bpf_strlcpy(enable, controllers, sizeof(enable)); in __enable_controllers()
103 * enable_controllers() - Enable cgroup v2 controllers
105 * @controllers: List of controllers to enable in cgroup.controllers format
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-5.10/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
75 Every registered EPC device will be listed in controllers directory. The
79 /sys/kernel/config/pci_ep/controllers/
99 | controllers/
|
| /kernel/linux/linux-6.6/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 */
|
| /kernel/linux/linux-5.10/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 */
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/drivers/pinctrl/bcm/ |
| D | Kconfig | 45 The Broadcom Cygnus SoC has 3 GPIO controllers including the ASIU
47 the always-ON GPIO controller (CRMU/AON). All 3 GPIO controllers are
50 The Broadcom NSP has two GPIO controllers including the ChipcommonA
55 the ChipcommonG GPIO. Both controllers are supported by this driver.
57 The Broadcom Stingray GPIO controllers are supported by this driver.
59 All above SoCs GPIO controllers support basic PINCONF functions such
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | cgroup-v2.rst | 25 2-4. Controlling Controllers
44 5. Controllers
96 qualifier as in "cgroup controllers". When explicitly referring to
107 cgroup is largely composed of two parts - the core and controllers.
111 although there are utility controllers which serve purposes other than
121 Following certain structural constraints, controllers may be enabled or
143 controllers which support v2 and are not bound to a v1 hierarchy are
145 Controllers which are not in active use in the v2 hierarchy can be
151 controller states are destroyed asynchronously and controllers may
157 to inter-controller dependencies, other controllers may need to be
[all …]
|