blob: 7a1ee74a555526069d82a2d7773f02eac7f349b7 [file] [log] [blame]
Sam Protsenkob084b0c2016-03-25 16:39:47 +02001#
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.
Sam Protsenkofb115b12016-04-13 14:20:24 +030036
37if USB_GADGET
38
Sam Protsenkob4a0bf72016-04-13 14:20:25 +030039config USB_GADGET_ATMEL_USBA
40 bool "Atmel USBA"
41 select USB_GADGET_DUALSPEED
42 help
43 USBA is the integrated high-speed USB Device controller on
44 the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel.
45
Steve Rae437689f2016-08-15 17:26:26 -070046config USB_GADGET_BCM_UDC_OTG_PHY
47 bool "Broadcom UDC OTG PHY"
48 help
49 Enable the Broadcom UDC OTG physical device interface.
50
Sam Protsenkob4a0bf72016-04-13 14:20:25 +030051config USB_GADGET_DWC2_OTG
52 bool "DesignWare USB2.0 HS OTG controller (gadget mode)"
53 select USB_GADGET_DUALSPEED
54 help
55 The Designware USB2.0 high-speed gadget controller
56 integrated into many SoCs. Select this option if you want the
57 driver to operate in Peripheral mode. This option requires
58 USB_GADGET to be enabled.
59
Steve Raed7198f32016-06-07 15:35:21 -070060if USB_GADGET_DWC2_OTG
61
62config USB_GADGET_DWC2_OTG_PHY_BUS_WIDTH_8
63 bool "DesignWare USB2.0 HS OTG controller 8-bit PHY bus width"
64 help
65 Set the Designware USB2.0 high-speed OTG controller
66 PHY interface width to 8 bits, rather than the default (16 bits).
67
68endif # USB_GADGET_DWC2_OTG
69
Sam Protsenkob4a0bf72016-04-13 14:20:25 +030070config CI_UDC
71 bool "ChipIdea device controller"
72 select USB_GADGET_DUALSPEED
73 help
74 Say Y here to enable device controller functionality of the
75 ChipIdea driver.
76
Sam Protsenkofb115b12016-04-13 14:20:24 +030077config USB_GADGET_VBUS_DRAW
78 int "Maximum VBUS Power usage (2-500 mA)"
79 range 2 500
80 default 2
81 help
82 Some devices need to draw power from USB when they are
83 configured, perhaps to operate circuitry or to recharge
84 batteries. This is in addition to any local power supply,
85 such as an AC adapter or batteries.
86
87 Enter the maximum power your device draws through USB, in
88 milliAmperes. The permitted range of values is 2 - 500 mA;
89 0 mA would be legal, but can make some hosts misbehave.
90
91 This value will be used except for system-specific gadget
92 drivers that have more specific information.
93
Sam Protsenkob4a0bf72016-04-13 14:20:25 +030094# Selected by UDC drivers that support high-speed operation.
95config USB_GADGET_DUALSPEED
96 bool
97
Sam Protsenko4d2439d2016-04-13 14:20:26 +030098config USB_GADGET_DOWNLOAD
99 bool "Enable USB download gadget"
100 help
101 Composite USB download gadget support (g_dnl) for download functions.
102 This code works on top of composite gadget.
103
Sam Protsenkob706ffd2016-04-13 14:20:30 +0300104if USB_GADGET_DOWNLOAD
105
Stefan Agnerffbd5d02017-08-16 11:00:51 -0700106config USB_FUNCTION_SDP
107 bool "Enable USB SDP (Serial Download Protocol)"
108 help
109 Enable Serial Download Protocol (SDP) device support in U-Boot. This
110 allows to download images into memory and execute (jump to) them
111 using the same protocol as implemented by the i.MX family's boot ROM.
112
Sam Protsenkob706ffd2016-04-13 14:20:30 +0300113config G_DNL_MANUFACTURER
114 string "Vendor name of USB device"
115
116config G_DNL_VENDOR_NUM
117 hex "Vendor ID of USB device"
118
119config G_DNL_PRODUCT_NUM
120 hex "Product ID of USB device"
121
Maxime Riparda8ad6362017-09-06 22:54:52 +0200122endif # USB_GADGET_DOWNLOAD
123
Maxime Ripard65849772017-09-06 23:23:21 +0200124config USB_ETHER
125 bool "USB Ethernet Gadget"
126 help
127 Creates an Ethernet network device through a USB peripheral
128 controller. This will create a network interface on both the device
129 (U-Boot) and the host (remote device) that can be used just like any
130 other nework interface.
131 It will bind on the peripheral USB controller, ignoring the USB hosts
132 controllers in the system.
133
134if USB_ETHER
135
Maxime Ripard7285f482017-09-07 08:46:14 +0200136choice
137 prompt "USB Ethernet Gadget Model"
138 default USB_ETH_RNDIS
139 help
140 There is several models (protocols) to implement Ethernet over USB
141 devices. The main ones are Microsoft's RNDIS and USB's CDC-Ethernet
142 (also called CDC-ECM). RNDIS is obviously compatible with Windows,
143 while CDC-ECM is not. Most other operating systems support both, so
144 if inter-operability is a concern, RNDIS is to be preferred.
145
146config USB_ETH_CDC
147 bool "CDC-ECM Protocol"
148 help
149 CDC (Communications Device Class) is the standard for Ethernet over
150 USB devices. While there's several alternatives, the most widely used
151 protocol is ECM (Ethernet Control Model). However, compatibility with
152 Windows is not that great.
153
154config USB_ETH_RNDIS
155 bool "RNDIS Protocol"
156 help
157 The RNDIS (Remote Network Driver Interface Specification) is a
158 Microsoft proprietary protocol to create an Ethernet device over USB.
159 Windows obviously supports it, as well as all the major operating
160 systems, so it's the best option for compatibility.
161
162endchoice
163
Mugunthan V N095b7612016-11-18 11:09:15 +0530164config USBNET_DEVADDR
165 string "USB Gadget Ethernet device mac address"
166 default "de:ad:be:ef:00:01"
Maxime Ripardd4ff5312017-09-12 18:32:45 +0200167 help
168 Ethernet MAC address of the device-side (ie. local board's) MAC
169 address of the usb_ether interface
Mugunthan V N095b7612016-11-18 11:09:15 +0530170
Maxime Ripard764bf282017-09-06 22:53:43 +0200171config USBNET_HOST_ADDR
172 string "USB Gadget Ethernet host mac address"
173 default "de:ad:be:ef:00:00"
174 help
175 Ethernet MAC address of the host-side (ie. remote device's) MAC
176 address of the usb_ether interface
177
Maxime Ripard65849772017-09-06 23:23:21 +0200178endif # USB_ETHER
179
Sam Protsenkofb115b12016-04-13 14:20:24 +0300180endif # USB_GADGET