| /openbmc/u-boot/drivers/usb/ |
| H A D | Kconfig | 1 menuconfig USB config
2 bool "USB support"
4 Universal Serial Bus (USB) is a specification for a serial bus
7 and allows for hot swapping. Up to 127 USB peripherals can be
8 connected to a single USB host in a tree structure.
10 The USB host is the root of the tree, the peripherals are the
11 leaves and the inner nodes are special USB devices called hubs.
12 Most PCs now have USB host ports, used to connect peripherals
16 Say Y here if your device has an USB port, either host, peripheral or
19 For an USB host port, you then need to say Y to at least one of the
[all …]
|
| /openbmc/qemu/hw/usb/ |
| H A D | Kconfig | 1 config USB config
8 select USB
12 select USB
26 select USB
39 select USB
58 select USB
63 depends on USB
68 depends on USB
73 depends on USB
77 depends on USB
[all...] |
| /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"
13 The eXtensible Host Controller Interface (xHCI) is standard for USB 3.0
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
43 bool "Support for PCI-based xHCI USB controller"
50 bool "Support for Rockchip on-chip xHCI USB controller"
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.usb | 7 USB Support
10 The USB support is implemented on the base of the UHCI Host
13 Currently supported are USB Hubs, USB Keyboards, USB Floppys, USB
14 flash sticks and USB network adaptors.
20 The USB (at least the USB UHCI) needs a frame list (4k), transfer
23 frame pointer. This may cause to crash the OS during boot. So the USB
24 _MUST_ be stopped during OS boot. This is the reason, why the USB is
25 NOT automatically started during start-up. If someone needs the USB
29 For USB keyboards this can be done by a script which is automatically
31 USB keyboard another script is necessary, which first disables the
[all …]
|
| H A D | README.fsl-hwconfig | 24 Specific to boards have USB controller
26 This option specifies the following for a USB controller:
29 - which USB PHY to use
31 This is used by generic USB device-tree fixup function to update
34 Also used for configuring multiple USB controllers such that
38 Select USB phy type: 'utmi' OR 'ulpi'
41 Select USB controller mode: 'host', 'peripheral' OR 'otg'
|
| /openbmc/u-boot/drivers/usb/gadget/ |
| H A D | Kconfig | 2 # USB Gadget support on a system involves
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
21 The USB hardware is asymmetric, which makes it easier to set up:
33 a USB peripheral device. Configure one hardware driver for your
42 Support Aspeed USB device on port A. You can emulate USB device as
46 bool "Aspeed USB Device support on gadget"
50 Support Aspeed USB device gadget. It's a different architecture with
55 string "Vendor name of the USB device"
[all …]
|
| /openbmc/u-boot/drivers/usb/eth/ |
| H A D | Kconfig | 2 bool "USB to Ethernet Controller Drivers"
4 Say Y here if you would like to enable support for USB Ethernet
10 bool "ASIX AX8817X (USB 2.0) support"
13 Say Y here if you would like to support ASIX AX8817X based USB 2.0
17 bool "ASIX AX88179 (USB 3.0) support"
20 Say Y here if you would like to support ASIX AX88179 based USB 3.0
29 USB 2.0 to 10/100/1000 Gigabit Ethernet controller.
38 Say Y here if you would like to support Microchip LAN78XX USB 3.1
48 (7730/7830/7832) USB 2.0 Ethernet Devices.
55 USB Ethernet Devices. This driver also supports compatible devices
[all …]
|
| /openbmc/qemu/docs/system/devices/ |
| H A D | usb.rst | 1 USB emulation
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
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
25 therefore only a single USB bus) present in the system there is no
26 need to use the bus= parameter when adding USB devices.
32 The QEMU EHCI Adapter supports USB 2.0 devices. It can be used either
[all …]
|
| /openbmc/u-boot/arch/arm/mach-rockchip/rk3399/ |
| H A D | Kconfig | 11 usb2.0 host ports, LVDS, JTAG, MAC, SDcard, HDMI, USB-2-serial...
23 * on-module USB 3.0 hub (2x USB 3.0 host + 1x USB 2.0 host)
24 * USB 3.0 dual-role
46 * 1x USB 3.0 type A, 1x USB 2.0 type A (host mode only),
47 1x USB 3.0 type C OTG
53 * 2x USB 3.0 type A, 2x USB 2.0 type A (host mode only),
54 1x USB 3.0 type C OTG
60 It has two USB 3.0 type-C ports, 4GB of SDRAM, WiFi and a 10.1",
61 1280x800 display. It uses its USB ports for both power and external
|
| /openbmc/u-boot/drivers/usb/musb-new/ |
| H A D | Kconfig | 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"
54 Say y here to enable support for the sunxi OTG / DRC USB controller
|
| /openbmc/u-boot/drivers/phy/ |
| H A D | Kconfig | 114 tristate "Renesas R-Car Gen2 USB PHY"
117 Support for the Renesas R-Car Gen2 USB PHY. This driver operates the
122 tristate "Renesas R-Car Gen3 USB PHY"
126 Support for the Renesas R-Car Gen3 USB PHY. This driver operates the
127 PHY connected to EHCI USB module and controls USB OTG operation.
130 tristate "STMicroelectronics STM32 SoC USB HS PHY driver"
133 Enable this to support the High-Speed USB transceiver that is part of
136 This driver controls the entire USB PHY block: the USB PHY controller
138 used by an HS USB Host controller, and the second one is shared
139 between an HS USB OTG controller and an HS USB Host controller,
[all …]
|
| /openbmc/u-boot/drivers/usb/emul/ |
| H A D | Kconfig | 2 bool "Support for USB device emulation"
5 Since sandbox does not have access to a real USB bus, it is possible
6 to use device emulators instead. This allows testing of the USB
8 USB resources.
|
| /openbmc/u-boot/drivers/phy/allwinner/ |
| H A D | Kconfig | 5 bool "Allwinner Sun4I USB PHY driver"
12 This driver controls the entire USB PHY block, both the USB OTG
13 parts, as well as the 2 regular USB 2 host PHYs.
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | usb-info.txt | 1 How USB works with driver model
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
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
25 as drivers in the USB uclass. For example:
63 in USB device mode (OTG operation). It can be omitted if that is not
72 set up the USB controllers from board init code. When 'usb start' is used,
94 as a work-around for controllers which can act as USB devices in OTG
[all …]
|
| /openbmc/u-boot/board/technexion/pico-imx7d/ |
| H A D | README | 16 1. Loading U-Boot via USB Serial Download Protocol
22 Put pico board in USB download mode (refer to the PICO-iMX7D Quick Start Guide
25 Connect a USB to serial adapter between the host PC and pico.
27 Connect a USB cable between the OTG pico port and the host PC.
29 Note: Some computers may be a bit strict with USB current draw and will
31 to use an externally powered USB hub between the board and the host computer.
37 Load the SPL binary via USB:
41 Load the u-boot.img binary via USB:
|
| /openbmc/u-boot/arch/x86/include/asm/arch-baytrail/acpi/ |
| H A D | xhci.asl | 25 Device (PRT1) { Name(_ADR, 1) } /* USB Port 0 */
26 Device (PRT2) { Name(_ADR, 2) } /* USB Port 1 */
27 Device (PRT3) { Name(_ADR, 3) } /* USB Port 2 */
28 Device (PRT4) { Name(_ADR, 4) } /* USB Port 3 */
|
| H A D | usb.asl | 28 Device(PRT1) { Name(_ADR, 1) } /* USB Port 0 */
29 Device(PRT2) { Name(_ADR, 2) } /* USB Port 1 */
30 Device(PRT3) { Name(_ADR, 3) } /* USB Port 2 */
31 Device(PRT4) { Name(_ADR, 4) } /* USB Port 3 */
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/pxaregs/pxaregs-1.14/ |
| H A D | usb.patch | 11 +{ "UP2OCR", 0x40600020, 0, 0xffffffff, 'x', "USB Port 2 Output Control Register" },
12 +{ "UP2OCR_SEOS", 0x40600020, 24, 7, 'x', "USB Port 2 Single-Ended Output Select" },
13 +{ "UP2OCR_HXOE", 0x40600020, 17, 1, 'x', "USB Port 2 Tranceiver OE" },
14 +{ "UP2OCR_HXS", 0x40600020, 16, 1, 'x', "USB Port 2 Tranceiver Output Select" },
|
| /openbmc/openbmc/meta-facebook/meta-sanmiguel/recipes-kernel/linux/linux-aspeed/ |
| H A D | sanmiguel.cfg | 23 # USB EHCI
27 # USB NET
35 # USB HID
41 # USB Serial
|
| /openbmc/u-boot/doc/imx/misc/ |
| H A D | sdp.txt | 7 image to the chip over USB and UART serial connection.
9 The implementation in U-Boot uses the USB Downloader Gadget (g_dnl) to
10 provide a SDP implementation over USB. This allows to download program
14 The SDP protocol over USB is a USB HID class protocol. USB HID class
15 protocols allow to access a USB device without OS specific drivers. The
20 install U-Boot without a JTAG debugger, using the USB boot mode as
46 Trying to boot from USB SDP
51 the boot ROM's SDP protocol. The USB VID/PID will depend on standard
53 imx_usb is aware of the USB VID/PID for your device by adding a
110 Booting in USB mode, the i.MX6 announces itself to the Linux Host as:
|
| /openbmc/docs/designs/ |
| H A D | firmware-update-via-usb.md | 1 # In-Band Update of BMC Firmware using USB
17 and USB is not yet supported.
19 The intent of this new application design is to enable the USB driver of BMC to
26 - Monitor whether the USB key is inserted.
27 - The first tar file found in the sorted list of files on the USB device is
41 repository to identify whether to enable the USB Code Update function, which
67 - Assuming that the USB drive has a physical security vulnerability (such as
68 memory overflow, etc.), should disable "USB code update" via Redfish. After
69 the vulnerability is fixed, enable "USB code update" again via Redfish.
81 This impacts security because it can copy files to the BMC via an external USB
[all …]
|
| /openbmc/u-boot/board/hisilicon/poplar/ |
| H A D | README | 15 USB Two USB 2.0 ports One USB 3.0 ports
16 CONSOLE USB-micro port for console support
137 Using USB debrick support:
138 Copy fastboot.bin to a FAT partition on the USB drive and reboot the
146 2) using FAT formated USB drive
149 1. TFTP (USB ethernet dongle)
152 Plug a USB AXIS ethernet dongle on any of the USB2 ports on the Poplar board.
159 starting USB...
160 USB0: USB EHCI 1.00
161 scanning bus 0 for devices... 1 USB Device(s) found
[all …]
|
| /openbmc/u-boot/drivers/usb/dwc3/ |
| H A D | Kconfig | 6 USB controller based on the DesignWare USB3 IP Core.
15 depends on USB
57 bool "TI OMAP SoC series USB DRD PHY driver"
63 bool "Exynos5 SoC series USB DRD PHY driver"
65 Enable USB DRD PHY support for Exynos 5 SoC series.
66 This driver provides PHY interface for USB 3.0 DRD controller
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-kernel/usbip-tools/ |
| H A D | usbip-tools.bb | 1 # Recipe for building userspace part of USB/IP
14 DESCRIPTION = " USB/IP protocol allows to pass USB device from server to \
16 USB device. Client is a machine which uses USB device provided by server \
17 over the network. The USB device may be either physical device connected \
18 to a server or software entity created on a server using USB gadget subsystem."
|
| /openbmc/u-boot/board/bticino/mamoj/ |
| H A D | README | 14 1. USB SDP boot
20 1. USB SDP boot:
33 - Plug-in USB-to-Serial, Open minicom 1152008N1 and USB OTG cables to Host
60 We can see U-Boot boot from USB SDP on minicom
65 Once booted from USB SDP, program the eMMC as below(make sure to connect USB OTG)
|