2 # USB Gadget support on a system involves
3 # (a) a peripheral controller, and
4 # (b) the gadget driver using it.
6 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
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.
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).
17 bool "USB Gadget Support"
21 USB is a master/slave protocol, organized with one master
22 host (such as a PC) controlling up to 127 peripheral devices.
23 The USB hardware is asymmetric, which makes it easier to set up:
24 you can't connect a "to-the-host" connector to a peripheral.
26 U-Boot can run in the host, or in the peripheral. In both cases
27 you need a low level bus controller driver, and some software
28 talking to it. Peripheral controllers are often discrete silicon,
29 or are integrated with the CPU in a microcontroller. The more
30 familiar host side controllers have names like "EHCI", "OHCI",
31 or "UHCI", and are usually integrated into southbridges on PC
34 Enable this configuration option if you want to run U-Boot inside
35 a USB peripheral device. Configure one hardware driver for your
36 peripheral/device side bus controller, and a "gadget driver" for
37 your peripheral protocol.
41 config USB_GADGET_MANUFACTURER
42 string "Vendor name of the USB device"
43 default "Allwinner Technology" if ARCH_SUNXI
44 default "Rockchip" if ARCH_ROCKCHIP
47 Vendor name of the USB device emulated, reported to the host device.
48 This is usually either the manufacturer of the device or the SoC.
50 config USB_GADGET_VENDOR_NUM
51 hex "Vendor ID of the USB device"
52 default 0x1f3a if ARCH_SUNXI
53 default 0x2207 if ARCH_ROCKCHIP
56 Vendor ID of the USB device emulated, reported to the host device.
57 This is usually the board or SoC vendor's, unless you've registered
60 config USB_GADGET_PRODUCT_NUM
61 hex "Product ID of the USB device"
62 default 0x1010 if ARCH_SUNXI
63 default 0x310a if ROCKCHIP_RK3036
64 default 0x310c if ROCKCHIP_RK3128
65 default 0x320a if ROCKCHIP_RK3229 || ROCKCHIP_RK3288
66 default 0x330a if ROCKCHIP_RK3328
67 default 0x330c if ROCKCHIP_RK3399
70 Product ID of the USB device emulated, reported to the host device.
72 config USB_GADGET_ATMEL_USBA
74 select USB_GADGET_DUALSPEED
76 USBA is the integrated high-speed USB Device controller on
77 the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel.
79 config USB_GADGET_BCM_UDC_OTG_PHY
80 bool "Broadcom UDC OTG PHY"
82 Enable the Broadcom UDC OTG physical device interface.
84 config USB_GADGET_DWC2_OTG
85 bool "DesignWare USB2.0 HS OTG controller (gadget mode)"
86 select USB_GADGET_DUALSPEED
88 The Designware USB2.0 high-speed gadget controller
89 integrated into many SoCs. Select this option if you want the
90 driver to operate in Peripheral mode. This option requires
91 USB_GADGET to be enabled.
93 if USB_GADGET_DWC2_OTG
95 config USB_GADGET_DWC2_OTG_PHY
96 bool "DesignWare USB2.0 HS OTG PHY"
98 Enable the DesignWare USB2.0 HS OTG physical device interface.
100 config USB_GADGET_DWC2_OTG_PHY_BUS_WIDTH_8
101 bool "DesignWare USB2.0 HS OTG controller 8-bit PHY bus width"
103 Set the Designware USB2.0 high-speed OTG controller
104 PHY interface width to 8 bits, rather than the default (16 bits).
106 endif # USB_GADGET_DWC2_OTG
108 config USB_GADGET_OS_DESCRIPTORS
109 bool "USB OS Feature Descriptors support"
111 This is a porting patch from linux kernel: 37a3a533429e
112 ("usb: gadget: OS Feature Descriptors support"), the original commit
114 There is a custom (non-USB IF) extension to the USB standard:
115 http://msdn.microsoft.com/library/windows/hardware/gg463182
118 bool "ChipIdea device controller"
119 select USB_GADGET_DUALSPEED
121 Say Y here to enable device controller functionality of the
124 config USB_GADGET_MAX3420
125 bool "MAX3420 USB Over SPI"
128 MAX3420, from MAXIM, implements USB-over-SPI Full-Speed device controller.
130 config USB_GADGET_VBUS_DRAW
131 int "Maximum VBUS Power usage (2-500 mA)"
135 Some devices need to draw power from USB when they are
136 configured, perhaps to operate circuitry or to recharge
137 batteries. This is in addition to any local power supply,
138 such as an AC adapter or batteries.
140 Enter the maximum power your device draws through USB, in
141 milliAmperes. The permitted range of values is 2 - 500 mA;
142 0 mA would be legal, but can make some hosts misbehave.
144 This value will be used except for system-specific gadget
145 drivers that have more specific information.
148 hex "Default load address at SDP_WRITE and SDP_JUMP"
151 # Selected by UDC drivers that support high-speed operation.
152 config USB_GADGET_DUALSPEED
155 config USB_GADGET_DOWNLOAD
156 bool "Enable USB download gadget"
158 Composite USB download gadget support (g_dnl) for download functions.
159 This code works on top of composite gadget.
161 if USB_GADGET_DOWNLOAD
163 config USB_FUNCTION_MASS_STORAGE
164 bool "Enable USB mass storage gadget"
166 Enable mass storage protocol support in U-Boot. It allows exporting
167 the eMMC/SD card content to HOST PC so it can be mounted.
169 config USB_FUNCTION_ROCKUSB
170 bool "Enable USB rockusb gadget"
172 Rockusb protocol is widely used by Rockchip SoC based devices. It can
173 read/write info, image to/from devices. This enables the USB part of
174 the rockusb gadget.for more detail about Rockusb protocol, please see
177 config USB_FUNCTION_SDP
178 bool "Enable USB SDP (Serial Download Protocol)"
180 Enable Serial Download Protocol (SDP) device support in U-Boot. This
181 allows to download images into memory and execute (jump to) them
182 using the same protocol as implemented by the i.MX family's boot ROM.
184 config USB_FUNCTION_THOR
185 bool "Enable USB THOR gadget"
187 Enable Tizen's THOR download protocol support in U-Boot. It
188 allows downloading images into memory and flash them to target device.
190 config USB_FUNCTION_ACM
191 bool "Enable CDC ACM gadget"
192 select SYS_STDIO_DEREGISTER
195 ACM serial link. This function can be used to create a stdio device to
196 interoperate with MS-Windows hosts or with the Linux-USB "cdc-acm"
199 endif # USB_GADGET_DOWNLOAD
202 bool "USB Ethernet Gadget"
204 default y if ARCH_SUNXI && USB_MUSB_GADGET
206 Creates an Ethernet network device through a USB peripheral
207 controller. This will create a network interface on both the device
208 (U-Boot) and the host (remote device) that can be used just like any
209 other nework interface.
210 It will bind on the peripheral USB controller, ignoring the USB hosts
211 controllers in the system.
216 prompt "USB Ethernet Gadget Model"
217 default USB_ETH_RNDIS
219 There is several models (protocols) to implement Ethernet over USB
220 devices. The main ones are Microsoft's RNDIS and USB's CDC-Ethernet
221 (also called CDC-ECM). RNDIS is obviously compatible with Windows,
222 while CDC-ECM is not. Most other operating systems support both, so
223 if inter-operability is a concern, RNDIS is to be preferred.
226 bool "CDC-ECM Protocol"
228 CDC (Communications Device Class) is the standard for Ethernet over
229 USB devices. While there's several alternatives, the most widely used
230 protocol is ECM (Ethernet Control Model). However, compatibility with
231 Windows is not that great.
234 bool "RNDIS Protocol"
236 The RNDIS (Remote Network Driver Interface Specification) is a
237 Microsoft proprietary protocol to create an Ethernet device over USB.
238 Windows obviously supports it, as well as all the major operating
239 systems, so it's the best option for compatibility.
243 config USBNET_DEVADDR
244 string "USB Gadget Ethernet device mac address"
245 default "de:ad:be:ef:00:01"
247 Ethernet MAC address of the device-side (ie. local board's) MAC
248 address of the usb_ether interface
250 config USBNET_HOST_ADDR
251 string "USB Gadget Ethernet host mac address"
252 default "de:ad:be:ef:00:00"
254 Ethernet MAC address of the host-side (ie. remote device's) MAC
255 address of the usb_ether interface