Commit | Line | Data |
---|---|---|
90fccb52 AP |
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 | # | |
17 | # USB Peripheral Controller Support | |
18 | # | |
19 | # The order here is alphabetical, except that integrated controllers go | |
20 | # before discrete ones so they will be the initial/default value: | |
21 | # - integrated/SOC controllers first | |
22 | # - licensed IP used in both SOC and discrete versions | |
23 | # - discrete ones (including all PCI-only controllers) | |
24 | # - debug/dummy gadget+hcd is last. | |
25 | # | |
26 | menu "USB Peripheral Controller" | |
27 | ||
28 | # | |
29 | # Integrated controllers | |
30 | # | |
31 | ||
32 | config USB_AT91 | |
33 | tristate "Atmel AT91 USB Device Port" | |
34 | depends on ARCH_AT91 | |
9f00fc1d | 35 | depends on OF || COMPILE_TEST |
90fccb52 AP |
36 | help |
37 | Many Atmel AT91 processors (such as the AT91RM2000) have a | |
38 | full speed USB Device Port with support for five configurable | |
39 | endpoints (plus endpoint zero). | |
40 | ||
41 | Say "y" to link the driver statically, or "m" to build a | |
42 | dynamically linked module called "at91_udc" and force all | |
43 | gadget drivers to also be dynamically linked. | |
44 | ||
45 | config USB_LPC32XX | |
46 | tristate "LPC32XX USB Peripheral Controller" | |
47 | depends on ARCH_LPC32XX && I2C | |
48 | select USB_ISP1301 | |
49 | help | |
50 | This option selects the USB device controller in the LPC32xx SoC. | |
51 | ||
52 | Say "y" to link the driver statically, or "m" to build a | |
53 | dynamically linked module called "lpc32xx_udc" and force all | |
54 | gadget drivers to also be dynamically linked. | |
55 | ||
56 | config USB_ATMEL_USBA | |
57 | tristate "Atmel USBA" | |
9af91954 | 58 | depends on ((AVR32 && !OF) || ARCH_AT91) |
90fccb52 AP |
59 | help |
60 | USBA is the integrated high-speed USB Device controller on | |
61 | the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel. | |
62 | ||
63 | config USB_BCM63XX_UDC | |
64 | tristate "Broadcom BCM63xx Peripheral Controller" | |
65 | depends on BCM63XX | |
66 | help | |
67 | Many Broadcom BCM63xx chipsets (such as the BCM6328) have a | |
68 | high speed USB Device Port with support for four fixed endpoints | |
69 | (plus endpoint zero). | |
70 | ||
71 | Say "y" to link the driver statically, or "m" to build a | |
72 | dynamically linked module called "bcm63xx_udc". | |
73 | ||
74 | config USB_FSL_USB2 | |
75 | tristate "Freescale Highspeed USB DR Peripheral Controller" | |
76 | depends on FSL_SOC || ARCH_MXC | |
90fccb52 AP |
77 | help |
78 | Some of Freescale PowerPC and i.MX processors have a High Speed | |
79 | Dual-Role(DR) USB controller, which supports device mode. | |
80 | ||
81 | The number of programmable endpoints is different through | |
82 | SOC revisions. | |
83 | ||
84 | Say "y" to link the driver statically, or "m" to build a | |
85 | dynamically linked module called "fsl_usb2_udc" and force | |
86 | all gadget drivers to also be dynamically linked. | |
87 | ||
88 | config USB_FUSB300 | |
89 | tristate "Faraday FUSB300 USB Peripheral Controller" | |
90 | depends on !PHYS_ADDR_T_64BIT && HAS_DMA | |
91 | help | |
92 | Faraday usb device controller FUSB300 driver | |
93 | ||
94 | config USB_FOTG210_UDC | |
95 | depends on HAS_DMA | |
96 | tristate "Faraday FOTG210 USB Peripheral Controller" | |
97 | help | |
98 | Faraday USB2.0 OTG controller which can be configured as | |
99 | high speed or full speed USB device. This driver supppors | |
100 | Bulk Transfer so far. | |
101 | ||
102 | Say "y" to link the driver statically, or "m" to build a | |
103 | dynamically linked module called "fotg210_udc". | |
104 | ||
105 | config USB_GR_UDC | |
106 | tristate "Aeroflex Gaisler GRUSBDC USB Peripheral Controller Driver" | |
107 | depends on HAS_DMA | |
108 | help | |
109 | Select this to support Aeroflex Gaisler GRUSBDC cores from the GRLIB | |
110 | VHDL IP core library. | |
111 | ||
112 | config USB_OMAP | |
113 | tristate "OMAP USB Device Controller" | |
114 | depends on ARCH_OMAP1 | |
115 | depends on ISP1301_OMAP || !(MACH_OMAP_H2 || MACH_OMAP_H3) | |
116 | help | |
117 | Many Texas Instruments OMAP processors have flexible full | |
118 | speed USB device controllers, with support for up to 30 | |
119 | endpoints (plus endpoint zero). This driver supports the | |
120 | controller in the OMAP 1611, and should work with controllers | |
121 | in other OMAP processors too, given minor tweaks. | |
122 | ||
123 | Say "y" to link the driver statically, or "m" to build a | |
124 | dynamically linked module called "omap_udc" and force all | |
125 | gadget drivers to also be dynamically linked. | |
126 | ||
127 | config USB_PXA25X | |
128 | tristate "PXA 25x or IXP 4xx" | |
129 | depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX | |
1b4ea40b | 130 | depends on HAS_IOMEM |
90fccb52 AP |
131 | help |
132 | Intel's PXA 25x series XScale ARM-5TE processors include | |
133 | an integrated full speed USB 1.1 device controller. The | |
134 | controller in the IXP 4xx series is register-compatible. | |
135 | ||
136 | It has fifteen fixed-function endpoints, as well as endpoint | |
137 | zero (for control transfers). | |
138 | ||
139 | Say "y" to link the driver statically, or "m" to build a | |
140 | dynamically linked module called "pxa25x_udc" and force all | |
141 | gadget drivers to also be dynamically linked. | |
142 | ||
143 | # if there's only one gadget driver, using only two bulk endpoints, | |
144 | # don't waste memory for the other endpoints | |
145 | config USB_PXA25X_SMALL | |
146 | depends on USB_PXA25X | |
147 | bool | |
148 | default n if USB_ETH_RNDIS | |
149 | default y if USB_ZERO | |
150 | default y if USB_ETH | |
151 | default y if USB_G_SERIAL | |
152 | ||
153 | config USB_R8A66597 | |
154 | tristate "Renesas R8A66597 USB Peripheral Controller" | |
155 | depends on HAS_DMA | |
156 | help | |
157 | R8A66597 is a discrete USB host and peripheral controller chip that | |
158 | supports both full and high speed USB 2.0 data transfers. | |
159 | It has nine configurable endpoints, and endpoint zero. | |
160 | ||
161 | Say "y" to link the driver statically, or "m" to build a | |
162 | dynamically linked module called "r8a66597_udc" and force all | |
163 | gadget drivers to also be dynamically linked. | |
164 | ||
165 | config USB_RENESAS_USBHS_UDC | |
166 | tristate 'Renesas USBHS controller' | |
fa9a582d | 167 | depends on USB_RENESAS_USBHS && HAS_DMA |
90fccb52 AP |
168 | help |
169 | Renesas USBHS is a discrete USB host and peripheral controller chip | |
170 | that supports both full and high speed USB 2.0 data transfers. | |
171 | It has nine or more configurable endpoints, and endpoint zero. | |
172 | ||
173 | Say "y" to link the driver statically, or "m" to build a | |
174 | dynamically linked module called "renesas_usbhs" and force all | |
175 | gadget drivers to also be dynamically linked. | |
176 | ||
746bfe63 YS |
177 | config USB_RENESAS_USB3 |
178 | tristate 'Renesas USB3.0 Peripheral controller' | |
dd9fee67 | 179 | depends on ARCH_RENESAS || COMPILE_TEST |
746bfe63 YS |
180 | help |
181 | Renesas USB3.0 Peripheral controller is a USB peripheral controller | |
182 | that supports super, high, and full speed USB 3.0 data transfers. | |
183 | ||
184 | Say "y" to link the driver statically, or "m" to build a | |
185 | dynamically linked module called "renesas_usb3" and force all | |
186 | gadget drivers to also be dynamically linked. | |
187 | ||
90fccb52 AP |
188 | config USB_PXA27X |
189 | tristate "PXA 27x" | |
c470ba38 | 190 | depends on HAS_IOMEM |
90fccb52 AP |
191 | help |
192 | Intel's PXA 27x series XScale ARM v5TE processors include | |
193 | an integrated full speed USB 1.1 device controller. | |
194 | ||
195 | It has up to 23 endpoints, as well as endpoint zero (for | |
196 | control transfers). | |
197 | ||
198 | Say "y" to link the driver statically, or "m" to build a | |
199 | dynamically linked module called "pxa27x_udc" and force all | |
200 | gadget drivers to also be dynamically linked. | |
201 | ||
202 | config USB_S3C2410 | |
203 | tristate "S3C2410 USB Device Controller" | |
204 | depends on ARCH_S3C24XX | |
205 | help | |
206 | Samsung's S3C2410 is an ARM-4 processor with an integrated | |
207 | full speed USB 1.1 device controller. It has 4 configurable | |
208 | endpoints, as well as endpoint zero (for control transfers). | |
209 | ||
210 | This driver has been tested on the S3C2410, S3C2412, and | |
211 | S3C2440 processors. | |
212 | ||
213 | config USB_S3C2410_DEBUG | |
6341e62b | 214 | bool "S3C2410 udc debug messages" |
90fccb52 AP |
215 | depends on USB_S3C2410 |
216 | ||
217 | config USB_S3C_HSUDC | |
218 | tristate "S3C2416, S3C2443 and S3C2450 USB Device Controller" | |
219 | depends on ARCH_S3C24XX | |
220 | help | |
221 | Samsung's S3C2416, S3C2443 and S3C2450 is an ARM9 based SoC | |
222 | integrated with dual speed USB 2.0 device controller. It has | |
223 | 8 endpoints, as well as endpoint zero. | |
224 | ||
225 | This driver has been tested on S3C2416 and S3C2450 processors. | |
226 | ||
227 | config USB_MV_UDC | |
228 | tristate "Marvell USB2.0 Device Controller" | |
229 | depends on HAS_DMA | |
230 | help | |
231 | Marvell Socs (including PXA and MMP series) include a high speed | |
232 | USB2.0 OTG controller, which can be configured as high speed or | |
233 | full speed USB peripheral. | |
234 | ||
235 | config USB_MV_U3D | |
236 | depends on HAS_DMA | |
237 | tristate "MARVELL PXA2128 USB 3.0 controller" | |
238 | help | |
239 | MARVELL PXA2128 Processor series include a super speed USB3.0 device | |
240 | controller, which support super speed USB peripheral. | |
241 | ||
242 | # | |
243 | # Controllers available in both integrated and discrete versions | |
244 | # | |
245 | ||
246 | config USB_M66592 | |
247 | tristate "Renesas M66592 USB Peripheral Controller" | |
be6708e6 | 248 | depends on HAS_IOMEM |
90fccb52 AP |
249 | help |
250 | M66592 is a discrete USB peripheral controller chip that | |
251 | supports both full and high speed USB 2.0 data transfers. | |
252 | It has seven configurable endpoints, and endpoint zero. | |
253 | ||
254 | Say "y" to link the driver statically, or "m" to build a | |
255 | dynamically linked module called "m66592_udc" and force all | |
256 | gadget drivers to also be dynamically linked. | |
257 | ||
efed421a AP |
258 | source "drivers/usb/gadget/udc/bdc/Kconfig" |
259 | ||
90fccb52 AP |
260 | # |
261 | # Controllers available only in discrete form (and all PCI controllers) | |
262 | # | |
263 | ||
264 | config USB_AMD5536UDC | |
265 | tristate "AMD5536 UDC" | |
266 | depends on PCI | |
267 | help | |
268 | The AMD5536 UDC is part of the AMD Geode CS5536, an x86 southbridge. | |
269 | It is a USB Highspeed DMA capable USB device controller. Beside ep0 | |
270 | it provides 4 IN and 4 OUT endpoints (bulk or interrupt type). | |
271 | The UDC port supports OTG operation, and may be used as a host port | |
272 | if it's not being used to implement peripheral or OTG roles. | |
273 | ||
274 | Say "y" to link the driver statically, or "m" to build a | |
275 | dynamically linked module called "amd5536udc" and force all | |
276 | gadget drivers to also be dynamically linked. | |
277 | ||
278 | config USB_FSL_QE | |
279 | tristate "Freescale QE/CPM USB Device Controller" | |
280 | depends on FSL_SOC && (QUICC_ENGINE || CPM) | |
281 | help | |
282 | Some of Freescale PowerPC processors have a Full Speed | |
283 | QE/CPM2 USB controller, which support device mode with 4 | |
284 | programmable endpoints. This driver supports the | |
285 | controller in the MPC8360 and MPC8272, and should work with | |
286 | controllers having QE or CPM2, given minor tweaks. | |
287 | ||
288 | Set CONFIG_USB_GADGET to "m" to build this driver as a | |
289 | dynamically linked module called "fsl_qe_udc". | |
290 | ||
291 | config USB_NET2272 | |
7562b75b | 292 | depends on HAS_IOMEM |
90fccb52 AP |
293 | tristate "PLX NET2272" |
294 | help | |
295 | PLX NET2272 is a USB peripheral controller which supports | |
296 | both full and high speed USB 2.0 data transfers. | |
297 | ||
298 | It has three configurable endpoints, as well as endpoint zero | |
299 | (for control transfer). | |
300 | Say "y" to link the driver statically, or "m" to build a | |
301 | dynamically linked module called "net2272" and force all | |
302 | gadget drivers to also be dynamically linked. | |
303 | ||
304 | config USB_NET2272_DMA | |
6341e62b | 305 | bool "Support external DMA controller" |
90fccb52 AP |
306 | depends on USB_NET2272 && HAS_DMA |
307 | help | |
308 | The NET2272 part can optionally support an external DMA | |
309 | controller, but your board has to have support in the | |
310 | driver itself. | |
311 | ||
312 | If unsure, say "N" here. The driver works fine in PIO mode. | |
313 | ||
314 | config USB_NET2280 | |
5185c913 | 315 | tristate "NetChip NET228x / PLX USB3x8x" |
90fccb52 AP |
316 | depends on PCI |
317 | help | |
318 | NetChip 2280 / 2282 is a PCI based USB peripheral controller which | |
319 | supports both full and high speed USB 2.0 data transfers. | |
320 | ||
321 | It has six configurable endpoints, as well as endpoint zero | |
322 | (for control transfers) and several endpoints with dedicated | |
323 | functions. | |
324 | ||
5185c913 TH |
325 | PLX 2380 is a PCIe version of the PLX 2380. |
326 | ||
90fccb52 AP |
327 | PLX 3380 / 3382 is a PCIe based USB peripheral controller which |
328 | supports full, high speed USB 2.0 and super speed USB 3.0 | |
329 | data transfers. | |
330 | ||
331 | It has eight configurable endpoints, as well as endpoint zero | |
332 | (for control transfers) and several endpoints with dedicated | |
333 | functions. | |
334 | ||
335 | Say "y" to link the driver statically, or "m" to build a | |
336 | dynamically linked module called "net2280" and force all | |
337 | gadget drivers to also be dynamically linked. | |
338 | ||
339 | config USB_GOKU | |
340 | tristate "Toshiba TC86C001 'Goku-S'" | |
341 | depends on PCI | |
342 | help | |
343 | The Toshiba TC86C001 is a PCI device which includes controllers | |
344 | for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI). | |
345 | ||
346 | The device controller has three configurable (bulk or interrupt) | |
347 | endpoints, plus endpoint zero (for control transfers). | |
348 | ||
349 | Say "y" to link the driver statically, or "m" to build a | |
350 | dynamically linked module called "goku_udc" and to force all | |
351 | gadget drivers to also be dynamically linked. | |
352 | ||
353 | config USB_EG20T | |
a68df706 | 354 | tristate "Intel QUARK X1000/EG20T PCH/LAPIS Semiconductor IOH(ML7213/ML7831) UDC" |
90fccb52 AP |
355 | depends on PCI |
356 | help | |
357 | This is a USB device driver for EG20T PCH. | |
358 | EG20T PCH is the platform controller hub that is used in Intel's | |
359 | general embedded platform. EG20T PCH has USB device interface. | |
360 | Using this interface, it is able to access system devices connected | |
361 | to USB device. | |
362 | This driver enables USB device function. | |
363 | USB device is a USB peripheral controller which | |
364 | supports both full and high speed USB 2.0 data transfers. | |
365 | This driver supports both control transfer and bulk transfer modes. | |
366 | This driver dose not support interrupt transfer or isochronous | |
367 | transfer modes. | |
368 | ||
369 | This driver also can be used for LAPIS Semiconductor's ML7213 which is | |
370 | for IVI(In-Vehicle Infotainment) use. | |
371 | ML7831 is for general purpose use. | |
372 | ML7213/ML7831 is companion chip for Intel Atom E6xx series. | |
373 | ML7213/ML7831 is completely compatible for Intel EG20T PCH. | |
374 | ||
a68df706 | 375 | This driver can be used with Intel's Quark X1000 SOC platform |
1f7c5166 SSB |
376 | |
377 | config USB_GADGET_XILINX | |
378 | tristate "Xilinx USB Driver" | |
f1113be1 | 379 | depends on HAS_DMA |
1f7c5166 SSB |
380 | depends on OF || COMPILE_TEST |
381 | help | |
382 | USB peripheral controller driver for Xilinx USB2 device. | |
383 | Xilinx USB2 device is a soft IP which supports both full | |
384 | and high speed USB 2.0 data transfers. It has seven configurable | |
385 | endpoints(bulk or interrupt or isochronous), as well as | |
386 | endpoint zero(for control transfers). | |
387 | ||
388 | Say "y" to link the driver statically, or "m" to build a | |
389 | dynamically linked module called "udc-xilinx" and force all | |
390 | gadget drivers to also be dynamically linked. | |
391 | ||
90fccb52 AP |
392 | # |
393 | # LAST -- dummy/emulated controller | |
394 | # | |
395 | ||
396 | config USB_DUMMY_HCD | |
397 | tristate "Dummy HCD (DEVELOPMENT)" | |
398 | depends on USB=y || (USB=m && USB_GADGET=m) | |
399 | help | |
400 | This host controller driver emulates USB, looping all data transfer | |
401 | requests back to a USB "gadget driver" in the same host. The host | |
402 | side is the master; the gadget side is the slave. Gadget drivers | |
403 | can be high, full, or low speed; and they have access to endpoints | |
404 | like those from NET2280, PXA2xx, or SA1100 hardware. | |
405 | ||
406 | This may help in some stages of creating a driver to embed in a | |
407 | Linux device, since it lets you debug several parts of the gadget | |
408 | driver without its hardware or drivers being involved. | |
409 | ||
410 | Since such a gadget side driver needs to interoperate with a host | |
411 | side Linux-USB device driver, this may help to debug both sides | |
412 | of a USB protocol stack. | |
413 | ||
414 | Say "y" to link the driver statically, or "m" to build a | |
415 | dynamically linked module called "dummy_hcd" and force all | |
416 | gadget drivers to also be dynamically linked. | |
417 | ||
418 | # NOTE: Please keep dummy_hcd LAST so that "real hardware" appears | |
419 | # first and will be selected by default. | |
420 | ||
421 | endmenu |