1# 2# USB Gadget support on a system involves 3# (a) a peripheral controller, and 4# (b) the gadget driver using it. 5# 6# NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !! 7# 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. 11# 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). 14# 15 16menuconfig USB_GADGET 17 bool "USB Gadget Support" 18 help 19 USB is a master/slave protocol, organized with one master 20 host (such as a PC) controlling up to 127 peripheral devices. 21 The USB hardware is asymmetric, which makes it easier to set up: 22 you can't connect a "to-the-host" connector to a peripheral. 23 24 U-Boot can run in the host, or in the peripheral. In both cases 25 you need a low level bus controller driver, and some software 26 talking to it. Peripheral controllers are often discrete silicon, 27 or are integrated with the CPU in a microcontroller. The more 28 familiar host side controllers have names like "EHCI", "OHCI", 29 or "UHCI", and are usually integrated into southbridges on PC 30 motherboards. 31 32 Enable this configuration option if you want to run U-Boot inside 33 a USB peripheral device. Configure one hardware driver for your 34 peripheral/device side bus controller, and a "gadget driver" for 35 your peripheral protocol. 36 37if USB_GADGET 38 39config ASPEED_UDC 40 bool "Aspeed USB Device support" 41 help 42 Support Aspeed USB device on port A. You can emulate USB device as 43 CDC-ACM (usbtty) for example. 44 45config USB_GADGET_MANUFACTURER 46 string "Vendor name of the USB device" 47 default "Allwinner Technology" if ARCH_SUNXI 48 default "U-Boot" 49 help 50 Vendor name of the USB device emulated, reported to the host device. 51 This is usually either the manufacturer of the device or the SoC. 52 53config USB_GADGET_VENDOR_NUM 54 hex "Vendor ID of the USB device" 55 default 0x1f3a if ARCH_SUNXI 56 default 0x0 57 help 58 Vendor ID of the USB device emulated, reported to the host device. 59 This is usually the board or SoC vendor's, unless you've registered 60 for one. 61 62config USB_GADGET_PRODUCT_NUM 63 hex "Product ID of the USB device" 64 default 0x1010 if ARCH_SUNXI 65 default 0x0 66 help 67 Product ID of the USB device emulated, reported to the host device. 68 69config USB_GADGET_ATMEL_USBA 70 bool "Atmel USBA" 71 select USB_GADGET_DUALSPEED 72 help 73 USBA is the integrated high-speed USB Device controller on 74 the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel. 75 76config USB_GADGET_BCM_UDC_OTG_PHY 77 bool "Broadcom UDC OTG PHY" 78 help 79 Enable the Broadcom UDC OTG physical device interface. 80 81config USB_GADGET_DWC2_OTG 82 bool "DesignWare USB2.0 HS OTG controller (gadget mode)" 83 select USB_GADGET_DUALSPEED 84 help 85 The Designware USB2.0 high-speed gadget controller 86 integrated into many SoCs. Select this option if you want the 87 driver to operate in Peripheral mode. This option requires 88 USB_GADGET to be enabled. 89 90if USB_GADGET_DWC2_OTG 91 92config USB_GADGET_DWC2_OTG_PHY_BUS_WIDTH_8 93 bool "DesignWare USB2.0 HS OTG controller 8-bit PHY bus width" 94 help 95 Set the Designware USB2.0 high-speed OTG controller 96 PHY interface width to 8 bits, rather than the default (16 bits). 97 98endif # USB_GADGET_DWC2_OTG 99 100config CI_UDC 101 bool "ChipIdea device controller" 102 select USB_GADGET_DUALSPEED 103 help 104 Say Y here to enable device controller functionality of the 105 ChipIdea driver. 106 107config USB_GADGET_VBUS_DRAW 108 int "Maximum VBUS Power usage (2-500 mA)" 109 range 2 500 110 default 2 111 help 112 Some devices need to draw power from USB when they are 113 configured, perhaps to operate circuitry or to recharge 114 batteries. This is in addition to any local power supply, 115 such as an AC adapter or batteries. 116 117 Enter the maximum power your device draws through USB, in 118 milliAmperes. The permitted range of values is 2 - 500 mA; 119 0 mA would be legal, but can make some hosts misbehave. 120 121 This value will be used except for system-specific gadget 122 drivers that have more specific information. 123 124# Selected by UDC drivers that support high-speed operation. 125config USB_GADGET_DUALSPEED 126 bool 127 128config USB_GADGET_DOWNLOAD 129 bool "Enable USB download gadget" 130 help 131 Composite USB download gadget support (g_dnl) for download functions. 132 This code works on top of composite gadget. 133 134if USB_GADGET_DOWNLOAD 135 136config USB_FUNCTION_MASS_STORAGE 137 bool "Enable USB mass storage gadget" 138 help 139 Enable mass storage protocol support in U-Boot. It allows exporting 140 the eMMC/SD card content to HOST PC so it can be mounted. 141 142config USB_FUNCTION_ROCKUSB 143 bool "Enable USB rockusb gadget" 144 help 145 Rockusb protocol is widely used by Rockchip SoC based devices. It can 146 read/write info, image to/from devices. This enables the USB part of 147 the rockusb gadget.for more detail about Rockusb protocol, please see 148 doc/README.rockusb 149 150config USB_FUNCTION_SDP 151 bool "Enable USB SDP (Serial Download Protocol)" 152 help 153 Enable Serial Download Protocol (SDP) device support in U-Boot. This 154 allows to download images into memory and execute (jump to) them 155 using the same protocol as implemented by the i.MX family's boot ROM. 156 157config USB_FUNCTION_THOR 158 bool "Enable USB THOR gadget" 159 help 160 Enable Tizen's THOR download protocol support in U-Boot. It 161 allows downloading images into memory and flash them to target device. 162 163endif # USB_GADGET_DOWNLOAD 164 165config USB_ETHER 166 bool "USB Ethernet Gadget" 167 depends on NET 168 default y if ARCH_SUNXI && USB_MUSB_GADGET 169 help 170 Creates an Ethernet network device through a USB peripheral 171 controller. This will create a network interface on both the device 172 (U-Boot) and the host (remote device) that can be used just like any 173 other nework interface. 174 It will bind on the peripheral USB controller, ignoring the USB hosts 175 controllers in the system. 176 177if USB_ETHER 178 179choice 180 prompt "USB Ethernet Gadget Model" 181 default USB_ETH_RNDIS 182 help 183 There is several models (protocols) to implement Ethernet over USB 184 devices. The main ones are Microsoft's RNDIS and USB's CDC-Ethernet 185 (also called CDC-ECM). RNDIS is obviously compatible with Windows, 186 while CDC-ECM is not. Most other operating systems support both, so 187 if inter-operability is a concern, RNDIS is to be preferred. 188 189config USB_ETH_CDC 190 bool "CDC-ECM Protocol" 191 help 192 CDC (Communications Device Class) is the standard for Ethernet over 193 USB devices. While there's several alternatives, the most widely used 194 protocol is ECM (Ethernet Control Model). However, compatibility with 195 Windows is not that great. 196 197config USB_ETH_RNDIS 198 bool "RNDIS Protocol" 199 help 200 The RNDIS (Remote Network Driver Interface Specification) is a 201 Microsoft proprietary protocol to create an Ethernet device over USB. 202 Windows obviously supports it, as well as all the major operating 203 systems, so it's the best option for compatibility. 204 205endchoice 206 207config USBNET_DEVADDR 208 string "USB Gadget Ethernet device mac address" 209 default "de:ad:be:ef:00:01" 210 help 211 Ethernet MAC address of the device-side (ie. local board's) MAC 212 address of the usb_ether interface 213 214config USBNET_HOST_ADDR 215 string "USB Gadget Ethernet host mac address" 216 default "de:ad:be:ef:00:00" 217 help 218 Ethernet MAC address of the host-side (ie. remote device's) MAC 219 address of the usb_ether interface 220 221endif # USB_ETHER 222 223endif # USB_GADGET 224