Home
last modified time | relevance | path

Searched full:controllers (Results 1 – 25 of 1409) sorted by relevance

12345678910>>...57

/linux/Documentation/devicetree/bindings/access-controllers/
H A Daccess-controllers.yaml4 $id: http://devicetree.org/schemas/access-controllers/access-controllers.yaml#
7 title: Generic Domain Access Controllers
13 Common access controllers properties
15 Access controllers are in charge of stating which of the hardware blocks under
22 controller provided by access-controllers property. In this case, the device
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
[all …]
/linux/Documentation/input/devices/
H 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.
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/Documentation/devicetree/bindings/i2c/
H 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
84 Tegra256 has 8 generic I2C controllers. The controllers are similar to
[all …]
/linux/Documentation/ABI/testing/
H A Ddebugfs-pcie-ptm6 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 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/include/linux/mux/
H A Ddriver.h57 * 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/devicetree/bindings/phy/
H 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.
H 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.
/linux/tools/testing/selftests/bpf/
H A Dcgroup_helpers.c60 static int __enable_controllers(const char *cgroup_path, const char *controllers) in __enable_controllers() argument
68 /* If not controllers are passed, enable all available controllers */ in __enable_controllers()
69 if (!controllers) { in __enable_controllers()
70 snprintf(path, sizeof(path), "%s/cgroup.controllers", in __enable_controllers()
74 log_err("Opening cgroup.controllers: %s", path); in __enable_controllers()
80 log_err("Reading cgroup.controllers: %s", path); in __enable_controllers()
82 } else if (len == 0) { /* No controllers to enable */ in __enable_controllers()
89 bpf_strlcpy(enable, controllers, sizeof(enable)); in __enable_controllers()
111 * enable_controllers() - Enable cgroup v2 controllers
121 enable_controllers(const char * relative_path,const char * controllers) enable_controllers() argument
[all...]
/linux/include/linux/
H A Dreset.h292 * multiple reset controllers.
331 * controllers.
352 * reset controllers.
401 * multiple reset controllers.
602 * Managed reset_control_get_exclusive(). For reset controllers returned
623 * controllers returned from this function, reset_control_assert() +
641 * Managed reset_control_bulk_get_exclusive(). For reset controllers returned
661 * Managed reset_control_get_exclusive_released(). For reset controllers
681 * Managed reset_control_bulk_get_exclusive_released(). For reset controllers
702 * reset controllers returned from this function, reset_control_put() is called
[all …]
/linux/drivers/phy/qualcomm/
H A DKconfig69 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/drivers/net/can/spi/
H 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/Documentation/PCI/endpoint/
H 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/mux/
H A Dcore.c79 * @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...]
/linux/drivers/usb/gadget/udc/
H A DKconfig11 # - 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
117 speed USB device controllers, with support for up to 30
119 controller in the OMAP 1611, and should work with controllers
255 # Controllers available in both integrated and discrete versions
273 # Controllers available only in discrete form (and all PCI controllers)
303 controllers having QE or CPM2, given minor tweaks.
[all …]
/linux/Documentation/devicetree/bindings/usb/
H 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
H 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
/linux/Documentation/devicetree/bindings/interrupt-controller/
H 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.
/linux/drivers/input/joystick/
H A Dxpad.c124 MODULE_PARM_DESC(auto_poweroff, "Power off wireless controllers on suspend");
441 /* original xbox controllers only */
495 * wireless controllers have protocol 129.
524 XPAD_XBOX360_VENDOR(0x0351), /* CRKD Controllers */
526 XPAD_XBOX360_VENDOR(0x03f0), /* HP HyperX Xbox 360 controllers */
527 XPAD_XBOXONE_VENDOR(0x03f0), /* HP HyperX Xbox One controllers */
528 XPAD_XBOX360_VENDOR(0x044f), /* Thrustmaster Xbox 360 controllers */
529 XPAD_XBOXONE_VENDOR(0x044f), /* Thrustmaster Xbox One controllers */
530 XPAD_XBOX360_VENDOR(0x045e), /* Microsoft Xbox 360 controllers */
531 XPAD_XBOXONE_VENDOR(0x045e), /* Microsoft Xbox One controllers */
[all...]
/linux/Documentation/devicetree/bindings/memory-controllers/
H A Drenesas,dbsc.yaml4 $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/Documentation/devicetree/bindings/mmc/
H 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/pci/controller/
H A Dpcie-iproc.h11 * @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/drivers/dma/lgm/
H 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/driver-api/
H A Dedac.rst120 Memory Controllers
125 to describe the memory controllers, with is an opaque struct for the EDAC
132 PCI Controllers
135 The EDAC subsystem provides a mechanism to handle PCI controllers by calling
137 :c:type:`edac_pci_ctl_info` to describe the PCI controllers.
159 - PCIe interface controllers
199 and each GPU data fabric contains four Unified Memory Controllers (UMC).
207 Memory controllers on AMD GPU nodes can be represented in EDAC thusly:
/linux/tools/testing/selftests/devices/probe/boards/
H A Dgoogle,spherion.yaml7 # The top-level is a list of controllers, either for USB or PCI(e).
16 # sibling controllers. In this case, dt-mmio can't be used, and this property
18 # - usb-version: for USB controllers to differentiate between USB3 and USB2
21 # distinguish between multiple PCI host controllers.

12345678910>>...57