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