Home
last modified time | relevance | path

Searched refs:controllers (Results 1 – 25 of 708) sorted by relevance

12345678910>>...29

/linux/Documentation/devicetree/bindings/access-controllers/
A Daccess-controllers.yaml4 $id: http://devicetree.org/schemas/access-controllers/access-controllers.yaml#
13 Common access controllers properties
31 Access controllers are typically used to set/read the permissions of a
36 Each node can be a consumer for the several access controllers.
44 Number of cells in an access-controllers specifier;
51 A list of access-controllers names, sorted in the same order as
52 access-controllers entries. Consumer drivers will use
55 access-controllers:
59 bindings of the access-controllers provider.
65 clock_controller: access-controllers@50000 {
[all …]
/linux/arch/arm/boot/dts/st/
A Dstm32mp151.dtsi443 access-controllers = <&etzpc 16>;
480 access-controllers = <&etzpc 17>;
515 access-controllers = <&etzpc 18>;
552 access-controllers = <&etzpc 19>;
584 access-controllers = <&etzpc 20>;
605 access-controllers = <&etzpc 21>;
624 access-controllers = <&etzpc 22>;
649 access-controllers = <&etzpc 23>;
674 access-controllers = <&etzpc 24>;
699 access-controllers = <&etzpc 25>;
[all …]
/linux/Documentation/devicetree/bindings/mmc/
A Dsdhci-omap.txt8 - 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
A Dk3-dw-mshc.txt15 - "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.
A Dti-omap-hsmmc.txt12 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/
A DKconfig6 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/include/linux/mux/
A Ddriver.h65 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,
/linux/drivers/mux/
A Dcore.c93 unsigned int controllers, size_t sizeof_priv) in mux_chip_alloc() argument
98 if (WARN_ON(!dev || !controllers)) in mux_chip_alloc()
102 controllers * sizeof(*mux_chip->mux) + in mux_chip_alloc()
124 mux_chip->controllers = controllers; in mux_chip_alloc()
125 for (i = 0; i < controllers; ++i) { in mux_chip_alloc()
168 for (i = 0; i < mux_chip->controllers; ++i) { in mux_chip_register()
236 unsigned int controllers, in devm_mux_chip_alloc() argument
245 mux_chip = mux_chip_alloc(dev, controllers, sizeof_priv); in devm_mux_chip_alloc()
575 (args.args_count < 2 && mux_chip->controllers > 1)) { in mux_get()
591 (!args.args_count && mux_chip->controllers > 1)) { in mux_get()
[all …]
/linux/Documentation/devicetree/bindings/i2c/
A Dnvidia,tegra20-i2c.yaml39 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
/linux/Documentation/devicetree/bindings/phy/
A Drealtek,usb3phy.yaml16 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.
A Drealtek,usb2phy.yaml16 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.
/linux/arch/arm64/boot/dts/st/
A Dstm32mp251.dtsi248 access-controllers = <&rifsc 23>;
260 access-controllers = <&rifsc 24>;
269 access-controllers = <&rifsc 32>;
278 access-controllers = <&rifsc 33>;
287 access-controllers = <&rifsc 34>;
296 access-controllers = <&rifsc 35>;
309 access-controllers = <&rifsc 41>;
322 access-controllers = <&rifsc 42>;
335 access-controllers = <&rifsc 43>;
348 access-controllers = <&rifsc 44>;
[all …]
/linux/Documentation/input/devices/
A Dxpad.rst2 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.
100 - Wired Xbox 360 controllers use standard USB connectors.
101 - Xbox One controllers can be wireless but speak Wi-Fi Direct and are not
176 Unrecognized models of Xbox controllers should function as Generic
[all …]
/linux/drivers/dma/lgm/
A DKconfig3 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/ABI/testing/
A Dsysfs-bus-pci-drivers-ehci_hcd7 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/usb/
A Dusb-drd.yaml25 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
34 Tells OTG controllers we want to disable OTG HNP. Normally HNP is the
41 Tells OTG controllers we want to disable OTG SRP. SRP is optional for OTG
47 Tells OTG controllers we want to disable OTG ADP. ADP is optional for OTG
A Dusb.yaml37 Tells USB controllers that we want to configure the core to support a
41 selected. In case this isn't passed via DT, USB controllers should
48 Tells USB controllers we want to work up to a certain speed. In case this
49 isn't passed via DT, USB controllers should default to their maximum HW
A Dpxa-usb.txt1 PXA USB controllers
6 - compatible: Should be "marvell,pxa-ohci" for USB controllers
35 - compatible: Should be "marvell,pxa270-udc" for USB controllers
/linux/Documentation/PCI/endpoint/
A Dpci-endpoint-cfs.rst25 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/
A Dpci-ntb-howto.rst31 # 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
/linux/drivers/ata/
A DKconfig143 controllers.
414 comment "SATA SFF controllers with BMDMA"
423 host controllers.
555 comment "PATA SFF controllers with BMDMA"
608 controllers.
721 controllers via the new ATA layer.
730 PATA controllers via the new ATA layer
887 PATA controllers via the new ATA layer
994 comment "PIO-only SFF controllers"
1135 PATA controllers via the new ATA layer
[all …]
/linux/Documentation/devicetree/bindings/memory-controllers/
A Drenesas,dbsc.yaml4 $id: http://devicetree.org/schemas/memory-controllers/renesas,dbsc.yaml#
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/Documentation/devicetree/bindings/memory-controllers/ddr/
A Djedec,lpddr-channel.yaml4 $id: http://devicetree.org/schemas/memory-controllers/ddr/jedec,lpddr-channel.yaml#
71 $ref: /schemas/memory-controllers/ddr/jedec,lpddr2.yaml#
80 $ref: /schemas/memory-controllers/ddr/jedec,lpddr3.yaml#
89 $ref: /schemas/memory-controllers/ddr/jedec,lpddr4.yaml#
98 $ref: /schemas/memory-controllers/ddr/jedec,lpddr5.yaml#
/linux/drivers/mtd/nand/raw/
A Dcs553x_nand.c238 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/
A Dmsi.txt1 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.

Completed in 41 milliseconds

12345678910>>...29