| /openbmc/u-boot/drivers/usb/host/ |
| H A D | Kconfig | 2 # USB Host Controller Drivers
4 comment "USB Host Controller Drivers"
10 bool "xHCI HCD (USB 3.0) support"
12 ---help---
13 The eXtensible Host Controller Interface (xHCI) is standard for USB 3.0
14 "SuperSpeed" host controller hardware.
22 USB controller based on the DesignWare USB3 IP Core.
30 USB controller based on the DesignWare USB3 IP Core.
33 bool "MVEBU USB 3.0 support"
38 Choose this option to add support for USB 3.0 driver on mvebu
[all …]
|
| /openbmc/linux/drivers/usb/gadget/udc/ |
| H A D | Kconfig | 1 # 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 …]
|
| /openbmc/linux/drivers/usb/host/ |
| H A D | Kconfig | 1 # 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 …]
|
| H A D | ehci-xilinx-of.c | 1 // 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 …]
|
| /openbmc/linux/Documentation/devicetree/bindings/phy/ |
| H A D | realtek,usb2phy.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Realtek DHC SoCs USB 2.0 PHY
11 - Stanley Chang <stanley_chang@realtek.com>
14 Realtek USB 2.0 PHY support the digital home center (DHC) RTD series SoCs.
15 The USB 2.0 PHY driver is designed to support the XHCI controller. The SoCs
17 controller.
19 RTD1295/RTD1619 SoCs USB
20 The USB architecture includes three XHCI controllers.
[all …]
|
| H A D | realtek,usb3phy.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Realtek DHC SoCs USB 3.0 PHY
11 - Stanley Chang <stanley_chang@realtek.com>
14 Realtek USB 3.0 PHY support the digital home center (DHC) RTD series SoCs.
15 The USB 3.0 PHY driver is designed to support the XHCI controller. The SoCs
17 controller.
19 RTD1295/RTD1619 SoCs USB
20 The USB architecture includes three XHCI controllers.
[all …]
|
| H A D | marvell,armada-cp110-utmi-phy.yaml | 1 # 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 …]
|
| H A D | allwinner,sun8i-h3-usb-phy.yaml | 1 # 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 …]
|
| /openbmc/linux/drivers/usb/typec/tcpm/ |
| H A D | Kconfig | 1 # 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 …]
|
| /openbmc/linux/drivers/usb/typec/ |
| H A D | Kconfig | 1 # 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 …]
|
| /openbmc/linux/drivers/clk/qcom/ |
| H A D | Kconfig | 1 # 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"
54 Support for the CPU clock controller on msm8996 devices.
59 tristate "SDX55 and SDX65 APCS Clock Controller"
63 Support for the APCS Clock Controller on SDX55, SDX65 platforms. The
69 tristate "RPM based Clock Controller"
82 tristate "RPM over SMD based Clock Controller"
104 tristate "APQ8084 Global Clock Controller"
[all …]
|
| /openbmc/u-boot/drivers/usb/gadget/ |
| H A D | Kconfig | 2 # USB Gadget support on a system involves
3 # (a) a peripheral controller, and
6 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
8 # - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
9 # - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
10 # - Some systems have both kinds of controllers.
12 # With help from a special transceiver and a "Mini-AB" jack, systems with
13 # both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
17 bool "USB Gadget Support"
19 USB is a master/slave protocol, organized with one master
[all …]
|
| /openbmc/qemu/docs/system/devices/ |
| H A D | usb.rst | 1 USB emulation
2 -------------
4 QEMU can emulate a PCI UHCI, OHCI, EHCI or XHCI USB controller. You can
5 plug virtual USB devices or real host USB devices (only works with
7 connect virtual USB hubs as necessary to connect multiple USB devices.
9 USB controllers
12 XHCI controller support
16 more virtualization-friendly when compared to EHCI and UHCI, thus XHCI
21 |qemu_system| -device qemu-xhci
23 XHCI supports USB 1.1, USB 2.0 and USB 3.0 devices, so this is the
[all …]
|
| /openbmc/linux/Documentation/driver-api/usb/ |
| H A D | writing_musb_glue_layer.rst | 10 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 …]
|
| H A D | gadget.rst | 2 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 …]
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | usb-info.txt | 1 How USB works with driver model
5 ------------
7 Driver model USB support makes use of existing features but changes how
9 understand how things work with USB in U-Boot when driver model is enabled.
12 Enabling driver model for USB
13 -----------------------------
15 A new CONFIG_DM_USB option is provided to enable driver model for USB. This
16 causes the USB uclass to be included, and drops the equivalent code in
17 usb.c. In particular the usb_init() function is then implemented by the
22 -------------------------
[all …]
|
| /openbmc/linux/drivers/usb/usbip/ |
| H A D | Kconfig | 1 # 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 …]
|
| /openbmc/u-boot/drivers/usb/musb-new/ |
| H A D | Kconfig | 2 # MUSB Controller Driver
4 comment "MUSB Controller Driver"
11 Enables the MUSB USB dual-role controller in host mode.
19 Enables the MUSB USB dual-role controller in gadget mode.
22 bool "Enable TI OTG USB controller"
27 speed USB controller based on the Mentor Graphics
43 bool "Enable Microchip PIC32 DRC USB controller"
46 Say y to enable PIC32 USB DRC controller support
50 bool "Enable sunxi OTG / DRC USB controller"
53 ---help---
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | USBController.v1_0_1.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
37 …"longDescription": "This Redfish Specification-described type shall contain links to resources tha…
39 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
56 …operties contained in this object shall conform to the Redfish Specification-described requirement…
60 "description": "A link to the PCIe device that represents this USB controller.",
61 …erty shall contain a link to a resource of type `PCIeDevice` that represents this USB controller.",
[all …]
|
| /openbmc/linux/Documentation/usb/ |
| H A D | ehci.rst | 5 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 …]
|
| /openbmc/linux/sound/usb/ |
| H A D | Kconfig | 1 # 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"
22 Say Y here to include support for USB audio and USB MIDI
26 will be called snd-usb-audio.
29 bool "MIDI 2.0 support by USB Audio driver"
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/usb/ |
| H A D | am33xx-usb.txt | 3 - 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 …]
|
| H A D | msm-hsusb.txt | 6 - 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 …]
|
| /openbmc/linux/drivers/usb/fotg210/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
4 tristate "Faraday FOTG210 USB2 Dual Role controller"
5 depends on USB || USB_GADGET
11 Faraday FOTG210 is a dual-mode USB controller that can act
12 in both host controller and peripheral controller mode.
17 bool "Faraday FOTG210 USB Host Controller support"
18 depends on USB=y || USB=USB_FOTG210
20 Faraday FOTG210 is an OTG controller which can be configured as
25 module will be called fotg210-hcd.
29 bool "Faraday FOTG210 USB Peripheral Controller support"
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.fsl-hwconfig | 1 Freescale-specific 'hwconfig' options.
3 This file documents Freescale-specific key:value pairs for the 'hwconfig'
13 will be programmed accordingly. Second, the clock-frequency property
23 usb
24 Specific to boards have USB controller
26 This option specifies the following for a USB controller:
28 - which controller mode to use
29 - which USB PHY to use
31 This is used by generic USB device-tree fixup function to update
32 modified values of phy type and controller mode.
[all …]
|