Root/
Source at commit 7ddcf13ec88da95c6098c45d5fa40c8e42b4338e created 14 years 2 months ago. By Lars-Peter Clausen, From ba0e3820ee1def7c358391df293551b726fb7014 Mon Sep 17 00:00:00 2001 Subject: [PATCH] /opt/Projects/openwrt/target/linux/xburst/patches-2.6.31/104-usb.patch | |
---|---|
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 | tristate "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 | 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 |
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 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 | |
44 | if USB_GADGET |
45 | |
46 | config USB_GADGET_DEBUG |
47 | boolean "Debugging messages (DEVELOPMENT)" |
48 | depends on DEBUG_KERNEL |
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 | |
60 | config USB_GADGET_DEBUG_FILES |
61 | boolean "Debugging information files (DEVELOPMENT)" |
62 | depends on PROC_FS |
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 | |
71 | config USB_GADGET_DEBUG_FS |
72 | boolean "Debugging information files in debugfs (DEVELOPMENT)" |
73 | depends on DEBUG_FS |
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 | |
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 | |
99 | config USB_GADGET_SELECTED |
100 | boolean |
101 | |
102 | # |
103 | # USB Peripheral Controller Support |
104 | # |
105 | # The order here is alphabetical, except that integrated controllers go |
106 | # before discrete ones so they will be the initial/default value: |
107 | # - integrated/SOC controllers first |
108 | # - licensed IP used in both SOC and discrete versions |
109 | # - discrete ones (including all PCI-only controllers) |
110 | # - debug/dummy gadget+hcd is last. |
111 | # |
112 | choice |
113 | prompt "USB Peripheral Controller" |
114 | depends on USB_GADGET |
115 | help |
116 | A USB device uses a controller to talk to its host. |
117 | Systems should have only one such upstream link. |
118 | Many controller drivers are platform-specific; these |
119 | often need board-specific hooks. |
120 | |
121 | # |
122 | # Integrated controllers |
123 | # |
124 | config USB_GADGET_JZ4740 |
125 | boolean "JZ4740 UDC" |
126 | depends on SOC_JZ4740 |
127 | select USB_GADGET_SELECTED |
128 | select USB_GADGET_DUALSPEED |
129 | help |
130 | Select this to support the Ingenic JZ4740 processor |
131 | high speed USB device controller. |
132 | |
133 | config USB_JZ4740 |
134 | tristate |
135 | depends on USB_GADGET_JZ4740 |
136 | default USB_GADGET |
137 | |
138 | config USB_GADGET_AT91 |
139 | boolean "Atmel AT91 USB Device Port" |
140 | depends on ARCH_AT91 && !ARCH_AT91SAM9RL && !ARCH_AT91CAP9 && !ARCH_AT91SAM9G45 |
141 | select USB_GADGET_SELECTED |
142 | |
143 | help |
144 | Many Atmel AT91 processors (such as the AT91RM2000) have a |
145 | full speed USB Device Port with support for five configurable |
146 | endpoints (plus endpoint zero). |
147 | |
148 | Say "y" to link the driver statically, or "m" to build a |
149 | dynamically linked module called "at91_udc" and force all |
150 | gadget drivers to also be dynamically linked. |
151 | |
152 | config USB_AT91 |
153 | tristate |
154 | depends on USB_GADGET_AT91 |
155 | default USB_GADGET |
156 | |
157 | config USB_GADGET_ATMEL_USBA |
158 | boolean "Atmel USBA" |
159 | select USB_GADGET_DUALSPEED |
160 | depends on AVR32 || ARCH_AT91CAP9 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45 |
161 | help |
162 | USBA is the integrated high-speed USB Device controller on |
163 | the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel. |
164 | |
165 | config USB_ATMEL_USBA |
166 | tristate |
167 | depends on USB_GADGET_ATMEL_USBA |
168 | default USB_GADGET |
169 | select USB_GADGET_SELECTED |
170 | |
171 | config USB_GADGET_FSL_USB2 |
172 | boolean "Freescale Highspeed USB DR Peripheral Controller" |
173 | depends on FSL_SOC || ARCH_MXC |
174 | select USB_GADGET_DUALSPEED |
175 | help |
176 | Some of Freescale PowerPC processors have a High Speed |
177 | Dual-Role(DR) USB controller, which supports device mode. |
178 | |
179 | The number of programmable endpoints is different through |
180 | SOC revisions. |
181 | |
182 | Say "y" to link the driver statically, or "m" to build a |
183 | dynamically linked module called "fsl_usb2_udc" and force |
184 | all gadget drivers to also be dynamically linked. |
185 | |
186 | config USB_FSL_USB2 |
187 | tristate |
188 | depends on USB_GADGET_FSL_USB2 |
189 | default USB_GADGET |
190 | select USB_GADGET_SELECTED |
191 | |
192 | config USB_GADGET_LH7A40X |
193 | boolean "LH7A40X" |
194 | depends on ARCH_LH7A40X |
195 | help |
196 | This driver provides USB Device Controller driver for LH7A40x |
197 | |
198 | config USB_LH7A40X |
199 | tristate |
200 | depends on USB_GADGET_LH7A40X |
201 | default USB_GADGET |
202 | select USB_GADGET_SELECTED |
203 | |
204 | config USB_GADGET_OMAP |
205 | boolean "OMAP USB Device Controller" |
206 | depends on ARCH_OMAP |
207 | select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_H4_OTG |
208 | select USB_OTG_UTILS if ARCH_OMAP |
209 | help |
210 | Many Texas Instruments OMAP processors have flexible full |
211 | speed USB device controllers, with support for up to 30 |
212 | endpoints (plus endpoint zero). This driver supports the |
213 | controller in the OMAP 1611, and should work with controllers |
214 | in other OMAP processors too, given minor tweaks. |
215 | |
216 | Say "y" to link the driver statically, or "m" to build a |
217 | dynamically linked module called "omap_udc" and force all |
218 | gadget drivers to also be dynamically linked. |
219 | |
220 | config USB_OMAP |
221 | tristate |
222 | depends on USB_GADGET_OMAP |
223 | default USB_GADGET |
224 | select USB_GADGET_SELECTED |
225 | |
226 | config USB_OTG |
227 | boolean "OTG Support" |
228 | depends on USB_GADGET_OMAP && ARCH_OMAP_OTG && USB_OHCI_HCD |
229 | help |
230 | The most notable feature of USB OTG is support for a |
231 | "Dual-Role" device, which can act as either a device |
232 | or a host. The initial role choice can be changed |
233 | later, when two dual-role devices talk to each other. |
234 | |
235 | Select this only if your OMAP board has a Mini-AB connector. |
236 | |
237 | config USB_GADGET_PXA25X |
238 | boolean "PXA 25x or IXP 4xx" |
239 | depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX |
240 | select USB_OTG_UTILS |
241 | help |
242 | Intel's PXA 25x series XScale ARM-5TE processors include |
243 | an integrated full speed USB 1.1 device controller. The |
244 | controller in the IXP 4xx series is register-compatible. |
245 | |
246 | It has fifteen fixed-function endpoints, as well as endpoint |
247 | zero (for control transfers). |
248 | |
249 | Say "y" to link the driver statically, or "m" to build a |
250 | dynamically linked module called "pxa25x_udc" and force all |
251 | gadget drivers to also be dynamically linked. |
252 | |
253 | config USB_PXA25X |
254 | tristate |
255 | depends on USB_GADGET_PXA25X |
256 | default USB_GADGET |
257 | select USB_GADGET_SELECTED |
258 | |
259 | # if there's only one gadget driver, using only two bulk endpoints, |
260 | # don't waste memory for the other endpoints |
261 | config USB_PXA25X_SMALL |
262 | depends on USB_GADGET_PXA25X |
263 | bool |
264 | default n if USB_ETH_RNDIS |
265 | default y if USB_ZERO |
266 | default y if USB_ETH |
267 | default y if USB_G_SERIAL |
268 | |
269 | config USB_GADGET_R8A66597 |
270 | boolean "Renesas R8A66597 USB Peripheral Controller" |
271 | select USB_GADGET_DUALSPEED |
272 | help |
273 | R8A66597 is a discrete USB host and peripheral controller chip that |
274 | supports both full and high speed USB 2.0 data transfers. |
275 | It has nine configurable endpoints, and endpoint zero. |
276 | |
277 | Say "y" to link the driver statically, or "m" to build a |
278 | dynamically linked module called "r8a66597_udc" and force all |
279 | gadget drivers to also be dynamically linked. |
280 | |
281 | config USB_R8A66597 |
282 | tristate |
283 | depends on USB_GADGET_R8A66597 |
284 | default USB_GADGET |
285 | select USB_GADGET_SELECTED |
286 | |
287 | config USB_GADGET_PXA27X |
288 | boolean "PXA 27x" |
289 | depends on ARCH_PXA && (PXA27x || PXA3xx) |
290 | select USB_OTG_UTILS |
291 | help |
292 | Intel's PXA 27x series XScale ARM v5TE processors include |
293 | an integrated full speed USB 1.1 device controller. |
294 | |
295 | It has up to 23 endpoints, as well as endpoint zero (for |
296 | control transfers). |
297 | |
298 | Say "y" to link the driver statically, or "m" to build a |
299 | dynamically linked module called "pxa27x_udc" and force all |
300 | gadget drivers to also be dynamically linked. |
301 | |
302 | config USB_PXA27X |
303 | tristate |
304 | depends on USB_GADGET_PXA27X |
305 | default USB_GADGET |
306 | select USB_GADGET_SELECTED |
307 | |
308 | config USB_GADGET_S3C_HSOTG |
309 | boolean "S3C HS/OtG USB Device controller" |
310 | depends on S3C_DEV_USB_HSOTG |
311 | select USB_GADGET_S3C_HSOTG_PIO |
312 | help |
313 | The Samsung S3C64XX USB2.0 high-speed gadget controller |
314 | integrated into the S3C64XX series SoC. |
315 | |
316 | config USB_S3C_HSOTG |
317 | tristate |
318 | depends on USB_GADGET_S3C_HSOTG |
319 | default USB_GADGET |
320 | select USB_GADGET_SELECTED |
321 | |
322 | config USB_GADGET_IMX |
323 | boolean "Freescale IMX USB Peripheral Controller" |
324 | depends on ARCH_MX1 |
325 | help |
326 | Freescale's IMX series include an integrated full speed |
327 | USB 1.1 device controller. The controller in the IMX series |
328 | is register-compatible. |
329 | |
330 | It has Six fixed-function endpoints, as well as endpoint |
331 | zero (for control transfers). |
332 | |
333 | Say "y" to link the driver statically, or "m" to build a |
334 | dynamically linked module called "imx_udc" and force all |
335 | gadget drivers to also be dynamically linked. |
336 | |
337 | config USB_IMX |
338 | tristate |
339 | depends on USB_GADGET_IMX |
340 | default USB_GADGET |
341 | select USB_GADGET_SELECTED |
342 | |
343 | config USB_GADGET_S3C2410 |
344 | boolean "S3C2410 USB Device Controller" |
345 | depends on ARCH_S3C2410 |
346 | help |
347 | Samsung's S3C2410 is an ARM-4 processor with an integrated |
348 | full speed USB 1.1 device controller. It has 4 configurable |
349 | endpoints, as well as endpoint zero (for control transfers). |
350 | |
351 | This driver has been tested on the S3C2410, S3C2412, and |
352 | S3C2440 processors. |
353 | |
354 | config USB_S3C2410 |
355 | tristate |
356 | depends on USB_GADGET_S3C2410 |
357 | default USB_GADGET |
358 | select USB_GADGET_SELECTED |
359 | |
360 | config USB_S3C2410_DEBUG |
361 | boolean "S3C2410 udc debug messages" |
362 | depends on USB_GADGET_S3C2410 |
363 | |
364 | # |
365 | # Controllers available in both integrated and discrete versions |
366 | # |
367 | |
368 | # musb builds in ../musb along with host support |
369 | config USB_GADGET_MUSB_HDRC |
370 | boolean "Inventra HDRC USB Peripheral (TI, ADI, ...)" |
371 | depends on USB_MUSB_HDRC && (USB_MUSB_PERIPHERAL || USB_MUSB_OTG) |
372 | select USB_GADGET_DUALSPEED |
373 | select USB_GADGET_SELECTED |
374 | help |
375 | This OTG-capable silicon IP is used in dual designs including |
376 | the TI DaVinci, OMAP 243x, OMAP 343x, TUSB 6010, and ADI Blackfin |
377 | |
378 | config USB_GADGET_M66592 |
379 | boolean "Renesas M66592 USB Peripheral Controller" |
380 | select USB_GADGET_DUALSPEED |
381 | help |
382 | M66592 is a discrete USB peripheral controller chip that |
383 | supports both full and high speed USB 2.0 data transfers. |
384 | It has seven configurable endpoints, and endpoint zero. |
385 | |
386 | Say "y" to link the driver statically, or "m" to build a |
387 | dynamically linked module called "m66592_udc" and force all |
388 | gadget drivers to also be dynamically linked. |
389 | |
390 | config USB_M66592 |
391 | tristate |
392 | depends on USB_GADGET_M66592 |
393 | default USB_GADGET |
394 | select USB_GADGET_SELECTED |
395 | |
396 | # |
397 | # Controllers available only in discrete form (and all PCI controllers) |
398 | # |
399 | |
400 | config USB_GADGET_AMD5536UDC |
401 | boolean "AMD5536 UDC" |
402 | depends on PCI |
403 | select USB_GADGET_DUALSPEED |
404 | help |
405 | The AMD5536 UDC is part of the AMD Geode CS5536, an x86 southbridge. |
406 | It is a USB Highspeed DMA capable USB device controller. Beside ep0 |
407 | it provides 4 IN and 4 OUT endpoints (bulk or interrupt type). |
408 | The UDC port supports OTG operation, and may be used as a host port |
409 | if it's not being used to implement peripheral or OTG roles. |
410 | |
411 | Say "y" to link the driver statically, or "m" to build a |
412 | dynamically linked module called "amd5536udc" and force all |
413 | gadget drivers to also be dynamically linked. |
414 | |
415 | config USB_AMD5536UDC |
416 | tristate |
417 | depends on USB_GADGET_AMD5536UDC |
418 | default USB_GADGET |
419 | select USB_GADGET_SELECTED |
420 | |
421 | config USB_GADGET_FSL_QE |
422 | boolean "Freescale QE/CPM USB Device Controller" |
423 | depends on FSL_SOC && (QUICC_ENGINE || CPM) |
424 | help |
425 | Some of Freescale PowerPC processors have a Full Speed |
426 | QE/CPM2 USB controller, which support device mode with 4 |
427 | programmable endpoints. This driver supports the |
428 | controller in the MPC8360 and MPC8272, and should work with |
429 | controllers having QE or CPM2, given minor tweaks. |
430 | |
431 | Set CONFIG_USB_GADGET to "m" to build this driver as a |
432 | dynamically linked module called "fsl_qe_udc". |
433 | |
434 | config USB_FSL_QE |
435 | tristate |
436 | depends on USB_GADGET_FSL_QE |
437 | default USB_GADGET |
438 | select USB_GADGET_SELECTED |
439 | |
440 | config USB_GADGET_CI13XXX |
441 | boolean "MIPS USB CI13xxx" |
442 | depends on PCI |
443 | select USB_GADGET_DUALSPEED |
444 | help |
445 | MIPS USB IP core family device controller |
446 | Currently it only supports IP part number CI13412 |
447 | |
448 | Say "y" to link the driver statically, or "m" to build a |
449 | dynamically linked module called "ci13xxx_udc" and force all |
450 | gadget drivers to also be dynamically linked. |
451 | |
452 | config USB_CI13XXX |
453 | tristate |
454 | depends on USB_GADGET_CI13XXX |
455 | default USB_GADGET |
456 | select USB_GADGET_SELECTED |
457 | |
458 | config USB_GADGET_NET2280 |
459 | boolean "NetChip 228x" |
460 | depends on PCI |
461 | select USB_GADGET_DUALSPEED |
462 | help |
463 | NetChip 2280 / 2282 is a PCI based USB peripheral controller which |
464 | supports both full and high speed USB 2.0 data transfers. |
465 | |
466 | It has six configurable endpoints, as well as endpoint zero |
467 | (for control transfers) and several endpoints with dedicated |
468 | functions. |
469 | |
470 | Say "y" to link the driver statically, or "m" to build a |
471 | dynamically linked module called "net2280" and force all |
472 | gadget drivers to also be dynamically linked. |
473 | |
474 | config USB_NET2280 |
475 | tristate |
476 | depends on USB_GADGET_NET2280 |
477 | default USB_GADGET |
478 | select USB_GADGET_SELECTED |
479 | |
480 | config USB_GADGET_GOKU |
481 | boolean "Toshiba TC86C001 'Goku-S'" |
482 | depends on PCI |
483 | help |
484 | The Toshiba TC86C001 is a PCI device which includes controllers |
485 | for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI). |
486 | |
487 | The device controller has three configurable (bulk or interrupt) |
488 | endpoints, plus endpoint zero (for control transfers). |
489 | |
490 | Say "y" to link the driver statically, or "m" to build a |
491 | dynamically linked module called "goku_udc" and to force all |
492 | gadget drivers to also be dynamically linked. |
493 | |
494 | config USB_GOKU |
495 | tristate |
496 | depends on USB_GADGET_GOKU |
497 | default USB_GADGET |
498 | select USB_GADGET_SELECTED |
499 | |
500 | config USB_GADGET_LANGWELL |
501 | boolean "Intel Langwell USB Device Controller" |
502 | depends on PCI |
503 | select USB_GADGET_DUALSPEED |
504 | help |
505 | Intel Langwell USB Device Controller is a High-Speed USB |
506 | On-The-Go device controller. |
507 | |
508 | The number of programmable endpoints is different through |
509 | controller revision. |
510 | |
511 | Say "y" to link the driver statically, or "m" to build a |
512 | dynamically linked module called "langwell_udc" and force all |
513 | gadget drivers to also be dynamically linked. |
514 | |
515 | config USB_LANGWELL |
516 | tristate |
517 | depends on USB_GADGET_LANGWELL |
518 | default USB_GADGET |
519 | select USB_GADGET_SELECTED |
520 | |
521 | |
522 | # |
523 | # LAST -- dummy/emulated controller |
524 | # |
525 | |
526 | config USB_GADGET_DUMMY_HCD |
527 | boolean "Dummy HCD (DEVELOPMENT)" |
528 | depends on USB=y || (USB=m && USB_GADGET=m) |
529 | select USB_GADGET_DUALSPEED |
530 | help |
531 | This host controller driver emulates USB, looping all data transfer |
532 | requests back to a USB "gadget driver" in the same host. The host |
533 | side is the master; the gadget side is the slave. Gadget drivers |
534 | can be high, full, or low speed; and they have access to endpoints |
535 | like those from NET2280, PXA2xx, or SA1100 hardware. |
536 | |
537 | This may help in some stages of creating a driver to embed in a |
538 | Linux device, since it lets you debug several parts of the gadget |
539 | driver without its hardware or drivers being involved. |
540 | |
541 | Since such a gadget side driver needs to interoperate with a host |
542 | side Linux-USB device driver, this may help to debug both sides |
543 | of a USB protocol stack. |
544 | |
545 | Say "y" to link the driver statically, or "m" to build a |
546 | dynamically linked module called "dummy_hcd" and force all |
547 | gadget drivers to also be dynamically linked. |
548 | |
549 | config USB_DUMMY_HCD |
550 | tristate |
551 | depends on USB_GADGET_DUMMY_HCD |
552 | default USB_GADGET |
553 | select USB_GADGET_SELECTED |
554 | |
555 | # NOTE: Please keep dummy_hcd LAST so that "real hardware" appears |
556 | # first and will be selected by default. |
557 | |
558 | endchoice |
559 | |
560 | config USB_GADGET_DUALSPEED |
561 | bool |
562 | depends on USB_GADGET |
563 | default n |
564 | help |
565 | Means that gadget drivers should include extra descriptors |
566 | and code to handle dual-speed controllers. |
567 | |
568 | # |
569 | # USB Gadget Drivers |
570 | # |
571 | choice |
572 | tristate "USB Gadget Drivers" |
573 | depends on USB_GADGET && USB_GADGET_SELECTED |
574 | default USB_ETH |
575 | help |
576 | A Linux "Gadget Driver" talks to the USB Peripheral Controller |
577 | driver through the abstract "gadget" API. Some other operating |
578 | systems call these "client" drivers, of which "class drivers" |
579 | are a subset (implementing a USB device class specification). |
580 | A gadget driver implements one or more USB functions using |
581 | the peripheral hardware. |
582 | |
583 | Gadget drivers are hardware-neutral, or "platform independent", |
584 | except that they sometimes must understand quirks or limitations |
585 | of the particular controllers they work with. For example, when |
586 | a controller doesn't support alternate configurations or provide |
587 | enough of the right types of endpoints, the gadget driver might |
588 | not be able work with that controller, or might need to implement |
589 | a less common variant of a device class protocol. |
590 | |
591 | # this first set of drivers all depend on bulk-capable hardware. |
592 | |
593 | config USB_ZERO |
594 | tristate "Gadget Zero (DEVELOPMENT)" |
595 | help |
596 | Gadget Zero is a two-configuration device. It either sinks and |
597 | sources bulk data; or it loops back a configurable number of |
598 | transfers. It also implements control requests, for "chapter 9" |
599 | conformance. The driver needs only two bulk-capable endpoints, so |
600 | it can work on top of most device-side usb controllers. It's |
601 | useful for testing, and is also a working example showing how |
602 | USB "gadget drivers" can be written. |
603 | |
604 | Make this be the first driver you try using on top of any new |
605 | USB peripheral controller driver. Then you can use host-side |
606 | test software, like the "usbtest" driver, to put your hardware |
607 | and its driver through a basic set of functional tests. |
608 | |
609 | Gadget Zero also works with the host-side "usb-skeleton" driver, |
610 | and with many kinds of host-side test software. You may need |
611 | to tweak product and vendor IDs before host software knows about |
612 | this device, and arrange to select an appropriate configuration. |
613 | |
614 | Say "y" to link the driver statically, or "m" to build a |
615 | dynamically linked module called "g_zero". |
616 | |
617 | config USB_ZERO_HNPTEST |
618 | boolean "HNP Test Device" |
619 | depends on USB_ZERO && USB_OTG |
620 | help |
621 | You can configure this device to enumerate using the device |
622 | identifiers of the USB-OTG test device. That means that when |
623 | this gadget connects to another OTG device, with this one using |
624 | the "B-Peripheral" role, that device will use HNP to let this |
625 | one serve as the USB host instead (in the "B-Host" role). |
626 | |
627 | config USB_AUDIO |
628 | tristate "Audio Gadget (EXPERIMENTAL)" |
629 | depends on SND |
630 | select SND_PCM |
631 | help |
632 | Gadget Audio is compatible with USB Audio Class specification 1.0. |
633 | It will include at least one AudioControl interface, zero or more |
634 | AudioStream interface and zero or more MIDIStream interface. |
635 | |
636 | Gadget Audio will use on-board ALSA (CONFIG_SND) audio card to |
637 | playback or capture audio stream. |
638 | |
639 | Say "y" to link the driver statically, or "m" to build a |
640 | dynamically linked module called "g_audio". |
641 | |
642 | config USB_ETH |
643 | tristate "Ethernet Gadget (with CDC Ethernet support)" |
644 | depends on NET |
645 | select CRC32 |
646 | help |
647 | This driver implements Ethernet style communication, in one of |
648 | several ways: |
649 | |
650 | - The "Communication Device Class" (CDC) Ethernet Control Model. |
651 | That protocol is often avoided with pure Ethernet adapters, in |
652 | favor of simpler vendor-specific hardware, but is widely |
653 | supported by firmware for smart network devices. |
654 | |
655 | - On hardware can't implement that protocol, a simple CDC subset |
656 | is used, placing fewer demands on USB. |
657 | |
658 | - CDC Ethernet Emulation Model (EEM) is a newer standard that has |
659 | a simpler interface that can be used by more USB hardware. |
660 | |
661 | RNDIS support is an additional option, more demanding than than |
662 | subset. |
663 | |
664 | Within the USB device, this gadget driver exposes a network device |
665 | "usbX", where X depends on what other networking devices you have. |
666 | Treat it like a two-node Ethernet link: host, and gadget. |
667 | |
668 | The Linux-USB host-side "usbnet" driver interoperates with this |
669 | driver, so that deep I/O queues can be supported. On 2.4 kernels, |
670 | use "CDCEther" instead, if you're using the CDC option. That CDC |
671 | mode should also interoperate with standard CDC Ethernet class |
672 | drivers on other host operating systems. |
673 | |
674 | Say "y" to link the driver statically, or "m" to build a |
675 | dynamically linked module called "g_ether". |
676 | |
677 | config USB_ETH_RNDIS |
678 | bool "RNDIS support" |
679 | depends on USB_ETH |
680 | default y |
681 | help |
682 | Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol, |
683 | and Microsoft provides redistributable binary RNDIS drivers for |
684 | older versions of Windows. |
685 | |
686 | If you say "y" here, the Ethernet gadget driver will try to provide |
687 | a second device configuration, supporting RNDIS to talk to such |
688 | Microsoft USB hosts. |
689 | |
690 | To make MS-Windows work with this, use Documentation/usb/linux.inf |
691 | as the "driver info file". For versions of MS-Windows older than |
692 | XP, you'll need to download drivers from Microsoft's website; a URL |
693 | is given in comments found in that info file. |
694 | |
695 | config USB_ETH_EEM |
696 | bool "Ethernet Emulation Model (EEM) support" |
697 | depends on USB_ETH |
698 | default n |
699 | help |
700 | CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM |
701 | and therefore can be supported by more hardware. Technically ECM and |
702 | EEM are designed for different applications. The ECM model extends |
703 | the network interface to the target (e.g. a USB cable modem), and the |
704 | EEM model is for mobile devices to communicate with hosts using |
705 | ethernet over USB. For Linux gadgets, however, the interface with |
706 | the host is the same (a usbX device), so the differences are minimal. |
707 | |
708 | If you say "y" here, the Ethernet gadget driver will use the EEM |
709 | protocol rather than ECM. If unsure, say "n". |
710 | |
711 | config USB_GADGETFS |
712 | tristate "Gadget Filesystem (EXPERIMENTAL)" |
713 | depends on EXPERIMENTAL |
714 | help |
715 | This driver provides a filesystem based API that lets user mode |
716 | programs implement a single-configuration USB device, including |
717 | endpoint I/O and control requests that don't relate to enumeration. |
718 | All endpoints, transfer speeds, and transfer types supported by |
719 | the hardware are available, through read() and write() calls. |
720 | |
721 | Currently, this option is still labelled as EXPERIMENTAL because |
722 | of existing race conditions in the underlying in-kernel AIO core. |
723 | |
724 | Say "y" to link the driver statically, or "m" to build a |
725 | dynamically linked module called "gadgetfs". |
726 | |
727 | config USB_FILE_STORAGE |
728 | tristate "File-backed Storage Gadget" |
729 | depends on BLOCK |
730 | help |
731 | The File-backed Storage Gadget acts as a USB Mass Storage |
732 | disk drive. As its storage repository it can use a regular |
733 | file or a block device (in much the same way as the "loop" |
734 | device driver), specified as a module parameter. |
735 | |
736 | Say "y" to link the driver statically, or "m" to build a |
737 | dynamically linked module called "g_file_storage". |
738 | |
739 | config USB_FILE_STORAGE_TEST |
740 | bool "File-backed Storage Gadget testing version" |
741 | depends on USB_FILE_STORAGE |
742 | default n |
743 | help |
744 | Say "y" to generate the larger testing version of the |
745 | File-backed Storage Gadget, useful for probing the |
746 | behavior of USB Mass Storage hosts. Not needed for |
747 | normal operation. |
748 | |
749 | config USB_G_SERIAL |
750 | tristate "Serial Gadget (with CDC ACM and CDC OBEX support)" |
751 | help |
752 | The Serial Gadget talks to the Linux-USB generic serial driver. |
753 | This driver supports a CDC-ACM module option, which can be used |
754 | to interoperate with MS-Windows hosts or with the Linux-USB |
755 | "cdc-acm" driver. |
756 | |
757 | This driver also supports a CDC-OBEX option. You will need a |
758 | user space OBEX server talking to /dev/ttyGS*, since the kernel |
759 | itself doesn't implement the OBEX protocol. |
760 | |
761 | Say "y" to link the driver statically, or "m" to build a |
762 | dynamically linked module called "g_serial". |
763 | |
764 | For more information, see Documentation/usb/gadget_serial.txt |
765 | which includes instructions and a "driver info file" needed to |
766 | make MS-Windows work with CDC ACM. |
767 | |
768 | config USB_MIDI_GADGET |
769 | tristate "MIDI Gadget (EXPERIMENTAL)" |
770 | depends on SND && EXPERIMENTAL |
771 | select SND_RAWMIDI |
772 | help |
773 | The MIDI Gadget acts as a USB Audio device, with one MIDI |
774 | input and one MIDI output. These MIDI jacks appear as |
775 | a sound "card" in the ALSA sound system. Other MIDI |
776 | connections can then be made on the gadget system, using |
777 | ALSA's aconnect utility etc. |
778 | |
779 | Say "y" to link the driver statically, or "m" to build a |
780 | dynamically linked module called "g_midi". |
781 | |
782 | config USB_G_PRINTER |
783 | tristate "Printer Gadget" |
784 | help |
785 | The Printer Gadget channels data between the USB host and a |
786 | userspace program driving the print engine. The user space |
787 | program reads and writes the device file /dev/g_printer to |
788 | receive or send printer data. It can use ioctl calls to |
789 | the device file to get or set printer status. |
790 | |
791 | Say "y" to link the driver statically, or "m" to build a |
792 | dynamically linked module called "g_printer". |
793 | |
794 | For more information, see Documentation/usb/gadget_printer.txt |
795 | which includes sample code for accessing the device file. |
796 | |
797 | config USB_CDC_COMPOSITE |
798 | tristate "CDC Composite Device (Ethernet and ACM)" |
799 | depends on NET |
800 | help |
801 | This driver provides two functions in one configuration: |
802 | a CDC Ethernet (ECM) link, and a CDC ACM (serial port) link. |
803 | |
804 | This driver requires four bulk and two interrupt endpoints, |
805 | plus the ability to handle altsettings. Not all peripheral |
806 | controllers are that capable. |
807 | |
808 | Say "y" to link the driver statically, or "m" to build a |
809 | dynamically linked module. |
810 | |
811 | # put drivers that need isochronous transfer support (for audio |
812 | # or video class gadget drivers), or specific hardware, here. |
813 | |
814 | # - none yet |
815 | |
816 | endchoice |
817 | |
818 | endif # USB_GADGET |
819 |
Branches:
ben-wpan
ben-wpan-stefan
javiroman/ks7010
jz-2.6.34
jz-2.6.34-rc5
jz-2.6.34-rc6
jz-2.6.34-rc7
jz-2.6.35
jz-2.6.36
jz-2.6.37
jz-2.6.38
jz-2.6.39
jz-3.0
jz-3.1
jz-3.11
jz-3.12
jz-3.13
jz-3.15
jz-3.16
jz-3.18-dt
jz-3.2
jz-3.3
jz-3.4
jz-3.5
jz-3.6
jz-3.6-rc2-pwm
jz-3.9
jz-3.9-clk
jz-3.9-rc8
jz47xx
jz47xx-2.6.38
master
Tags:
od-2011-09-04
od-2011-09-18
v2.6.34-rc5
v2.6.34-rc6
v2.6.34-rc7
v3.9