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