]>
Commit | Line | Data |
---|---|---|
1da177e4 LT |
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). | |
cab00891 | 10 | # - Some systems have both kinds of controllers. |
1da177e4 LT |
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 | # | |
1da177e4 | 15 | |
b75be4ab DC |
16 | menuconfig USB_GADGET |
17 | tristate "USB Gadget Support" | |
1da177e4 LT |
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 | Linux 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 | |
e113f29c | 28 | familiar host side controllers have names like "EHCI", "OHCI", |
1da177e4 LT |
29 | or "UHCI", and are usually integrated into southbridges on PC |
30 | motherboards. | |
31 | ||
32 | Enable this configuration option if you want to run Linux 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. (If you use modular gadget drivers, | |
36 | you may configure more than one.) | |
37 | ||
38 | If in doubt, say "N" and don't enable these drivers; most people | |
39 | don't have this kind of hardware (except maybe inside Linux PDAs). | |
40 | ||
41 | For more information, see <http://www.linux-usb.org/gadget> and | |
42 | the kernel DocBook documentation for this API. | |
43 | ||
b75be4ab DC |
44 | if USB_GADGET |
45 | ||
70790f63 | 46 | config USB_GADGET_DEBUG |
afd0e0f2 | 47 | boolean "Debugging messages (DEVELOPMENT)" |
36e893d2 | 48 | depends on DEBUG_KERNEL |
70790f63 DB |
49 | help |
50 | Many controller and gadget drivers will print some debugging | |
51 | messages if you use this option to ask for those messages. | |
52 | ||
53 | Avoid enabling these messages, even if you're actively | |
54 | debugging such a driver. Many drivers will emit so many | |
55 | messages that the driver timings are affected, which will | |
56 | either create new failure modes or remove the one you're | |
57 | trying to track down. Never enable these messages for a | |
58 | production build. | |
59 | ||
1da177e4 | 60 | config USB_GADGET_DEBUG_FILES |
afd0e0f2 | 61 | boolean "Debugging information files (DEVELOPMENT)" |
36e893d2 | 62 | depends on PROC_FS |
1da177e4 LT |
63 | help |
64 | Some of the drivers in the "gadget" framework can expose | |
65 | debugging information in files such as /proc/driver/udc | |
66 | (for a peripheral controller). The information in these | |
67 | files may help when you're troubleshooting or bringing up a | |
68 | driver on a new board. Enable these files by choosing "Y" | |
69 | here. If in doubt, or to conserve kernel memory, say "N". | |
70 | ||
914a3f3b | 71 | config USB_GADGET_DEBUG_FS |
afd0e0f2 | 72 | boolean "Debugging information files in debugfs (DEVELOPMENT)" |
36e893d2 | 73 | depends on DEBUG_FS |
914a3f3b HS |
74 | help |
75 | Some of the drivers in the "gadget" framework can expose | |
76 | debugging information in files under /sys/kernel/debug/. | |
77 | The information in these files may help when you're | |
78 | troubleshooting or bringing up a driver on a new board. | |
79 | Enable these files by choosing "Y" here. If in doubt, or | |
80 | to conserve kernel memory, say "N". | |
81 | ||
36e893d2 DB |
82 | config USB_GADGET_VBUS_DRAW |
83 | int "Maximum VBUS Power usage (2-500 mA)" | |
84 | range 2 500 | |
85 | default 2 | |
86 | help | |
87 | Some devices need to draw power from USB when they are | |
88 | configured, perhaps to operate circuitry or to recharge | |
89 | batteries. This is in addition to any local power supply, | |
90 | such as an AC adapter or batteries. | |
91 | ||
92 | Enter the maximum power your device draws through USB, in | |
93 | milliAmperes. The permitted range of values is 2 - 500 mA; | |
94 | 0 mA would be legal, but can make some hosts misbehave. | |
95 | ||
96 | This value will be used except for system-specific gadget | |
97 | drivers that have more specific information. | |
98 | ||
1da177e4 LT |
99 | # |
100 | # USB Peripheral Controller Support | |
101 | # | |
a7a19fac DB |
102 | # The order here is alphabetical, except that integrated controllers go |
103 | # before discrete ones so they will be the initial/default value: | |
104 | # - integrated/SOC controllers first | |
105 | # - licensed IP used in both SOC and discrete versions | |
106 | # - discrete ones (including all PCI-only controllers) | |
107 | # - debug/dummy gadget+hcd is last. | |
108 | # | |
1da177e4 LT |
109 | choice |
110 | prompt "USB Peripheral Controller" | |
111 | depends on USB_GADGET | |
112 | help | |
113 | A USB device uses a controller to talk to its host. | |
114 | Systems should have only one such upstream link. | |
115 | Many controller drivers are platform-specific; these | |
116 | often need board-specific hooks. | |
117 | ||
a7a19fac DB |
118 | # |
119 | # Integrated controllers | |
120 | # | |
121 | ||
193ab2a6 FB |
122 | config USB_AT91 |
123 | tristate "Atmel AT91 USB Device Port" | |
aa781af0 | 124 | depends on ARCH_AT91 && !ARCH_AT91SAM9RL && !ARCH_AT91CAP9 && !ARCH_AT91SAM9G45 |
55d402d8 | 125 | help |
a7a19fac DB |
126 | Many Atmel AT91 processors (such as the AT91RM2000) have a |
127 | full speed USB Device Port with support for five configurable | |
128 | endpoints (plus endpoint zero). | |
55d402d8 TD |
129 | |
130 | Say "y" to link the driver statically, or "m" to build a | |
a7a19fac | 131 | dynamically linked module called "at91_udc" and force all |
55d402d8 TD |
132 | gadget drivers to also be dynamically linked. |
133 | ||
193ab2a6 FB |
134 | config USB_ATMEL_USBA |
135 | tristate "Atmel USBA" | |
914a3f3b | 136 | select USB_GADGET_DUALSPEED |
aa781af0 | 137 | depends on AVR32 || ARCH_AT91CAP9 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45 |
914a3f3b HS |
138 | help |
139 | USBA is the integrated high-speed USB Device controller on | |
ba45ca43 | 140 | the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel. |
914a3f3b | 141 | |
193ab2a6 FB |
142 | config USB_FSL_USB2 |
143 | tristate "Freescale Highspeed USB DR Peripheral Controller" | |
54e4026b | 144 | depends on FSL_SOC || ARCH_MXC |
b504882d | 145 | select USB_GADGET_DUALSPEED |
018b97d0 | 146 | select USB_FSL_MPH_DR_OF if OF |
b504882d LY |
147 | help |
148 | Some of Freescale PowerPC processors have a High Speed | |
149 | Dual-Role(DR) USB controller, which supports device mode. | |
150 | ||
151 | The number of programmable endpoints is different through | |
152 | SOC revisions. | |
153 | ||
154 | Say "y" to link the driver statically, or "m" to build a | |
155 | dynamically linked module called "fsl_usb2_udc" and force | |
156 | all gadget drivers to also be dynamically linked. | |
157 | ||
193ab2a6 FB |
158 | config USB_FUSB300 |
159 | tristate "Faraday FUSB300 USB Peripheral Controller" | |
ac17317d | 160 | depends on !PHYS_ADDR_T_64BIT |
0fe6f1d1 YHC |
161 | select USB_GADGET_DUALSPEED |
162 | help | |
163 | Faraday usb device controller FUSB300 driver | |
164 | ||
193ab2a6 FB |
165 | config USB_OMAP |
166 | tristate "OMAP USB Device Controller" | |
a7a19fac | 167 | depends on ARCH_OMAP |
f1c9e151 | 168 | select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_H4_OTG |
54b9ed35 | 169 | select USB_OTG_UTILS if ARCH_OMAP |
a7a19fac DB |
170 | help |
171 | Many Texas Instruments OMAP processors have flexible full | |
172 | speed USB device controllers, with support for up to 30 | |
173 | endpoints (plus endpoint zero). This driver supports the | |
174 | controller in the OMAP 1611, and should work with controllers | |
175 | in other OMAP processors too, given minor tweaks. | |
1da177e4 LT |
176 | |
177 | Say "y" to link the driver statically, or "m" to build a | |
a7a19fac | 178 | dynamically linked module called "omap_udc" and force all |
1da177e4 LT |
179 | gadget drivers to also be dynamically linked. |
180 | ||
193ab2a6 FB |
181 | config USB_PXA25X |
182 | tristate "PXA 25x or IXP 4xx" | |
1da177e4 | 183 | depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX |
09963911 | 184 | select USB_OTG_UTILS |
1da177e4 LT |
185 | help |
186 | Intel's PXA 25x series XScale ARM-5TE processors include | |
187 | an integrated full speed USB 1.1 device controller. The | |
188 | controller in the IXP 4xx series is register-compatible. | |
189 | ||
190 | It has fifteen fixed-function endpoints, as well as endpoint | |
191 | zero (for control transfers). | |
192 | ||
193 | Say "y" to link the driver statically, or "m" to build a | |
7a857620 | 194 | dynamically linked module called "pxa25x_udc" and force all |
1da177e4 LT |
195 | gadget drivers to also be dynamically linked. |
196 | ||
1da177e4 LT |
197 | # if there's only one gadget driver, using only two bulk endpoints, |
198 | # don't waste memory for the other endpoints | |
7a857620 | 199 | config USB_PXA25X_SMALL |
193ab2a6 | 200 | depends on USB_PXA25X |
1da177e4 LT |
201 | bool |
202 | default n if USB_ETH_RNDIS | |
203 | default y if USB_ZERO | |
204 | default y if USB_ETH | |
205 | default y if USB_G_SERIAL | |
206 | ||
193ab2a6 FB |
207 | config USB_R8A66597 |
208 | tristate "Renesas R8A66597 USB Peripheral Controller" | |
c4144247 YS |
209 | select USB_GADGET_DUALSPEED |
210 | help | |
211 | R8A66597 is a discrete USB host and peripheral controller chip that | |
212 | supports both full and high speed USB 2.0 data transfers. | |
213 | It has nine configurable endpoints, and endpoint zero. | |
214 | ||
215 | Say "y" to link the driver statically, or "m" to build a | |
216 | dynamically linked module called "r8a66597_udc" and force all | |
217 | gadget drivers to also be dynamically linked. | |
218 | ||
030ed1fc | 219 | config USB_RENESAS_USBHS_UDC |
193ab2a6 FB |
220 | tristate 'Renesas USBHS controller' |
221 | depends on SUPERH || ARCH_SHMOBILE | |
030ed1fc KM |
222 | depends on USB_RENESAS_USBHS |
223 | select USB_GADGET_DUALSPEED | |
2f98382d | 224 | help |
193ab2a6 FB |
225 | Renesas USBHS is a discrete USB host and peripheral controller chip |
226 | that supports both full and high speed USB 2.0 data transfers. | |
227 | It has nine or more configurable endpoints, and endpoint zero. | |
2f98382d | 228 | |
193ab2a6 FB |
229 | Say "y" to link the driver statically, or "m" to build a |
230 | dynamically linked module called "renesas_usbhs" and force all | |
231 | gadget drivers to also be dynamically linked. | |
2f98382d | 232 | |
193ab2a6 FB |
233 | config USB_PXA27X |
234 | tristate "PXA 27x" | |
9f5351b7 | 235 | depends on ARCH_PXA && (PXA27x || PXA3xx) |
7fec3c25 | 236 | select USB_OTG_UTILS |
d75379a5 RJ |
237 | help |
238 | Intel's PXA 27x series XScale ARM v5TE processors include | |
239 | an integrated full speed USB 1.1 device controller. | |
240 | ||
241 | It has up to 23 endpoints, as well as endpoint zero (for | |
242 | control transfers). | |
243 | ||
244 | Say "y" to link the driver statically, or "m" to build a | |
245 | dynamically linked module called "pxa27x_udc" and force all | |
246 | gadget drivers to also be dynamically linked. | |
247 | ||
193ab2a6 FB |
248 | config USB_S3C_HSOTG |
249 | tristate "S3C HS/OtG USB Device controller" | |
5b7d70c6 BD |
250 | depends on S3C_DEV_USB_HSOTG |
251 | select USB_GADGET_S3C_HSOTG_PIO | |
0287e43d | 252 | select USB_GADGET_DUALSPEED |
5b7d70c6 BD |
253 | help |
254 | The Samsung S3C64XX USB2.0 high-speed gadget controller | |
255 | integrated into the S3C64XX series SoC. | |
256 | ||
193ab2a6 FB |
257 | config USB_IMX |
258 | tristate "Freescale IMX USB Peripheral Controller" | |
c03e7d4b PZ |
259 | depends on ARCH_MX1 |
260 | help | |
261 | Freescale's IMX series include an integrated full speed | |
262 | USB 1.1 device controller. The controller in the IMX series | |
263 | is register-compatible. | |
264 | ||
265 | It has Six fixed-function endpoints, as well as endpoint | |
266 | zero (for control transfers). | |
267 | ||
268 | Say "y" to link the driver statically, or "m" to build a | |
269 | dynamically linked module called "imx_udc" and force all | |
270 | gadget drivers to also be dynamically linked. | |
271 | ||
193ab2a6 FB |
272 | config USB_S3C2410 |
273 | tristate "S3C2410 USB Device Controller" | |
a7a19fac | 274 | depends on ARCH_S3C2410 |
1da177e4 | 275 | help |
a7a19fac DB |
276 | Samsung's S3C2410 is an ARM-4 processor with an integrated |
277 | full speed USB 1.1 device controller. It has 4 configurable | |
278 | endpoints, as well as endpoint zero (for control transfers). | |
1da177e4 | 279 | |
a7a19fac DB |
280 | This driver has been tested on the S3C2410, S3C2412, and |
281 | S3C2440 processors. | |
1da177e4 | 282 | |
a7a19fac DB |
283 | config USB_S3C2410_DEBUG |
284 | boolean "S3C2410 udc debug messages" | |
193ab2a6 | 285 | depends on USB_S3C2410 |
1da177e4 | 286 | |
193ab2a6 FB |
287 | config USB_S3C_HSUDC |
288 | tristate "S3C2416, S3C2443 and S3C2450 USB Device Controller" | |
a9df304c TA |
289 | depends on ARCH_S3C2410 |
290 | select USB_GADGET_DUALSPEED | |
291 | help | |
292 | Samsung's S3C2416, S3C2443 and S3C2450 is an ARM9 based SoC | |
293 | integrated with dual speed USB 2.0 device controller. It has | |
294 | 8 endpoints, as well as endpoint zero. | |
295 | ||
296 | This driver has been tested on S3C2416 and S3C2450 processors. | |
297 | ||
193ab2a6 FB |
298 | config USB_PXA_U2O |
299 | tristate "PXA9xx Processor USB2.0 controller" | |
300 | depends on ARCH_MMP | |
e7cddda4 | 301 | select USB_GADGET_DUALSPEED |
302 | help | |
303 | PXA9xx Processor series include a high speed USB2.0 device | |
304 | controller, which support high speed and full speed USB peripheral. | |
305 | ||
72246da4 FB |
306 | config USB_GADGET_DWC3 |
307 | tristate "DesignWare USB3.0 (DRD) Controller" | |
308 | depends on USB_DWC3 | |
309 | select USB_GADGET_DUALSPEED | |
310 | select USB_GADGET_SUPERSPEED | |
311 | help | |
312 | DesignWare USB3.0 controller is a SuperSpeed USB3.0 Controller | |
313 | which can be configured for peripheral-only, host-only, hub-only | |
314 | and Dual-Role operation. This Controller was first integrated into | |
315 | the OMAP5 series of processors. More information about the OMAP5 | |
316 | version of this controller, refer to http://www.ti.com/omap5. | |
317 | ||
a7a19fac DB |
318 | # |
319 | # Controllers available in both integrated and discrete versions | |
320 | # | |
1da177e4 | 321 | |
a7a19fac | 322 | # musb builds in ../musb along with host support |
550a7375 | 323 | config USB_GADGET_MUSB_HDRC |
193ab2a6 | 324 | tristate "Inventra HDRC USB Peripheral (TI, ADI, ...)" |
b61ae342 | 325 | depends on USB_MUSB_HDRC |
550a7375 | 326 | select USB_GADGET_DUALSPEED |
550a7375 FB |
327 | help |
328 | This OTG-capable silicon IP is used in dual designs including | |
085ad406 | 329 | the TI DaVinci, OMAP 243x, OMAP 343x, TUSB 6010, and ADI Blackfin |
550a7375 | 330 | |
193ab2a6 FB |
331 | config USB_M66592 |
332 | tristate "Renesas M66592 USB Peripheral Controller" | |
a7a19fac | 333 | select USB_GADGET_DUALSPEED |
1da177e4 | 334 | help |
a7a19fac DB |
335 | M66592 is a discrete USB peripheral controller chip that |
336 | supports both full and high speed USB 2.0 data transfers. | |
337 | It has seven configurable endpoints, and endpoint zero. | |
1da177e4 LT |
338 | |
339 | Say "y" to link the driver statically, or "m" to build a | |
a7a19fac | 340 | dynamically linked module called "m66592_udc" and force all |
1da177e4 LT |
341 | gadget drivers to also be dynamically linked. |
342 | ||
a7a19fac DB |
343 | # |
344 | # Controllers available only in discrete form (and all PCI controllers) | |
345 | # | |
346 | ||
193ab2a6 FB |
347 | config USB_AMD5536UDC |
348 | tristate "AMD5536 UDC" | |
a7a19fac DB |
349 | depends on PCI |
350 | select USB_GADGET_DUALSPEED | |
3fc154b6 | 351 | help |
a7a19fac DB |
352 | The AMD5536 UDC is part of the AMD Geode CS5536, an x86 southbridge. |
353 | It is a USB Highspeed DMA capable USB device controller. Beside ep0 | |
354 | it provides 4 IN and 4 OUT endpoints (bulk or interrupt type). | |
355 | The UDC port supports OTG operation, and may be used as a host port | |
356 | if it's not being used to implement peripheral or OTG roles. | |
3fc154b6 | 357 | |
a7a19fac DB |
358 | Say "y" to link the driver statically, or "m" to build a |
359 | dynamically linked module called "amd5536udc" and force all | |
360 | gadget drivers to also be dynamically linked. | |
3fc154b6 | 361 | |
193ab2a6 FB |
362 | config USB_FSL_QE |
363 | tristate "Freescale QE/CPM USB Device Controller" | |
3948f0e0 LY |
364 | depends on FSL_SOC && (QUICC_ENGINE || CPM) |
365 | help | |
366 | Some of Freescale PowerPC processors have a Full Speed | |
367 | QE/CPM2 USB controller, which support device mode with 4 | |
368 | programmable endpoints. This driver supports the | |
369 | controller in the MPC8360 and MPC8272, and should work with | |
370 | controllers having QE or CPM2, given minor tweaks. | |
371 | ||
372 | Set CONFIG_USB_GADGET to "m" to build this driver as a | |
692105b8 | 373 | dynamically linked module called "fsl_qe_udc". |
3948f0e0 | 374 | |
193ab2a6 FB |
375 | config USB_CI13XXX_PCI |
376 | tristate "MIPS USB CI13xxx PCI UDC" | |
aa69a809 DL |
377 | depends on PCI |
378 | select USB_GADGET_DUALSPEED | |
379 | help | |
380 | MIPS USB IP core family device controller | |
381 | Currently it only supports IP part number CI13412 | |
382 | ||
383 | Say "y" to link the driver statically, or "m" to build a | |
384 | dynamically linked module called "ci13xxx_udc" and force all | |
385 | gadget drivers to also be dynamically linked. | |
386 | ||
193ab2a6 FB |
387 | config USB_NET2272 |
388 | tristate "PLX NET2272" | |
ceb80363 SL |
389 | select USB_GADGET_DUALSPEED |
390 | help | |
391 | PLX NET2272 is a USB peripheral controller which supports | |
392 | both full and high speed USB 2.0 data transfers. | |
393 | ||
394 | It has three configurable endpoints, as well as endpoint zero | |
395 | (for control transfer). | |
396 | Say "y" to link the driver statically, or "m" to build a | |
397 | dynamically linked module called "net2272" and force all | |
398 | gadget drivers to also be dynamically linked. | |
399 | ||
193ab2a6 | 400 | config USB_NET2272_DMA |
ceb80363 | 401 | boolean "Support external DMA controller" |
193ab2a6 | 402 | depends on USB_NET2272 |
ceb80363 SL |
403 | help |
404 | The NET2272 part can optionally support an external DMA | |
405 | controller, but your board has to have support in the | |
406 | driver itself. | |
407 | ||
408 | If unsure, say "N" here. The driver works fine in PIO mode. | |
409 | ||
193ab2a6 FB |
410 | config USB_NET2280 |
411 | tristate "NetChip 228x" | |
a7a19fac DB |
412 | depends on PCI |
413 | select USB_GADGET_DUALSPEED | |
414 | help | |
415 | NetChip 2280 / 2282 is a PCI based USB peripheral controller which | |
416 | supports both full and high speed USB 2.0 data transfers. | |
3fc154b6 | 417 | |
a7a19fac DB |
418 | It has six configurable endpoints, as well as endpoint zero |
419 | (for control transfers) and several endpoints with dedicated | |
420 | functions. | |
421 | ||
422 | Say "y" to link the driver statically, or "m" to build a | |
423 | dynamically linked module called "net2280" and force all | |
424 | gadget drivers to also be dynamically linked. | |
425 | ||
193ab2a6 FB |
426 | config USB_GOKU |
427 | tristate "Toshiba TC86C001 'Goku-S'" | |
a7a19fac | 428 | depends on PCI |
bae4bd84 | 429 | help |
a7a19fac DB |
430 | The Toshiba TC86C001 is a PCI device which includes controllers |
431 | for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI). | |
432 | ||
433 | The device controller has three configurable (bulk or interrupt) | |
434 | endpoints, plus endpoint zero (for control transfers). | |
bae4bd84 DB |
435 | |
436 | Say "y" to link the driver statically, or "m" to build a | |
a7a19fac | 437 | dynamically linked module called "goku_udc" and to force all |
bae4bd84 DB |
438 | gadget drivers to also be dynamically linked. |
439 | ||
193ab2a6 FB |
440 | config USB_LANGWELL |
441 | tristate "Intel Langwell USB Device Controller" | |
5be19a9d | 442 | depends on PCI |
ac17317d | 443 | depends on !PHYS_ADDR_T_64BIT |
5be19a9d XS |
444 | select USB_GADGET_DUALSPEED |
445 | help | |
446 | Intel Langwell USB Device Controller is a High-Speed USB | |
447 | On-The-Go device controller. | |
448 | ||
449 | The number of programmable endpoints is different through | |
450 | controller revision. | |
451 | ||
452 | Say "y" to link the driver statically, or "m" to build a | |
453 | dynamically linked module called "langwell_udc" and force all | |
454 | gadget drivers to also be dynamically linked. | |
455 | ||
193ab2a6 FB |
456 | config USB_EG20T |
457 | tristate "Intel EG20T PCH/OKI SEMICONDUCTOR ML7213 IOH UDC" | |
f646cf94 TO |
458 | depends on PCI |
459 | select USB_GADGET_DUALSPEED | |
460 | help | |
461 | This is a USB device driver for EG20T PCH. | |
462 | EG20T PCH is the platform controller hub that is used in Intel's | |
463 | general embedded platform. EG20T PCH has USB device interface. | |
464 | Using this interface, it is able to access system devices connected | |
465 | to USB device. | |
466 | This driver enables USB device function. | |
467 | USB device is a USB peripheral controller which | |
468 | supports both full and high speed USB 2.0 data transfers. | |
469 | This driver supports both control transfer and bulk transfer modes. | |
470 | This driver dose not support interrupt transfer or isochronous | |
471 | transfer modes. | |
472 | ||
06f1b971 TM |
473 | This driver also can be used for OKI SEMICONDUCTOR's ML7213 which is |
474 | for IVI(In-Vehicle Infotainment) use. | |
475 | ML7213 is companion chip for Intel Atom E6xx series. | |
476 | ML7213 is completely compatible for Intel EG20T PCH. | |
477 | ||
193ab2a6 FB |
478 | config USB_CI13XXX_MSM |
479 | tristate "MIPS USB CI13xxx for MSM" | |
33f82f38 PK |
480 | depends on ARCH_MSM |
481 | select USB_GADGET_DUALSPEED | |
dfb2130c | 482 | select USB_MSM_OTG |
33f82f38 PK |
483 | help |
484 | MSM SoC has chipidea USB controller. This driver uses | |
485 | ci13xxx_udc core. | |
486 | This driver depends on OTG driver for PHY initialization, | |
487 | clock management, powering up VBUS, and power management. | |
8cf28f1f PK |
488 | This driver is not supported on boards like trout which |
489 | has an external PHY. | |
33f82f38 PK |
490 | |
491 | Say "y" to link the driver statically, or "m" to build a | |
492 | dynamically linked module called "ci13xxx_msm" and force all | |
493 | gadget drivers to also be dynamically linked. | |
494 | ||
a7a19fac DB |
495 | # |
496 | # LAST -- dummy/emulated controller | |
497 | # | |
1da177e4 | 498 | |
193ab2a6 FB |
499 | config USB_DUMMY_HCD |
500 | tristate "Dummy HCD (DEVELOPMENT)" | |
afd0e0f2 | 501 | depends on USB=y || (USB=m && USB_GADGET=m) |
1da177e4 | 502 | select USB_GADGET_DUALSPEED |
1cd8fd28 | 503 | select USB_GADGET_SUPERSPEED |
1da177e4 LT |
504 | help |
505 | This host controller driver emulates USB, looping all data transfer | |
506 | requests back to a USB "gadget driver" in the same host. The host | |
507 | side is the master; the gadget side is the slave. Gadget drivers | |
508 | can be high, full, or low speed; and they have access to endpoints | |
509 | like those from NET2280, PXA2xx, or SA1100 hardware. | |
193ab2a6 | 510 | |
1da177e4 LT |
511 | This may help in some stages of creating a driver to embed in a |
512 | Linux device, since it lets you debug several parts of the gadget | |
513 | driver without its hardware or drivers being involved. | |
193ab2a6 | 514 | |
1da177e4 LT |
515 | Since such a gadget side driver needs to interoperate with a host |
516 | side Linux-USB device driver, this may help to debug both sides | |
517 | of a USB protocol stack. | |
518 | ||
519 | Say "y" to link the driver statically, or "m" to build a | |
520 | dynamically linked module called "dummy_hcd" and force all | |
521 | gadget drivers to also be dynamically linked. | |
522 | ||
1da177e4 LT |
523 | # NOTE: Please keep dummy_hcd LAST so that "real hardware" appears |
524 | # first and will be selected by default. | |
525 | ||
526 | endchoice | |
527 | ||
97b2f900 | 528 | # Selected by UDC drivers that support high-speed operation. |
1da177e4 LT |
529 | config USB_GADGET_DUALSPEED |
530 | bool | |
531 | depends on USB_GADGET | |
1da177e4 | 532 | |
bdb64d72 TB |
533 | # Selected by UDC drivers that support super-speed opperation |
534 | config USB_GADGET_SUPERSPEED | |
535 | bool | |
536 | depends on USB_GADGET | |
537 | depends on USB_GADGET_DUALSPEED | |
538 | ||
1da177e4 LT |
539 | # |
540 | # USB Gadget Drivers | |
541 | # | |
542 | choice | |
543 | tristate "USB Gadget Drivers" | |
193ab2a6 | 544 | depends on USB_GADGET |
1da177e4 LT |
545 | default USB_ETH |
546 | help | |
547 | A Linux "Gadget Driver" talks to the USB Peripheral Controller | |
548 | driver through the abstract "gadget" API. Some other operating | |
549 | systems call these "client" drivers, of which "class drivers" | |
550 | are a subset (implementing a USB device class specification). | |
551 | A gadget driver implements one or more USB functions using | |
552 | the peripheral hardware. | |
553 | ||
554 | Gadget drivers are hardware-neutral, or "platform independent", | |
555 | except that they sometimes must understand quirks or limitations | |
556 | of the particular controllers they work with. For example, when | |
557 | a controller doesn't support alternate configurations or provide | |
558 | enough of the right types of endpoints, the gadget driver might | |
559 | not be able work with that controller, or might need to implement | |
560 | a less common variant of a device class protocol. | |
561 | ||
562 | # this first set of drivers all depend on bulk-capable hardware. | |
563 | ||
564 | config USB_ZERO | |
565 | tristate "Gadget Zero (DEVELOPMENT)" | |
1da177e4 LT |
566 | help |
567 | Gadget Zero is a two-configuration device. It either sinks and | |
568 | sources bulk data; or it loops back a configurable number of | |
569 | transfers. It also implements control requests, for "chapter 9" | |
570 | conformance. The driver needs only two bulk-capable endpoints, so | |
571 | it can work on top of most device-side usb controllers. It's | |
572 | useful for testing, and is also a working example showing how | |
573 | USB "gadget drivers" can be written. | |
574 | ||
575 | Make this be the first driver you try using on top of any new | |
576 | USB peripheral controller driver. Then you can use host-side | |
577 | test software, like the "usbtest" driver, to put your hardware | |
578 | and its driver through a basic set of functional tests. | |
579 | ||
580 | Gadget Zero also works with the host-side "usb-skeleton" driver, | |
581 | and with many kinds of host-side test software. You may need | |
582 | to tweak product and vendor IDs before host software knows about | |
583 | this device, and arrange to select an appropriate configuration. | |
584 | ||
585 | Say "y" to link the driver statically, or "m" to build a | |
586 | dynamically linked module called "g_zero". | |
587 | ||
588 | config USB_ZERO_HNPTEST | |
589 | boolean "HNP Test Device" | |
590 | depends on USB_ZERO && USB_OTG | |
591 | help | |
592 | You can configure this device to enumerate using the device | |
593 | identifiers of the USB-OTG test device. That means that when | |
594 | this gadget connects to another OTG device, with this one using | |
595 | the "B-Peripheral" role, that device will use HNP to let this | |
596 | one serve as the USB host instead (in the "B-Host" role). | |
597 | ||
c6994e6f BW |
598 | config USB_AUDIO |
599 | tristate "Audio Gadget (EXPERIMENTAL)" | |
600 | depends on SND | |
04950737 | 601 | select SND_PCM |
c6994e6f BW |
602 | help |
603 | Gadget Audio is compatible with USB Audio Class specification 1.0. | |
604 | It will include at least one AudioControl interface, zero or more | |
605 | AudioStream interface and zero or more MIDIStream interface. | |
606 | ||
607 | Gadget Audio will use on-board ALSA (CONFIG_SND) audio card to | |
608 | playback or capture audio stream. | |
609 | ||
610 | Say "y" to link the driver statically, or "m" to build a | |
611 | dynamically linked module called "g_audio". | |
612 | ||
1da177e4 LT |
613 | config USB_ETH |
614 | tristate "Ethernet Gadget (with CDC Ethernet support)" | |
615 | depends on NET | |
9e221be8 | 616 | select CRC32 |
1da177e4 | 617 | help |
9b39e9dd BN |
618 | This driver implements Ethernet style communication, in one of |
619 | several ways: | |
1da177e4 LT |
620 | |
621 | - The "Communication Device Class" (CDC) Ethernet Control Model. | |
622 | That protocol is often avoided with pure Ethernet adapters, in | |
623 | favor of simpler vendor-specific hardware, but is widely | |
624 | supported by firmware for smart network devices. | |
625 | ||
626 | - On hardware can't implement that protocol, a simple CDC subset | |
627 | is used, placing fewer demands on USB. | |
628 | ||
9b39e9dd BN |
629 | - CDC Ethernet Emulation Model (EEM) is a newer standard that has |
630 | a simpler interface that can be used by more USB hardware. | |
631 | ||
632 | RNDIS support is an additional option, more demanding than than | |
633 | subset. | |
1da177e4 LT |
634 | |
635 | Within the USB device, this gadget driver exposes a network device | |
636 | "usbX", where X depends on what other networking devices you have. | |
637 | Treat it like a two-node Ethernet link: host, and gadget. | |
638 | ||
639 | The Linux-USB host-side "usbnet" driver interoperates with this | |
640 | driver, so that deep I/O queues can be supported. On 2.4 kernels, | |
641 | use "CDCEther" instead, if you're using the CDC option. That CDC | |
642 | mode should also interoperate with standard CDC Ethernet class | |
643 | drivers on other host operating systems. | |
644 | ||
645 | Say "y" to link the driver statically, or "m" to build a | |
646 | dynamically linked module called "g_ether". | |
647 | ||
648 | config USB_ETH_RNDIS | |
afd0e0f2 RD |
649 | bool "RNDIS support" |
650 | depends on USB_ETH | |
1da177e4 LT |
651 | default y |
652 | help | |
653 | Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol, | |
654 | and Microsoft provides redistributable binary RNDIS drivers for | |
655 | older versions of Windows. | |
656 | ||
657 | If you say "y" here, the Ethernet gadget driver will try to provide | |
658 | a second device configuration, supporting RNDIS to talk to such | |
659 | Microsoft USB hosts. | |
660 | ||
661 | To make MS-Windows work with this, use Documentation/usb/linux.inf | |
662 | as the "driver info file". For versions of MS-Windows older than | |
663 | XP, you'll need to download drivers from Microsoft's website; a URL | |
664 | is given in comments found in that info file. | |
665 | ||
9b39e9dd BN |
666 | config USB_ETH_EEM |
667 | bool "Ethernet Emulation Model (EEM) support" | |
668 | depends on USB_ETH | |
669 | default n | |
670 | help | |
671 | CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM | |
672 | and therefore can be supported by more hardware. Technically ECM and | |
673 | EEM are designed for different applications. The ECM model extends | |
674 | the network interface to the target (e.g. a USB cable modem), and the | |
675 | EEM model is for mobile devices to communicate with hosts using | |
676 | ethernet over USB. For Linux gadgets, however, the interface with | |
677 | the host is the same (a usbX device), so the differences are minimal. | |
678 | ||
679 | If you say "y" here, the Ethernet gadget driver will use the EEM | |
680 | protocol rather than ECM. If unsure, say "n". | |
681 | ||
6c34d288 YK |
682 | config USB_G_NCM |
683 | tristate "Network Control Model (NCM) support" | |
684 | depends on NET | |
685 | select CRC32 | |
686 | help | |
687 | This driver implements USB CDC NCM subclass standard. NCM is | |
688 | an advanced protocol for Ethernet encapsulation, allows grouping | |
689 | of several ethernet frames into one USB transfer and diffferent | |
690 | alignment possibilities. | |
691 | ||
692 | Say "y" to link the driver statically, or "m" to build a | |
693 | dynamically linked module called "g_ncm". | |
694 | ||
1da177e4 LT |
695 | config USB_GADGETFS |
696 | tristate "Gadget Filesystem (EXPERIMENTAL)" | |
697 | depends on EXPERIMENTAL | |
698 | help | |
699 | This driver provides a filesystem based API that lets user mode | |
700 | programs implement a single-configuration USB device, including | |
701 | endpoint I/O and control requests that don't relate to enumeration. | |
702 | All endpoints, transfer speeds, and transfer types supported by | |
703 | the hardware are available, through read() and write() calls. | |
704 | ||
afd0e0f2 RD |
705 | Currently, this option is still labelled as EXPERIMENTAL because |
706 | of existing race conditions in the underlying in-kernel AIO core. | |
707 | ||
1da177e4 LT |
708 | Say "y" to link the driver statically, or "m" to build a |
709 | dynamically linked module called "gadgetfs". | |
710 | ||
c6c56008 MN |
711 | config USB_FUNCTIONFS |
712 | tristate "Function Filesystem (EXPERIMENTAL)" | |
713 | depends on EXPERIMENTAL | |
f8dae531 | 714 | select USB_FUNCTIONFS_GENERIC if !(USB_FUNCTIONFS_ETH || USB_FUNCTIONFS_RNDIS) |
c6c56008 | 715 | help |
eabf0f5f MP |
716 | The Function Filesystem (FunctionFS) lets one create USB |
717 | composite functions in user space in the same way GadgetFS | |
c6c56008 MN |
718 | lets one create USB gadgets in user space. This allows creation |
719 | of composite gadgets such that some of the functions are | |
720 | implemented in kernel space (for instance Ethernet, serial or | |
721 | mass storage) and other are implemented in user space. | |
722 | ||
f8dae531 MN |
723 | If you say "y" or "m" here you will be able what kind of |
724 | configurations the gadget will provide. | |
725 | ||
c6c56008 MN |
726 | Say "y" to link the driver statically, or "m" to build |
727 | a dynamically linked module called "g_ffs". | |
728 | ||
729 | config USB_FUNCTIONFS_ETH | |
f8dae531 | 730 | bool "Include configuration with CDC ECM (Ethernet)" |
17b2765e | 731 | depends on USB_FUNCTIONFS && NET |
c6c56008 | 732 | help |
eabf0f5f MP |
733 | Include a configuration with CDC ECM function (Ethernet) and the |
734 | Function Filesystem. | |
c6c56008 MN |
735 | |
736 | config USB_FUNCTIONFS_RNDIS | |
f8dae531 | 737 | bool "Include configuration with RNDIS (Ethernet)" |
17b2765e | 738 | depends on USB_FUNCTIONFS && NET |
c6c56008 | 739 | help |
eabf0f5f | 740 | Include a configuration with RNDIS function (Ethernet) and the Filesystem. |
c6c56008 MN |
741 | |
742 | config USB_FUNCTIONFS_GENERIC | |
743 | bool "Include 'pure' configuration" | |
f8dae531 | 744 | depends on USB_FUNCTIONFS |
c6c56008 | 745 | help |
f8dae531 MN |
746 | Include a configuration with the Function Filesystem alone with |
747 | no Ethernet interface. | |
c6c56008 | 748 | |
1da177e4 | 749 | config USB_FILE_STORAGE |
664a51a8 | 750 | tristate "File-backed Storage Gadget (DEPRECATED)" |
87840289 | 751 | depends on BLOCK |
1da177e4 LT |
752 | help |
753 | The File-backed Storage Gadget acts as a USB Mass Storage | |
754 | disk drive. As its storage repository it can use a regular | |
755 | file or a block device (in much the same way as the "loop" | |
756 | device driver), specified as a module parameter. | |
757 | ||
758 | Say "y" to link the driver statically, or "m" to build a | |
759 | dynamically linked module called "g_file_storage". | |
760 | ||
664a51a8 AS |
761 | NOTE: This driver is deprecated. Its replacement is the |
762 | Mass Storage Gadget. | |
763 | ||
1da177e4 LT |
764 | config USB_FILE_STORAGE_TEST |
765 | bool "File-backed Storage Gadget testing version" | |
766 | depends on USB_FILE_STORAGE | |
767 | default n | |
768 | help | |
769 | Say "y" to generate the larger testing version of the | |
770 | File-backed Storage Gadget, useful for probing the | |
771 | behavior of USB Mass Storage hosts. Not needed for | |
772 | normal operation. | |
773 | ||
d23b0f08 MN |
774 | config USB_MASS_STORAGE |
775 | tristate "Mass Storage Gadget" | |
776 | depends on BLOCK | |
777 | help | |
778 | The Mass Storage Gadget acts as a USB Mass Storage disk drive. | |
779 | As its storage repository it can use a regular file or a block | |
780 | device (in much the same way as the "loop" device driver), | |
781 | specified as a module parameter or sysfs option. | |
782 | ||
664a51a8 AS |
783 | This driver is an updated replacement for the deprecated |
784 | File-backed Storage Gadget (g_file_storage). | |
d23b0f08 MN |
785 | |
786 | Say "y" to link the driver statically, or "m" to build | |
664a51a8 | 787 | a dynamically linked module called "g_mass_storage". |
d23b0f08 | 788 | |
1da177e4 | 789 | config USB_G_SERIAL |
3086775a | 790 | tristate "Serial Gadget (with CDC ACM and CDC OBEX support)" |
1da177e4 LT |
791 | help |
792 | The Serial Gadget talks to the Linux-USB generic serial driver. | |
793 | This driver supports a CDC-ACM module option, which can be used | |
794 | to interoperate with MS-Windows hosts or with the Linux-USB | |
795 | "cdc-acm" driver. | |
796 | ||
3086775a FB |
797 | This driver also supports a CDC-OBEX option. You will need a |
798 | user space OBEX server talking to /dev/ttyGS*, since the kernel | |
799 | itself doesn't implement the OBEX protocol. | |
800 | ||
1da177e4 LT |
801 | Say "y" to link the driver statically, or "m" to build a |
802 | dynamically linked module called "g_serial". | |
803 | ||
804 | For more information, see Documentation/usb/gadget_serial.txt | |
805 | which includes instructions and a "driver info file" needed to | |
3086775a | 806 | make MS-Windows work with CDC ACM. |
1da177e4 | 807 | |
f2ebf92c BW |
808 | config USB_MIDI_GADGET |
809 | tristate "MIDI Gadget (EXPERIMENTAL)" | |
810 | depends on SND && EXPERIMENTAL | |
811 | select SND_RAWMIDI | |
812 | help | |
813 | The MIDI Gadget acts as a USB Audio device, with one MIDI | |
814 | input and one MIDI output. These MIDI jacks appear as | |
815 | a sound "card" in the ALSA sound system. Other MIDI | |
816 | connections can then be made on the gadget system, using | |
817 | ALSA's aconnect utility etc. | |
818 | ||
819 | Say "y" to link the driver statically, or "m" to build a | |
820 | dynamically linked module called "g_midi". | |
821 | ||
25a010c8 CN |
822 | config USB_G_PRINTER |
823 | tristate "Printer Gadget" | |
824 | help | |
825 | The Printer Gadget channels data between the USB host and a | |
826 | userspace program driving the print engine. The user space | |
827 | program reads and writes the device file /dev/g_printer to | |
828 | receive or send printer data. It can use ioctl calls to | |
829 | the device file to get or set printer status. | |
830 | ||
831 | Say "y" to link the driver statically, or "m" to build a | |
832 | dynamically linked module called "g_printer". | |
833 | ||
834 | For more information, see Documentation/usb/gadget_printer.txt | |
835 | which includes sample code for accessing the device file. | |
1da177e4 | 836 | |
19e20680 DB |
837 | config USB_CDC_COMPOSITE |
838 | tristate "CDC Composite Device (Ethernet and ACM)" | |
4ddd9ec1 | 839 | depends on NET |
19e20680 DB |
840 | help |
841 | This driver provides two functions in one configuration: | |
842 | a CDC Ethernet (ECM) link, and a CDC ACM (serial port) link. | |
843 | ||
844 | This driver requires four bulk and two interrupt endpoints, | |
845 | plus the ability to handle altsettings. Not all peripheral | |
846 | controllers are that capable. | |
847 | ||
848 | Say "y" to link the driver statically, or "m" to build a | |
849 | dynamically linked module. | |
850 | ||
f358f5b4 FB |
851 | config USB_G_NOKIA |
852 | tristate "Nokia composite gadget" | |
853 | depends on PHONET | |
854 | help | |
855 | The Nokia composite gadget provides support for acm, obex | |
856 | and phonet in only one composite gadget driver. | |
857 | ||
858 | It's only really useful for N900 hardware. If you're building | |
859 | a kernel for N900, say Y or M here. If unsure, say N. | |
860 | ||
f176a5d8 MN |
861 | config USB_G_MULTI |
862 | tristate "Multifunction Composite Gadget (EXPERIMENTAL)" | |
5791e103 | 863 | depends on BLOCK && NET |
279cc49a | 864 | select USB_G_MULTI_CDC if !USB_G_MULTI_RNDIS |
f176a5d8 MN |
865 | help |
866 | The Multifunction Composite Gadget provides Ethernet (RNDIS | |
867 | and/or CDC Ethernet), mass storage and ACM serial link | |
868 | interfaces. | |
869 | ||
5791e103 | 870 | You will be asked to choose which of the two configurations is |
f176a5d8 | 871 | to be available in the gadget. At least one configuration must |
5791e103 | 872 | be chosen to make the gadget usable. Selecting more than one |
f176a5d8 | 873 | configuration will prevent Windows from automatically detecting |
5791e103 | 874 | the gadget as a composite gadget, so an INF file will be needed to |
f176a5d8 MN |
875 | use the gadget. |
876 | ||
877 | Say "y" to link the driver statically, or "m" to build a | |
878 | dynamically linked module called "g_multi". | |
879 | ||
880 | config USB_G_MULTI_RNDIS | |
881 | bool "RNDIS + CDC Serial + Storage configuration" | |
882 | depends on USB_G_MULTI | |
883 | default y | |
884 | help | |
885 | This option enables a configuration with RNDIS, CDC Serial and | |
886 | Mass Storage functions available in the Multifunction Composite | |
5791e103 RD |
887 | Gadget. This is the configuration dedicated for Windows since RNDIS |
888 | is Microsoft's protocol. | |
f176a5d8 MN |
889 | |
890 | If unsure, say "y". | |
891 | ||
892 | config USB_G_MULTI_CDC | |
893 | bool "CDC Ethernet + CDC Serial + Storage configuration" | |
894 | depends on USB_G_MULTI | |
895 | default n | |
896 | help | |
897 | This option enables a configuration with CDC Ethernet (ECM), CDC | |
898 | Serial and Mass Storage functions available in the Multifunction | |
5791e103 | 899 | Composite Gadget. |
f176a5d8 MN |
900 | |
901 | If unsure, say "y". | |
902 | ||
71adf118 FC |
903 | config USB_G_HID |
904 | tristate "HID Gadget" | |
905 | help | |
906 | The HID gadget driver provides generic emulation of USB | |
907 | Human Interface Devices (HID). | |
908 | ||
909 | For more information, see Documentation/usb/gadget_hid.txt which | |
910 | includes sample code for accessing the device files. | |
911 | ||
912 | Say "y" to link the driver statically, or "m" to build a | |
913 | dynamically linked module called "g_hid". | |
f176a5d8 | 914 | |
f6c826a9 | 915 | config USB_G_DBGP |
916 | tristate "EHCI Debug Device Gadget" | |
917 | help | |
918 | This gadget emulates an EHCI Debug device. This is useful when you want | |
919 | to interact with an EHCI Debug Port. | |
920 | ||
921 | Say "y" to link the driver statically, or "m" to build a | |
922 | dynamically linked module called "g_dbgp". | |
923 | ||
924 | if USB_G_DBGP | |
925 | choice | |
926 | prompt "EHCI Debug Device mode" | |
927 | default USB_G_DBGP_SERIAL | |
928 | ||
929 | config USB_G_DBGP_PRINTK | |
930 | depends on USB_G_DBGP | |
931 | bool "printk" | |
932 | help | |
933 | Directly printk() received data. No interaction. | |
934 | ||
935 | config USB_G_DBGP_SERIAL | |
936 | depends on USB_G_DBGP | |
937 | bool "serial" | |
938 | help | |
939 | Userland can interact using /dev/ttyGSxxx. | |
940 | endchoice | |
941 | endif | |
942 | ||
1da177e4 LT |
943 | # put drivers that need isochronous transfer support (for audio |
944 | # or video class gadget drivers), or specific hardware, here. | |
a9914127 LP |
945 | config USB_G_WEBCAM |
946 | tristate "USB Webcam Gadget" | |
24337c13 | 947 | depends on VIDEO_DEV |
a9914127 LP |
948 | help |
949 | The Webcam Gadget acts as a composite USB Audio and Video Class | |
950 | device. It provides a userspace API to process UVC control requests | |
951 | and stream video data to the host. | |
1da177e4 | 952 | |
a9914127 LP |
953 | Say "y" to link the driver statically, or "m" to build a |
954 | dynamically linked module called "g_webcam". | |
1da177e4 LT |
955 | |
956 | endchoice | |
957 | ||
b75be4ab | 958 | endif # USB_GADGET |