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