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 USB_GADGET_OS_DESCRIPTORS
102	bool "USB OS Feature Descriptors support"
103	help
104	  This is a porting patch from linux kernel: 37a3a533429e
105	  ("usb: gadget: OS Feature Descriptors support"), the original commit
106	  log see below:
107	  There is a custom (non-USB IF) extension to the USB standard:
108	  http://msdn.microsoft.com/library/windows/hardware/gg463182
109
110config CI_UDC
111	bool "ChipIdea device controller"
112	select USB_GADGET_DUALSPEED
113	help
114	  Say Y here to enable device controller functionality of the
115	  ChipIdea driver.
116
117config USB_GADGET_MAX3420
118	bool "MAX3420 USB Over SPI"
119	depends on DM_SPI
120	help
121	  MAX3420, from MAXIM, implements USB-over-SPI Full-Speed device controller.
122
123config USB_GADGET_VBUS_DRAW
124	int "Maximum VBUS Power usage (2-500 mA)"
125	range 2 500
126	default 2
127	help
128	   Some devices need to draw power from USB when they are
129	   configured, perhaps to operate circuitry or to recharge
130	   batteries.  This is in addition to any local power supply,
131	   such as an AC adapter or batteries.
132
133	   Enter the maximum power your device draws through USB, in
134	   milliAmperes.  The permitted range of values is 2 - 500 mA;
135	   0 mA would be legal, but can make some hosts misbehave.
136
137	   This value will be used except for system-specific gadget
138	   drivers that have more specific information.
139
140config SDP_LOADADDR
141	hex "Default load address at SDP_WRITE and SDP_JUMP"
142	default 0
143
144# Selected by UDC drivers that support high-speed operation.
145config USB_GADGET_DUALSPEED
146	bool
147
148config USB_GADGET_DOWNLOAD
149	bool "Enable USB download gadget"
150	help
151	  Composite USB download gadget support (g_dnl) for download functions.
152	  This code works on top of composite gadget.
153
154if USB_GADGET_DOWNLOAD
155
156config USB_FUNCTION_MASS_STORAGE
157	bool "Enable USB mass storage gadget"
158	help
159	  Enable mass storage protocol support in U-Boot. It allows exporting
160	  the eMMC/SD card content to HOST PC so it can be mounted.
161
162config USB_FUNCTION_ROCKUSB
163        bool "Enable USB rockusb gadget"
164        help
165          Rockusb protocol is widely used by Rockchip SoC based devices. It can
166          read/write info, image to/from devices. This enables the USB part of
167          the rockusb gadget.for more detail about Rockusb protocol, please see
168          doc/README.rockusb
169
170config USB_FUNCTION_SDP
171	bool "Enable USB SDP (Serial Download Protocol)"
172	help
173	  Enable Serial Download Protocol (SDP) device support in U-Boot. This
174	  allows to download images into memory and execute (jump to) them
175	  using the same protocol as implemented by the i.MX family's boot ROM.
176
177config USB_FUNCTION_THOR
178	bool "Enable USB THOR gadget"
179	help
180	  Enable Tizen's THOR download protocol support in U-Boot. It
181	  allows downloading images into memory and flash them to target device.
182
183endif # USB_GADGET_DOWNLOAD
184
185config USB_ETHER
186	bool "USB Ethernet Gadget"
187	depends on NET
188	default y if ARCH_SUNXI && USB_MUSB_GADGET
189	help
190	  Creates an Ethernet network device through a USB peripheral
191	  controller. This will create a network interface on both the device
192	  (U-Boot) and the host (remote device) that can be used just like any
193	  other nework interface.
194	  It will bind on the peripheral USB controller, ignoring the USB hosts
195	  controllers in the system.
196
197if USB_ETHER
198
199choice
200	prompt "USB Ethernet Gadget Model"
201	default USB_ETH_RNDIS
202	help
203	  There is several models (protocols) to implement Ethernet over USB
204	  devices. The main ones are Microsoft's RNDIS and USB's CDC-Ethernet
205	  (also called CDC-ECM). RNDIS is obviously compatible with Windows,
206	  while CDC-ECM is not. Most other operating systems support both, so
207	  if inter-operability is a concern, RNDIS is to be preferred.
208
209config USB_ETH_CDC
210	bool "CDC-ECM Protocol"
211	help
212	  CDC (Communications Device Class) is the standard for Ethernet over
213	  USB devices. While there's several alternatives, the most widely used
214	  protocol is ECM (Ethernet Control Model). However, compatibility with
215	  Windows is not that great.
216
217config USB_ETH_RNDIS
218	bool "RNDIS Protocol"
219	help
220	  The RNDIS (Remote Network Driver Interface Specification) is a
221	  Microsoft proprietary protocol to create an Ethernet device over USB.
222	  Windows obviously supports it, as well as all the major operating
223	  systems, so it's the best option for compatibility.
224
225endchoice
226
227config USBNET_DEVADDR
228	string "USB Gadget Ethernet device mac address"
229	default "de:ad:be:ef:00:01"
230	help
231	  Ethernet MAC address of the device-side (ie. local board's) MAC
232	  address of the usb_ether interface
233
234config USBNET_HOST_ADDR
235	string "USB Gadget Ethernet host mac address"
236	default "de:ad:be:ef:00:00"
237	help
238	  Ethernet MAC address of the host-side (ie. remote device's) MAC
239	  address of the usb_ether interface
240
241endif # USB_ETHER
242
243endif # USB_GADGET
244