Home
last modified time | relevance | path

Searched +full:usb +full:- +full:controller (Results 1 – 25 of 1101) sorted by relevance

12345678910>>...45

/Linux-v6.1/drivers/usb/host/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
3 # USB Host Controller Drivers
5 comment "USB Host Controller Drivers"
11 The Cypress C67x00 (EZ-Host/EZ-OTG) chips are dual-role
12 host/peripheral/OTG USB controllers.
14 Enable this option to support this chip in host controller mode.
21 tristate "xHCI HCD (USB 3.0) support"
24 The eXtensible Host Controller Interface (xHCI) is standard for USB 3.0
25 "SuperSpeed" host controller hardware.
28 module will be called xhci-hcd.
[all …]
Dehci-xilinx-of.c1 // SPDX-License-Identifier: GPL-2.0+
3 * EHCI HCD (Host Controller Driver) for USB.
9 * Based on "ehci-ppc-of.c" by Valentine Barshak <vbarshak@ru.mvista.com>
10 * and "ehci-ppc-soc.c" by Stefan Roese <sr@denx.de>
11 * and "ohci-ppc-of.c" by Sylvain Munaut <tnt@246tNt.com>
23 * ehci_xilinx_port_handed_over - hand the port out if failed to enable it
24 * @hcd: Pointer to the usb_hcd device to which the host controller bound
27 * This function is used as a place to tell the user that the Xilinx USB host
28 * controller does support LS devices. And in an HS only configuration, it
32 * There are cases when the host controller fails to enable the port due to,
[all …]
/Linux-v6.1/drivers/usb/gadget/udc/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
3 # USB Gadget support on a system involves
4 # (a) a peripheral controller, and
7 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
9 # - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
10 # - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
11 # - Some systems have both kinds of controllers.
13 # With help from a special transceiver and a "Mini-AB" jack, systems with
14 # both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
18 # USB Peripheral Controller Support
[all …]
/Linux-v6.1/drivers/usb/typec/tcpm/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
4 tristate "USB Type-C Port Controller Manager"
5 depends on USB
9 The Type-C Port Controller Manager provides a USB PD and USB Type-C
10 state machine for use with Type-C Port Controllers.
15 tristate "Type-C Port Controller Interface driver"
19 Type-C Port Controller driver for TCPCI-compliant controller.
24 tristate "Richtek RT1711H Type-C chip driver"
26 Richtek RT1711H Type-C chip driver that works with
27 Type-C Port Controller Manager to provide USB PD and USB
[all …]
/Linux-v6.1/drivers/clk/qcom/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
40 tristate "MSM8916 APCS Clock Controller"
43 Support for the APCS Clock Controller on msm8916 devices. The
49 tristate "MSM8996 CPU Clock Controller"
53 Support for the CPU clock controller on msm8996 devices.
58 tristate "SDX55 and SDX65 APCS Clock Controller"
61 Support for the APCS Clock Controller on SDX55, SDX65 platforms. The
67 tristate "RPM based Clock Controller"
80 tristate "RPM over SMD based Clock Controller"
102 tristate "APQ8084 Global Clock Controller"
[all …]
/Linux-v6.1/drivers/usb/typec/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
4 tristate "USB Type-C Support"
6 USB Type-C Specification defines a cable and connector for USB where
8 be Type-A plug on one end of the cable and Type-B plug on the other.
9 Determination of the host-to-device relationship happens through a
10 specific Configuration Channel (CC) which goes through the USB Type-C
12 Accessory Modes - Analog Audio and Debug - and if USB Power Delivery
14 something else then USB communication.
16 USB Power Delivery Specification defines a protocol that can be used
18 partners. USB Power Delivery allows higher voltages then the normal
[all …]
/Linux-v6.1/Documentation/driver-api/usb/
Dwriting_musb_glue_layer.rst10 The Linux MUSB subsystem is part of the larger Linux USB subsystem. It
11 provides support for embedded USB Device Controllers (UDC) that do not
12 use Universal Host Controller Interface (UHCI) or Open Host Controller
15 Instead, these embedded UDC rely on the USB On-the-Go (OTG)
17 reference design used in most cases is the Multipoint USB Highspeed
18 Dual-Role Controller (MUSB HDRC) found in the Mentor Graphics Inventra™
21 As a self-taught exercise I have written an MUSB glue layer for the
24 ``drivers/usb/musb/jz4740.c``. In this documentation I will walk through the
28 .. _musb-basics:
33 To get started on the topic, please read USB On-the-Go Basics (see
[all …]
Dgadget.rst2 USB Gadget API for Linux
11 This document presents a Linux-USB "Gadget" kernel mode API, for use
12 within peripherals and other USB devices that embed Linux. It provides
17 - Supports USB 2.0, for high speed devices which can stream data at
20 - Handles devices with dozens of endpoints just as well as ones with
21 just two fixed-function ones. Gadget drivers can be written so
24 - Flexible enough to expose more complex USB device capabilities such
28 - USB "On-The-Go" (OTG) support, in conjunction with updates to the
29 Linux-USB host side.
31 - Sharing data structures and API models with the Linux-USB host side
[all …]
/Linux-v6.1/drivers/usb/usbip/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
4 tristate "USB/IP support"
9 This enables pushing USB packets over IP to allow remote
10 machines direct access to USB devices. It provides the
11 USB/IP core that is required by both drivers.
17 be called usbip-core.
23 depends on USBIP_CORE && USB
25 This enables the USB/IP virtual host controller driver,
29 module will be called vhci-hcd.
32 int "Number of ports per USB/IP virtual host controller"
[all …]
/Linux-v6.1/Documentation/usb/
Dehci.rst5 27-Dec-2002
7 The EHCI driver is used to talk to high speed USB 2.0 devices using
8 USB 2.0-capable host controller hardware. The USB 2.0 standard is
9 compatible with the USB 1.1 standard. It defines three transfer speeds:
11 - "High Speed" 480 Mbit/sec (60 MByte/sec)
12 - "Full Speed" 12 Mbit/sec (1.5 MByte/sec)
13 - "Low Speed" 1.5 Mbit/sec
15 USB 1.1 only addressed full speed and low speed. High speed devices
16 can be used on USB 1.1 systems, but they slow down to USB 1.1 speeds.
18 USB 1.1 devices may also be used on USB 2.0 systems. When plugged
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/phy/
Dmarvell,armada-cp110-utmi-phy.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: "http://devicetree.org/schemas/phy/marvell,armada-cp110-utmi-phy.yaml#"
6 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
11 - Konstantin Porotchkin <kostap@marvell.com>
14 On Armada 7k/8k and CN913x, there are two host and one device USB controllers.
15 Each of two exiting UTMI PHYs could be connected to either USB host or USB device
16 controller.
17 The USB device controller can only be connected to a single UTMI PHY port
18 0.H----- USB HOST0
[all …]
Dallwinner,sun8i-h3-usb-phy.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/phy/allwinner,sun8i-h3-usb-phy.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Allwinner H3 USB PHY
10 - Chen-Yu Tsai <wens@csie.org>
11 - Maxime Ripard <mripard@kernel.org>
14 "#phy-cells":
19 - allwinner,sun8i-h3-usb-phy
20 - allwinner,sun50i-h616-usb-phy
[all …]
/Linux-v6.1/sound/usb/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
2 # ALSA USB drivers
5 bool "USB sound devices"
6 depends on USB
9 Support for sound devices connected via the USB bus.
11 if SND_USB && USB
14 tristate "USB Audio/MIDI driver"
21 Say Y here to include support for USB audio and USB MIDI
25 will be called snd-usb-audio.
31 tristate "Edirol UA-101/UA-1000 driver"
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/usb/
Dam33xx-usb.txt3 - compatible: ti,am33xx-usb
4 - reg: offset and length of the usbss register sets
5 - ti,hwmods : must be "usb_otg_hs"
8 at least a control module node, USB node and a PHY node. The second USB
13 - compatible: ti,am335x-usb-ctrl-module
14 - reg: offset and length of the "USB control registers" in the "Control
15 Module" block. A second offset and length for the USB wake up control
17 - reg-names: "phy_ctrl" for the "USB control registers" and "wakeup" for
18 the USB wake up control register.
20 USB PHY
[all …]
Dmsm-hsusb.txt6 - compatible: Should contain "qcom,ehci-host"
7 - regs: offset and length of the register set in the memory map
8 - usb-phy: phandle for the PHY device
10 Example EHCI controller device node:
13 compatible = "qcom,ehci-host";
15 usb-phy = <&usb_otg>;
18 USB PHY with optional OTG:
21 - compatible: Should contain:
22 "qcom,usb-otg-ci" for chipsets with ChipIdea 45nm PHY
23 "qcom,usb-otg-snps" for chipsets with Synopsys 28nm PHY
[all …]
Dfsl-usb.txt1 Freescale SOC USB controllers
3 The device node for a USB controller that is part of a Freescale
9 - compatible : Should be "fsl-usb2-mph" for multi port host USB
10 controllers, or "fsl-usb2-dr" for dual role USB controllers
11 or "fsl,mpc5121-usb2-dr" for dual role USB controllers of MPC5121.
12 Wherever applicable, the IP version of the USB controller should
13 also be mentioned (for eg. fsl-usb2-dr-v2.2 for bsc9132).
14 - phy_type : For multi port host USB controllers, should be one of
15 "ulpi", or "serial". For dual role USB controllers, should be
17 - reg : Offset and length of the register set for the device
[all …]
Ds3c2410-usb.txt1 Samsung S3C2410 and compatible SoC USB controller
6 - compatible: should be "samsung,s3c2410-ohci" for USB host controller
7 - reg: address and length of the controller memory mapped region
8 - interrupts: interrupt number for the USB OHCI controller
9 - clocks: Should reference the bus and host clocks
10 - clock-names: Should contain two strings
11 "usb-bus-host" for the USB bus clock
12 "usb-host" for the USB host clock
17 compatible = "samsung,s3c2410-ohci";
21 clock-names = "usb-bus-host", "usb-host";
Dnvidia,tegra124-xusb.txt1 NVIDIA Tegra xHCI controller
4 The Tegra xHCI controller supports both USB2 and USB3 interfaces exposed by
5 the Tegra XUSB pad controller.
8 --------------------
9 - compatible: Must be:
10 - Tegra124: "nvidia,tegra124-xusb"
11 - Tegra132: "nvidia,tegra132-xusb", "nvidia,tegra124-xusb"
12 - Tegra210: "nvidia,tegra210-xusb"
13 - Tegra186: "nvidia,tegra186-xusb"
14 - reg: Must contain the base and length of the xHCI host registers, XUSB FPCI
[all …]
/Linux-v6.1/drivers/usb/misc/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
3 # USB Miscellaneous driver configuration
5 comment "USB Miscellaneous drivers"
8 tristate "EMI 6|2m USB Audio interface support"
10 This driver loads firmware to Emagic EMI 6|2m low latency USB
14 USB Audio driver.
22 tristate "EMI 2|6 USB Audio interface support"
24 This driver loads firmware to Emagic EMI 2|6 low latency USB
28 USB Audio driver.
43 tristate "USB 7-Segment LED Display"
[all …]
/Linux-v6.1/drivers/hid/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
15 most commonly used to refer to the USB-HID specification, but other
20 removed from the HID bus by the transport-layer drivers, such as
23 For docs and specs, see https://www.usb.org/developers/hidpage/
41 Say Y here if you want to support HID devices (from the USB
48 There is also a /dev/hiddev configuration option in the USB HID
51 to work on raw hid events when they want to, and avoid using transport-specific
57 tristate "User-space I/O driver support for HID subsystem"
60 Say Y here if you want to provide HID I/O Drivers from user-space.
61 This allows to write I/O drivers in user-space and feed the data from
[all …]
/Linux-v6.1/drivers/usb/cdns3/
DKconfig2 tristate "Cadence USB Support"
3 depends on USB_SUPPORT && (USB || USB_GADGET) && HAS_DMA
8 dual-role controller.
9 It supports: dual-role switch, Host-only, and Peripheral-only.
17 tristate "Cadence USB3 Dual-Role Controller"
20 Say Y here if your system has a Cadence USB3 dual-role controller.
21 It supports: dual-role switch, Host-only, and Peripheral-only.
30 bool "Cadence USB3 device controller"
33 Say Y here to enable device controller functionality of the
34 Cadence USBSS-DEV driver.
[all …]
/Linux-v6.1/drivers/phy/st/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
14 tristate "ST SPEAR1310-MIPHY driver"
21 tristate "ST SPEAR1340-MIPHY driver"
37 tristate "STMicroelectronics STM32 USB HS PHY Controller driver"
42 Enable this to support the High-Speed USB transceivers that are part
45 This driver controls the entire USB PHY block: the USB PHY controller
46 (USBPHYC) and the two 8-bit wide UTMI+ interfaces. First interface is
47 used by an HS USB Host controller, and the second one is shared
48 between an HS USB OTG controller and an HS USB Host controller,
49 selected by a USB switch.
/Linux-v6.1/Documentation/devicetree/bindings/dma/
Drenesas,usb-dmac.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/dma/renesas,usb-dmac.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Renesas USB DMA Controller
10 - Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
13 - $ref: "dma-controller.yaml#"
18 - enum:
19 - renesas,r8a7742-usb-dmac # RZ/G1H
20 - renesas,r8a7743-usb-dmac # RZ/G1M
[all …]
Dstericsson,dma40.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: ST-Ericsson DMA40 DMA Engine
10 - Linus Walleij <linus.walleij@linaro.org>
13 - $ref: "dma-controller.yaml#"
16 "#dma-cells":
22 0: SPI controller 0
23 1: SD/MMC controller 0 (unused)
24 2: SD/MMC controller 1 (unused)
[all …]
/Linux-v6.1/Documentation/ABI/testing/
Dsysfs-class-uwb_rc4 Contact: linux-usb@vger.kernel.org
9 Familiarity with the ECMA-368 'High Rate Ultra
24 Contact: linux-usb@vger.kernel.org
26 An individual UWB radio controller.
31 Contact: linux-usb@vger.kernel.org
38 or, if <channel> is -1, to prohibit beaconing. If
41 radio controller's supported band groups.
43 Reading returns the currently active channel, or -1 if
44 the radio controller is not beaconing.
49 Contact: linux-usb@vger.kernel.org
[all …]

12345678910>>...45