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