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