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