]> git.ipfire.org Git - people/ms/u-boot.git/blob - drivers/usb/gadget/Kconfig
usb: gadget: Make g_dnl USB settings common
[people/ms/u-boot.git] / drivers / usb / gadget / Kconfig
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
16 menuconfig 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
37 if USB_GADGET
38
39 config USB_GADGET_MANUFACTURER
40 string "Vendor name of the USB device"
41 default "U-Boot"
42 help
43 Vendor name of the USB device emulated, reported to the host device.
44 This is usually either the manufacturer of the device or the SoC.
45
46 config USB_GADGET_VENDOR_NUM
47 hex "Vendor ID of the USB device"
48 default 0x0
49 help
50 Vendor ID of the USB device emulated, reported to the host device.
51 This is usually the board or SoC vendor's, unless you've registered
52 for one.
53
54 config USB_GADGET_PRODUCT_NUM
55 hex "Product ID of the USB device"
56 default 0x0
57 help
58 Product ID of the USB device emulated, reported to the host device.
59
60 config USB_GADGET_ATMEL_USBA
61 bool "Atmel USBA"
62 select USB_GADGET_DUALSPEED
63 help
64 USBA is the integrated high-speed USB Device controller on
65 the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel.
66
67 config USB_GADGET_BCM_UDC_OTG_PHY
68 bool "Broadcom UDC OTG PHY"
69 help
70 Enable the Broadcom UDC OTG physical device interface.
71
72 config USB_GADGET_DWC2_OTG
73 bool "DesignWare USB2.0 HS OTG controller (gadget mode)"
74 select USB_GADGET_DUALSPEED
75 help
76 The Designware USB2.0 high-speed gadget controller
77 integrated into many SoCs. Select this option if you want the
78 driver to operate in Peripheral mode. This option requires
79 USB_GADGET to be enabled.
80
81 if USB_GADGET_DWC2_OTG
82
83 config USB_GADGET_DWC2_OTG_PHY_BUS_WIDTH_8
84 bool "DesignWare USB2.0 HS OTG controller 8-bit PHY bus width"
85 help
86 Set the Designware USB2.0 high-speed OTG controller
87 PHY interface width to 8 bits, rather than the default (16 bits).
88
89 endif # USB_GADGET_DWC2_OTG
90
91 config CI_UDC
92 bool "ChipIdea device controller"
93 select USB_GADGET_DUALSPEED
94 help
95 Say Y here to enable device controller functionality of the
96 ChipIdea driver.
97
98 config USB_GADGET_VBUS_DRAW
99 int "Maximum VBUS Power usage (2-500 mA)"
100 range 2 500
101 default 2
102 help
103 Some devices need to draw power from USB when they are
104 configured, perhaps to operate circuitry or to recharge
105 batteries. This is in addition to any local power supply,
106 such as an AC adapter or batteries.
107
108 Enter the maximum power your device draws through USB, in
109 milliAmperes. The permitted range of values is 2 - 500 mA;
110 0 mA would be legal, but can make some hosts misbehave.
111
112 This value will be used except for system-specific gadget
113 drivers that have more specific information.
114
115 # Selected by UDC drivers that support high-speed operation.
116 config USB_GADGET_DUALSPEED
117 bool
118
119 config USB_GADGET_DOWNLOAD
120 bool "Enable USB download gadget"
121 help
122 Composite USB download gadget support (g_dnl) for download functions.
123 This code works on top of composite gadget.
124
125 if USB_GADGET_DOWNLOAD
126
127 config USB_FUNCTION_SDP
128 bool "Enable USB SDP (Serial Download Protocol)"
129 help
130 Enable Serial Download Protocol (SDP) device support in U-Boot. This
131 allows to download images into memory and execute (jump to) them
132 using the same protocol as implemented by the i.MX family's boot ROM.
133
134 endif # USB_GADGET_DOWNLOAD
135
136 config USB_ETHER
137 bool "USB Ethernet Gadget"
138 help
139 Creates an Ethernet network device through a USB peripheral
140 controller. This will create a network interface on both the device
141 (U-Boot) and the host (remote device) that can be used just like any
142 other nework interface.
143 It will bind on the peripheral USB controller, ignoring the USB hosts
144 controllers in the system.
145
146 if USB_ETHER
147
148 choice
149 prompt "USB Ethernet Gadget Model"
150 default USB_ETH_RNDIS
151 help
152 There is several models (protocols) to implement Ethernet over USB
153 devices. The main ones are Microsoft's RNDIS and USB's CDC-Ethernet
154 (also called CDC-ECM). RNDIS is obviously compatible with Windows,
155 while CDC-ECM is not. Most other operating systems support both, so
156 if inter-operability is a concern, RNDIS is to be preferred.
157
158 config USB_ETH_CDC
159 bool "CDC-ECM Protocol"
160 help
161 CDC (Communications Device Class) is the standard for Ethernet over
162 USB devices. While there's several alternatives, the most widely used
163 protocol is ECM (Ethernet Control Model). However, compatibility with
164 Windows is not that great.
165
166 config USB_ETH_RNDIS
167 bool "RNDIS Protocol"
168 help
169 The RNDIS (Remote Network Driver Interface Specification) is a
170 Microsoft proprietary protocol to create an Ethernet device over USB.
171 Windows obviously supports it, as well as all the major operating
172 systems, so it's the best option for compatibility.
173
174 endchoice
175
176 config USBNET_DEVADDR
177 string "USB Gadget Ethernet device mac address"
178 default "de:ad:be:ef:00:01"
179 help
180 Ethernet MAC address of the device-side (ie. local board's) MAC
181 address of the usb_ether interface
182
183 config USBNET_HOST_ADDR
184 string "USB Gadget Ethernet host mac address"
185 default "de:ad:be:ef:00:00"
186 help
187 Ethernet MAC address of the host-side (ie. remote device's) MAC
188 address of the usb_ether interface
189
190 endif # USB_ETHER
191
192 endif # USB_GADGET