| /linux/include/linux/mux/ |
| H A D | driver.h | 57 * struct mux_chip - Represents a chip holding mux controllers.
58 * @controllers: Number of mux controllers handled by the chip.
62 * @mux: Array of mux controllers that are handled.
65 unsigned int controllers; member
70 struct mux_control mux[] __counted_by(controllers);
83 return &mux_chip->mux[mux_chip->controllers]; in mux_chip_priv()
87 unsigned int controllers, size_t sizeof_priv);
93 unsigned int controllers,
|
| /linux/Documentation/ABI/testing/ |
| H A D | debugfs-pcie-ptm | 6 Complex and Endpoint controllers.
13 Endpoint controllers.
20 Endpoint controllers.
27 Root Complex controllers.
34 Root Complex controllers.
41 Endpoint controllers.
48 Endpoint controllers.
62 Applicable only for Root Complex controllers. PTM context is
|
| H A 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/Documentation/devicetree/bindings/mmc/ |
| H A 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
|
| H A 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.
|
| H A 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/drivers/net/can/spi/ |
| H A 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/arch/arm64/boot/dts/st/ |
| H A D | stm32mp251.dtsi | 246 access-controllers = <&rifsc 111>;
263 access-controllers = <&rifsc 74>;
279 access-controllers = <&rifsc 75>;
303 access-controllers = <&rifsc 1>;
334 access-controllers = <&rifsc 2>;
365 access-controllers = <&rifsc 3>;
396 access-controllers = <&rifsc 4>;
427 access-controllers = <&rifsc 5>;
452 access-controllers = <&rifsc 6>;
477 access-controllers
[all...] |
| H A D | stm32mp231.dtsi | 238 access-controllers = <&rifsc 23>;
253 access-controllers = <&rifsc 23>;
268 access-controllers = <&rifsc 24>;
283 access-controllers = <&rifsc 24>;
297 access-controllers = <&rifsc 30>;
309 access-controllers = <&rifsc 32>;
321 access-controllers = <&rifsc 33>;
333 access-controllers = <&rifsc 34>;
345 access-controllers = <&rifsc 35>;
361 access-controllers
[all...] |
| H A D | stm32mp255.dtsi | 14 access-controllers = <&rifsc 89>;
23 access-controllers = <&rifsc 90>;
|
| /linux/drivers/mux/ |
| H A D | core.c | 79 * @controllers: The number of mux controllers to allocate for this chip.
82 * After allocating the mux-chip with the desired number of mux controllers
93 unsigned int controllers, size_t sizeof_priv) in mux_chip_alloc() argument
98 if (WARN_ON(!dev || !controllers)) in mux_chip_alloc()
101 mux_chip = kzalloc(size_add(struct_size(mux_chip, mux, controllers), in mux_chip_alloc()
123 mux_chip->controllers = controllers; in mux_chip_alloc()
124 for (i = 0; i < controllers; ++i) { in mux_chip_alloc()
152 * mux_chip_register() - Register a mux-chip, thus readying the controllers
235 devm_mux_chip_alloc(struct device * dev,unsigned int controllers,size_t sizeof_priv) devm_mux_chip_alloc() argument
[all...] |
| H A D | adg792a.c | 39 if (mux->chip->controllers == 1) { in adg792a_set()
91 mux_chip->controllers); in adg792a_probe()
98 for (i = 0; i < mux_chip->controllers; ++i) { in adg792a_probe()
|
| /linux/Documentation/input/devices/ |
| H A 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.
95 All generations of Xbox controllers speak USB over the wire.
97 - Original Xbox controllers use a proprietary connector and require adapters.
98 - Wireless Xbox 360 controllers requir
[all...] |
| /linux/drivers/dma/lgm/ |
| H A 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/Documentation/PCI/endpoint/ |
| H A 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/
|
| H A D | pci-ntb-howto.rst | 31 # ls /sys/kernel/config/pci_ep/controllers
111 NTB function device should be attached to two PCI endpoint controllers
117 # ln -s controllers/2900000.pcie-ep/ functions/pci-epf-ntb/func1/primary
118 # ln -s controllers/2910000.pcie-ep/ functions/pci-epf-ntb/func1/secondary
120 Once the above step is completed, both the PCI endpoint controllers are ready to
128 field should be populated with '1'. For NTB, both the PCI endpoint controllers
131 # echo 1 > controllers/2900000.pcie-ep/start
132 # echo 1 > controllers/2910000.pcie-ep/start
|
| H A D | pci-vntb-howto.rst | 28 # ls /sys/kernel/config/pci_ep/controllers
112 NTB function device should be attached to PCI endpoint controllers
115 # ln -s controllers/5f010000.pcie_ep functions/pci-epf-ntb/func1/primary
117 Once the above step is completed, the PCI endpoint controllers are ready to
125 field should be populated with '1'. For NTB, both the PCI endpoint controllers
128 # echo 1 > controllers/5f010000.pcie_ep/start
|
| /linux/drivers/ata/ |
| H A D | Kconfig | 159 controllers.
363 This option adds support for ATA controllers with SFF
367 the dawn of time. Almost all PATA controllers have an
368 SFF interface. Many SATA controllers have an SFF interface
371 For users with exclusively modern controllers like AHCI,
379 comment "SFF controllers with custom DMA interface"
385 This option enables support for Pacific Digital ADMA controllers
422 This option adds support for SFF ATA controllers with BMDMA
424 de facto DMA interface for SFF controllers.
430 comment "SATA SFF controllers wit
[all...] |
| /linux/drivers/mtd/nand/raw/ |
| H A D | cs553x_nand.c | 238 static struct cs553x_nand_controller *controllers[4]; variable
313 controllers[cs] = controller; in cs553x_init_one()
376 if (controllers[i]) { in cs553x_init()
378 mtd_device_register(nand_to_mtd(&controllers[i]->chip), in cs553x_init()
394 struct cs553x_nand_controller *controller = controllers[i]; in cs553x_cleanup()
407 controllers[i] = NULL; in cs553x_cleanup()
|
| /linux/Documentation/devicetree/bindings/interrupt-controller/ |
| H A 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/Documentation/devicetree/bindings/usb/ |
| H A 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
|
| /linux/drivers/hsi/controllers/ |
| H A D | Kconfig | 3 # HSI controllers configuration
5 comment "HSI controllers"
|
| /linux/drivers/phy/qualcomm/ |
| H A D | Kconfig | 69 with USB3 and DisplayPort controllers on Qualcomm chips.
78 with PCIe controllers on Qualcomm chips.
87 with PCIe controllers on Qualcomm msm8996 chips.
95 with UFS controllers on Qualcomm chips.
103 with USB3 controllers on Qualcomm chips.
124 controllers on Qualcomm chips. This driver supports the high-speed
157 is used with PCIe controllers on Qualcomm IPQ5332 chips. It
225 both HS and SS PHY controllers.
|
| /linux/Documentation/arch/xtensa/ |
| H A D | atomctl.rst | 26 use the memory controllers RCW, though non-MX controllers likely
30 Virtually all customers buy their memory controllers from vendors that
|
| /linux/drivers/gpu/drm/armada/ |
| H A D | Kconfig | 9 Support the "LCD" controllers found on the Marvell Armada 510
10 devices. There are two controllers on the device, each controller
|