| /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
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
24 only controller you need. With only a single USB controller (and
[all …]
|
| /openbmc/linux/drivers/usb/serial/ |
| H A D | ftdi_sio_ids.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
3 * vendor/product IDs (VID/PID) of devices using FTDI USB serial converters.
6 * Philipp Gühring - pg@futureware.at - added the Device ID of the USB relais
17 #define FTDI_VID 0x0403 /* Vendor Id */
25 #define FTDI_4232H_PID 0x6011 /* Quad channel hi-speed device */
26 #define FTDI_232H_PID 0x6014 /* Single channel hi-speed device */
27 #define FTDI_FTX_PID 0x6015 /* FT-X series (FT201X, FT230X, FT231X, etc) */
28 #define FTDI_FT2233HP_PID 0x6040 /* Dual channel hi-speed device with PD */
29 #define FTDI_FT4233HP_PID 0x6041 /* Quad channel hi-speed device with PD */
30 #define FTDI_FT2232HP_PID 0x6042 /* Dual channel hi-speed device with PD */
[all …]
|
| H A D | belkin_sa.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */
3 * Definitions for Belkin USB Serial Adapter Driver
8 * This program is largely derived from work by the linux-usb group
9 * and associated source files. Please see the usb/serial files for
12 * See Documentation/usb/usb-serial.rst for more information on using this
15 * 12-Mar-2001 gkh
16 * Added GoHubs GO-COM232 device id.
18 * 06-Nov-2000 gkh
21 * 12-Oct-2000 William Greathouse
22 * First cut at supporting Belkin USB Serial Adapter F5U103
[all …]
|
| /openbmc/qemu/hw/usb/ |
| H A D | quirks-ftdi-ids.h | 2 * vendor/product IDs (VID/PID) of devices using FTDI USB serial converters.
5 * Philipp Gühring - pg@futureware.at - added the Device ID of the USB relais
16 #define FTDI_VID 0x0403 /* Vendor Id */
24 #define FTDI_4232H_PID 0x6011 /* Quad channel hi-speed device */
25 #define FTDI_232H_PID 0x6014 /* Single channel hi-speed device */
26 #define FTDI_FTX_PID 0x6015 /* FT-X series (FT201X, FT230X, FT231X, etc) */
27 #define FTDI_SIO_PID 0x8372 /* Product Id SIO application of 8U100AX */
28 #define FTDI_232RL_PID 0xFBFA /* Product ID for FT232RL */
31 /*** third-party PIDs (using FTDI_VID) ***/
37 * http://www.open-rd.org
[all …]
|
| H A D | bus.c | 2 #include "hw/qdev-properties.h"
3 #include "hw/usb.h"
5 #include "qapi/qapi-commands-machine.h"
6 #include "qapi/type-helpers.h"
7 #include "qemu/error-report.h"
22 DEFINE_PROP_STRING("port", USBDevice, port_path),
24 DEFINE_PROP_BIT("msos-desc", USBDevice, flags,
35 k->print_dev = usb_bus_dev_print; in usb_bus_class_init()
36 k->get_dev_path = usb_get_dev_path; in usb_bus_class_init()
37 k->get_fw_dev_path = usb_get_fw_dev_path; in usb_bus_class_init()
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-usb | 1 What: /sys/bus/usb/devices/<INTERFACE>/authorized
9 by writing INTERFACE to /sys/bus/usb/drivers_probe
10 This allows to avoid side-effects with drivers
15 What: /sys/bus/usb/devices/usbX/interface_authorized_default
22 What: /sys/bus/usb/device/.../authorized
28 drivers, non-authorized one are not. By default, wired
29 USB devices are authorized.
31 What: /sys/bus/usb/drivers/.../new_id
33 Contact: linux-usb@vger.kernel.org
35 Writing a device ID to this file will attempt to
[all …]
|
| /openbmc/linux/drivers/usb/typec/ |
| H A D | class.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * USB Type-C Connector Class
13 #include <linux/usb/pd_vdo.h>
14 #include <linux/usb/typec_mux.h>
15 #include <linux/usb/typec_retimer.h>
27 /* ------------------------------------------------------------------------- */
36 /* Product types defined in USB PD Specification R3.0 V2.0 */
64 return partner->identity; in get_pd_identity()
68 return cable->identity; in get_pd_identity()
75 struct typec_port *port = to_typec_port(dev->parent); in get_pd_product_type() local
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/usb/ |
| H A D | usb251xb.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/usb/usb251xb.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Microchip USB 2.0 Hi-Speed Hub Controller
10 - Richard Leitner <richard.leitner@skidata.com>
15 - microchip,usb2422
16 - microchip,usb2512b
17 - microchip,usb2512bi
18 - microchip,usb2513b
[all …]
|
| H A D | usb-device.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/usb-device.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Generic USB Device
10 - Greg Kroah-Hartman <gregkh@linuxfoundation.org>
13 Usually, we only use device tree for hard wired USB device.
15 http://www.devicetree.org/open-firmware/bindings/usb/usb-1_0.ps
17 Four types of device-tree nodes are defined: "host-controller nodes"
18 representing USB host controllers, "device nodes" representing USB devices,
[all …]
|
| H A D | amlogic,meson-g12a-usb-ctrl.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/usb/amlogic,meson-g12a-usb-ctrl.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Amlogic Meson G12A DWC3 USB SoC Controller Glue
11 - Neil Armstrong <neil.armstrong@linaro.org>
14 The Amlogic G12A embeds a DWC3 USB IP Core configured for USB2 and USB3
15 in host-only mode, and a DWC2 IP Core configured for USB2 peripheral mode
20 One of the USB2 PHYs can be re-routed in peripheral mode to a DWC2 USB IP.
23 connected to the Glue to serve as OTG ID change detection.
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/extcon/ |
| H A D | extcon-usbc-cros-ec.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/extcon/extcon-usbc-cros-ec.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: ChromeOS EC USB Type-C cable and accessories detection
10 - Benson Leung <bleung@chromium.org>
13 On ChromeOS systems with USB Type C ports, the ChromeOS Embedded Controller is
15 or USB devices when said accessories are attached or detached.
16 The node for this device must be under a cros-ec node like google,cros-ec-spi
17 or google,cros-ec-i2c.
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/connector/ |
| H A D | usb-connector.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/connector/usb-connector.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: USB Connector
10 - Rob Herring <robh@kernel.org>
13 A USB connector node represents a physical USB connector. It should be a child
14 of a USB interface controller or a separate node when it is attached to both
15 MUX and USB interface controller.
20 - enum:
[all …]
|
| /openbmc/qemu/docs/ |
| H A D | qdev-device-use.txt | 1 = How to convert to -device & friends =
7 -device parameter bus.
10 where this address can be configured, devices provide a bus-specific
16 SCSI scsi-id %u
19 virtio-serial-bus nr %u
20 ccid-bus slot %u
21 USB port %d(.%d)* (port.port...)
23 Example: device i440FX-pcihost is on the root bus, and provides a PCI
24 bus named pci.0. To put a FOO device into its slot 4, use -device
25 FOO,bus=/i440FX-pcihost/pci.0,addr=4. The abbreviated form bus=pci.0
[all …]
|
| /openbmc/linux/Documentation/usb/ |
| H A D | usb-serial.rst | 2 USB serial
8 The USB serial driver currently supports a number of different USB to
44 ConnectTech WhiteHEAT 4 port converter
45 --------------------------------------
57 HandSpring Visor, Palm USB, and Clié USB driver
58 -----------------------------------------------
60 This driver works with all HandSpring USB, Palm USB, and Sony Clié USB
64 up to the host as a valid USB device. When this happens, the device is
65 properly enumerated, assigned a port, and then communication _should_ be
72 This goes against the current documentation for pilot-xfer and other
[all …]
|
| /openbmc/linux/drivers/usb/misc/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
3 # USB Miscellaneous driver configuration
5 comment "USB Miscellaneous drivers"
12 This driver is for USB parallel port adapters that use the Lucent
13 Technologies USS-720 chip. These cables are plugged into your USB
14 port and provide USB compatibility to peripherals designed with
15 parallel port interfaces.
18 mode, it looks to the computer like a standard USB printer. Only
19 printers may be connected to the USS-720 in this mode. The generic
20 USB printer driver ("USB Printer support", above) may be used in
[all …]
|
| /openbmc/qemu/tests/qtest/libqos/ |
| H A D | usb.c | 2 * common code shared by usb tests
12 * See the COPYING file in the top-level directory.
16 #include "hw/usb/uhci-regs.h"
17 #include "usb.h"
21 hc->dev = qpci_device_find(pcibus, devfn); in qusb_pci_init_one()
22 g_assert(hc->dev != NULL); in qusb_pci_init_one()
23 qpci_device_enable(hc->dev); in qusb_pci_init_one()
24 hc->bar = qpci_iomap(hc->dev, bar, NULL); in qusb_pci_init_one()
29 g_free(hc->dev); in uhci_deinit()
32 void uhci_port_test(struct qhc *hc, int port, uint16_t expect) in uhci_port_test() argument
[all …]
|
| /openbmc/linux/drivers/phy/marvell/ |
| H A D | phy-mvebu-cp110-utmi.c | 1 // SPDX-License-Identifier: GPL-2.0
19 #include <linux/usb/of.h>
20 #include <linux/usb/otg.h>
31 #define SYSCON_UTMI_CFG_REG(id) (0x440 + (id) * 4) argument
79 #define PORT_REGS(p) ((p)->priv->regs + (p)->id * 0x1000)
82 * struct mvebu_cp110_utmi - PHY driver data
97 * struct mvebu_cp110_utmi_port - PHY port data
100 * @id: PHY port ID
105 u32 id; member
109 static void mvebu_cp110_utmi_port_setup(struct mvebu_cp110_utmi_port *port) in mvebu_cp110_utmi_port_setup() argument
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/phy/ |
| H A D | nvidia,tegra186-xusb-padctl.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/phy/nvidia,tegra186-xusb-padctl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Jon Hunter <jonathanh@nvidia.com>
21 Some of the lanes are high-speed lanes, which can be used for PCIe, SATA or
22 super-speed USB. Other lanes are for various types of low-speed, full-speed
23 or high-speed USB (such as UTMI, ULPI and HSIC). The XUSB pad controller
24 contains a software-configurable mux that sits between the I/O controller
[all …]
|
| H A D | rockchip,inno-usb2phy.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/phy/rockchip,inno-usb2phy.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Heiko Stuebner <heiko@sntech.de>
15 - rockchip,px30-usb2phy
16 - rockchip,rk3128-usb2phy
17 - rockchip,rk3228-usb2phy
18 - rockchip,rk3308-usb2phy
19 - rockchip,rk3328-usb2phy
[all …]
|
| /openbmc/qemu/tests/qtest/ |
| H A D | usb-hcd-ehci-test.c | 2 * QTest testcase for USB EHCI
7 * See the COPYING file in the top-level directory.
11 #include "libqtest-single.h"
12 #include "libqos/pci-pc.h"
13 #include "hw/usb/uhci-regs.h"
14 #include "hw/usb/ehci-regs.h"
15 #include "libqos/usb.h"
26 static void uhci_port_update(struct qhc *hc, int port,
29 void *addr = hc->base + 0x10 + 2 * port;
32 value = qpci_io_readw(hc->dev, addr);
[all …]
|
| H A D | usb-hcd-uhci-test.c | 2 * QTest testcase for USB UHCI controller
7 * See the COPYING file in the top-level directory.
11 #include "libqtest-single.h"
13 #include "libqos/usb.h"
14 #include "libqos/libqos-pc.h"
15 #include "libqos/libqos-spapr.h"
16 #include "hw/usb/uhci-regs.h"
20 static void test_port(int port) in test_port() argument
24 g_assert(port > 0); in test_port()
25 qusb_pci_init_one(qs->pcibus, &uhci, QPCI_DEVFN(0x1d, 0), 4); in test_port()
[all …]
|
| /openbmc/linux/include/linux/usb/ |
| H A D | typec.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
8 /* USB Type-C Specification releases */
90 * struct enter_usb_data - Enter_USB Message details
94 * @active_link_training is a flag that should be set with uni-directional SBRX
95 * communication, and left 0 with passive cables and with bi-directional SBRX
104 * struct usb_pd_identity - USB Power Delivery identity data
105 * @id_header: ID Header VDO
110 * USB power delivery Discover Identity command response data.
112 * REVISIT: This is USB Power Delivery specific information, so this structure
113 * probable belongs to USB Power Delivery header file once we have them.
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/clock/ |
| H A D | mvebu-gated-clock.txt | 5 should specify the desired clock by having the clock ID in its
6 "clocks" phandle cell. The clock ID is directly mapped to the
11 ID Clock Peripheral
12 -----------------------------------
28 ID Clock Peripheral
29 -----------------------------------
41 18 usb USB Host
49 28 crypto0_enc Cryptographic Unit Port 0 Encryption
50 29 crypto0_core Cryptographic Unit Port 0 Core
51 30 crypto1_enc Cryptographic Unit Port 1 Encryption
[all …]
|
| /openbmc/linux/Documentation/driver-api/usb/ |
| H A D | typec.rst | 3 USB Type-C connector class
7 ------------
9 The typec class is meant for describing the USB Type-C ports in a system to the
14 The platforms are expected to register every USB Type-C port they have with the
15 class. In a normal case the registration will be done by a USB Type-C or PD PHY
17 USB PD controller or even driver for Thunderbolt3 controller. This document
18 considers the component registering the USB Type-C ports with the class as "port
22 the roles and alternate modes of ports, partners and cable plugs when the port
25 The class provides an API for the port drivers described in this document. The
26 attributes are described in Documentation/ABI/testing/sysfs-class-typec.
[all …]
|
| /openbmc/linux/Documentation/firmware-guide/acpi/ |
| H A D | extcon-intel-int3496.rst | 6 devices with an acpi-id of INT3496, such as found for example on
9 This ACPI device describes how the OS can read the id-pin of the devices'
10 USB-otg port, as well as how it optionally can enable Vbus output on the
11 otg port and how it can optionally control the muxing of the data pins
12 between an USB host and an USB peripheral controller.
18 Index 0 The input gpio for the id-pin, this is always present and valid
20 port, write 1 to enable the Vbus output (this gpio descriptor may
22 Index 2 The output gpio for muxing of the data pins between the USB host and
23 the USB peripheral controller, write 1 to mux to the peripheral
30 id index 0
|