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
51 default 0x2207 if ARCH_ROCKCHIP
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
58 config 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
68 Product ID of the USB device emulated, reported to the host device.
70 config USB_GADGET_ATMEL_USBA
72 select USB_GADGET_DUALSPEED
74 USBA is the integrated high-speed USB Device controller on
75 the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel.
77 config USB_GADGET_BCM_UDC_OTG_PHY
78 bool "Broadcom UDC OTG PHY"
80 Enable the Broadcom UDC OTG physical device interface.
82 config USB_GADGET_DWC2_OTG
83 bool "DesignWare USB2.0 HS OTG controller (gadget mode)"
84 select USB_GADGET_DUALSPEED
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.
91 if USB_GADGET_DWC2_OTG
93 config USB_GADGET_DWC2_OTG_PHY_BUS_WIDTH_8
94 bool "DesignWare USB2.0 HS OTG controller 8-bit PHY bus width"
96 Set the Designware USB2.0 high-speed OTG controller
97 PHY interface width to 8 bits, rather than the default (16 bits).
99 endif # USB_GADGET_DWC2_OTG
102 bool "ChipIdea device controller"
103 select USB_GADGET_DUALSPEED
105 Say Y here to enable device controller functionality of the
108 config USB_GADGET_VBUS_DRAW
109 int "Maximum VBUS Power usage (2-500 mA)"
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.
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.
122 This value will be used except for system-specific gadget
123 drivers that have more specific information.
126 hex "Default load address at SDP_WRITE and SDP_JUMP"
129 # Selected by UDC drivers that support high-speed operation.
130 config USB_GADGET_DUALSPEED
133 config USB_GADGET_DOWNLOAD
134 bool "Enable USB download gadget"
136 Composite USB download gadget support (g_dnl) for download functions.
137 This code works on top of composite gadget.
139 if USB_GADGET_DOWNLOAD
141 config USB_FUNCTION_MASS_STORAGE
142 bool "Enable USB mass storage gadget"
144 Enable mass storage protocol support in U-Boot. It allows exporting
145 the eMMC/SD card content to HOST PC so it can be mounted.
147 config USB_FUNCTION_ROCKUSB
148 bool "Enable USB rockusb gadget"
150 Rockusb protocol is widely used by Rockchip SoC based devices. It can
151 read/write info, image to/from devices. This enables the USB part of
152 the rockusb gadget.for more detail about Rockusb protocol, please see
155 config USB_FUNCTION_SDP
156 bool "Enable USB SDP (Serial Download Protocol)"
158 Enable Serial Download Protocol (SDP) device support in U-Boot. This
159 allows to download images into memory and execute (jump to) them
160 using the same protocol as implemented by the i.MX family's boot ROM.
162 config USB_FUNCTION_THOR
163 bool "Enable USB THOR gadget"
165 Enable Tizen's THOR download protocol support in U-Boot. It
166 allows downloading images into memory and flash them to target device.
168 endif # USB_GADGET_DOWNLOAD
171 bool "USB Ethernet Gadget"
173 default y if ARCH_SUNXI && USB_MUSB_GADGET
175 Creates an Ethernet network device through a USB peripheral
176 controller. This will create a network interface on both the device
177 (U-Boot) and the host (remote device) that can be used just like any
178 other nework interface.
179 It will bind on the peripheral USB controller, ignoring the USB hosts
180 controllers in the system.
185 prompt "USB Ethernet Gadget Model"
186 default USB_ETH_RNDIS
188 There is several models (protocols) to implement Ethernet over USB
189 devices. The main ones are Microsoft's RNDIS and USB's CDC-Ethernet
190 (also called CDC-ECM). RNDIS is obviously compatible with Windows,
191 while CDC-ECM is not. Most other operating systems support both, so
192 if inter-operability is a concern, RNDIS is to be preferred.
195 bool "CDC-ECM Protocol"
197 CDC (Communications Device Class) is the standard for Ethernet over
198 USB devices. While there's several alternatives, the most widely used
199 protocol is ECM (Ethernet Control Model). However, compatibility with
200 Windows is not that great.
203 bool "RNDIS Protocol"
205 The RNDIS (Remote Network Driver Interface Specification) is a
206 Microsoft proprietary protocol to create an Ethernet device over USB.
207 Windows obviously supports it, as well as all the major operating
208 systems, so it's the best option for compatibility.
212 config USBNET_DEVADDR
213 string "USB Gadget Ethernet device mac address"
214 default "de:ad:be:ef:00:01"
216 Ethernet MAC address of the device-side (ie. local board's) MAC
217 address of the usb_ether interface
219 config USBNET_HOST_ADDR
220 string "USB Gadget Ethernet host mac address"
221 default "de:ad:be:ef:00:00"
223 Ethernet MAC address of the host-side (ie. remote device's) MAC
224 address of the usb_ether interface