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