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 | |
a9df304c TA |
359 | config USB_GADGET_S3C_HSUDC |
360 | boolean "S3C2416, S3C2443 and S3C2450 USB Device Controller" | |
361 | depends on ARCH_S3C2410 | |
362 | select USB_GADGET_DUALSPEED | |
363 | help | |
364 | Samsung's S3C2416, S3C2443 and S3C2450 is an ARM9 based SoC | |
365 | integrated with dual speed USB 2.0 device controller. It has | |
366 | 8 endpoints, as well as endpoint zero. | |
367 | ||
368 | This driver has been tested on S3C2416 and S3C2450 processors. | |
369 | ||
370 | config USB_S3C_HSUDC | |
371 | tristate | |
372 | depends on USB_GADGET_S3C_HSUDC | |
373 | default USB_GADGET | |
374 | select USB_GADGET_SELECTED | |
375 | ||
e7cddda4 | 376 | config USB_GADGET_PXA_U2O |
377 | boolean "PXA9xx Processor USB2.0 controller" | |
378 | select USB_GADGET_DUALSPEED | |
379 | help | |
380 | PXA9xx Processor series include a high speed USB2.0 device | |
381 | controller, which support high speed and full speed USB peripheral. | |
382 | ||
383 | config USB_PXA_U2O | |
384 | tristate | |
385 | depends on USB_GADGET_PXA_U2O | |
386 | default USB_GADGET | |
387 | select USB_GADGET_SELECTED | |
388 | ||
a7a19fac DB |
389 | # |
390 | # Controllers available in both integrated and discrete versions | |
391 | # | |
1da177e4 | 392 | |
a7a19fac | 393 | # musb builds in ../musb along with host support |
550a7375 | 394 | config USB_GADGET_MUSB_HDRC |
085ad406 | 395 | boolean "Inventra HDRC USB Peripheral (TI, ADI, ...)" |
550a7375 FB |
396 | depends on USB_MUSB_HDRC && (USB_MUSB_PERIPHERAL || USB_MUSB_OTG) |
397 | select USB_GADGET_DUALSPEED | |
398 | select USB_GADGET_SELECTED | |
399 | help | |
400 | This OTG-capable silicon IP is used in dual designs including | |
085ad406 | 401 | the TI DaVinci, OMAP 243x, OMAP 343x, TUSB 6010, and ADI Blackfin |
550a7375 | 402 | |
a7a19fac DB |
403 | config USB_GADGET_M66592 |
404 | boolean "Renesas M66592 USB Peripheral Controller" | |
405 | select USB_GADGET_DUALSPEED | |
1da177e4 | 406 | help |
a7a19fac DB |
407 | M66592 is a discrete USB peripheral controller chip that |
408 | supports both full and high speed USB 2.0 data transfers. | |
409 | It has seven configurable endpoints, and endpoint zero. | |
1da177e4 LT |
410 | |
411 | Say "y" to link the driver statically, or "m" to build a | |
a7a19fac | 412 | dynamically linked module called "m66592_udc" and force all |
1da177e4 LT |
413 | gadget drivers to also be dynamically linked. |
414 | ||
a7a19fac | 415 | config USB_M66592 |
1da177e4 | 416 | tristate |
a7a19fac | 417 | depends on USB_GADGET_M66592 |
1da177e4 | 418 | default USB_GADGET |
028b271b | 419 | select USB_GADGET_SELECTED |
1da177e4 | 420 | |
a7a19fac DB |
421 | # |
422 | # Controllers available only in discrete form (and all PCI controllers) | |
423 | # | |
424 | ||
425 | config USB_GADGET_AMD5536UDC | |
426 | boolean "AMD5536 UDC" | |
427 | depends on PCI | |
428 | select USB_GADGET_DUALSPEED | |
3fc154b6 | 429 | help |
a7a19fac DB |
430 | The AMD5536 UDC is part of the AMD Geode CS5536, an x86 southbridge. |
431 | It is a USB Highspeed DMA capable USB device controller. Beside ep0 | |
432 | it provides 4 IN and 4 OUT endpoints (bulk or interrupt type). | |
433 | The UDC port supports OTG operation, and may be used as a host port | |
434 | if it's not being used to implement peripheral or OTG roles. | |
3fc154b6 | 435 | |
a7a19fac DB |
436 | Say "y" to link the driver statically, or "m" to build a |
437 | dynamically linked module called "amd5536udc" and force all | |
438 | gadget drivers to also be dynamically linked. | |
3fc154b6 | 439 | |
a7a19fac | 440 | config USB_AMD5536UDC |
3fc154b6 | 441 | tristate |
a7a19fac | 442 | depends on USB_GADGET_AMD5536UDC |
3fc154b6 AP |
443 | default USB_GADGET |
444 | select USB_GADGET_SELECTED | |
445 | ||
3948f0e0 LY |
446 | config USB_GADGET_FSL_QE |
447 | boolean "Freescale QE/CPM USB Device Controller" | |
448 | depends on FSL_SOC && (QUICC_ENGINE || CPM) | |
449 | help | |
450 | Some of Freescale PowerPC processors have a Full Speed | |
451 | QE/CPM2 USB controller, which support device mode with 4 | |
452 | programmable endpoints. This driver supports the | |
453 | controller in the MPC8360 and MPC8272, and should work with | |
454 | controllers having QE or CPM2, given minor tweaks. | |
455 | ||
456 | Set CONFIG_USB_GADGET to "m" to build this driver as a | |
692105b8 | 457 | dynamically linked module called "fsl_qe_udc". |
3948f0e0 LY |
458 | |
459 | config USB_FSL_QE | |
460 | tristate | |
461 | depends on USB_GADGET_FSL_QE | |
462 | default USB_GADGET | |
463 | select USB_GADGET_SELECTED | |
464 | ||
409a15da PK |
465 | config USB_GADGET_CI13XXX_PCI |
466 | boolean "MIPS USB CI13xxx PCI UDC" | |
aa69a809 DL |
467 | depends on PCI |
468 | select USB_GADGET_DUALSPEED | |
469 | help | |
470 | MIPS USB IP core family device controller | |
471 | Currently it only supports IP part number CI13412 | |
472 | ||
473 | Say "y" to link the driver statically, or "m" to build a | |
474 | dynamically linked module called "ci13xxx_udc" and force all | |
475 | gadget drivers to also be dynamically linked. | |
476 | ||
409a15da | 477 | config USB_CI13XXX_PCI |
aa69a809 | 478 | tristate |
409a15da | 479 | depends on USB_GADGET_CI13XXX_PCI |
aa69a809 DL |
480 | default USB_GADGET |
481 | select USB_GADGET_SELECTED | |
482 | ||
ceb80363 SL |
483 | config USB_GADGET_NET2272 |
484 | boolean "PLX NET2272" | |
485 | select USB_GADGET_DUALSPEED | |
486 | help | |
487 | PLX NET2272 is a USB peripheral controller which supports | |
488 | both full and high speed USB 2.0 data transfers. | |
489 | ||
490 | It has three configurable endpoints, as well as endpoint zero | |
491 | (for control transfer). | |
492 | Say "y" to link the driver statically, or "m" to build a | |
493 | dynamically linked module called "net2272" and force all | |
494 | gadget drivers to also be dynamically linked. | |
495 | ||
496 | config USB_GADGET_NET2272_DMA | |
497 | boolean "Support external DMA controller" | |
498 | depends on USB_GADGET_NET2272 | |
499 | help | |
500 | The NET2272 part can optionally support an external DMA | |
501 | controller, but your board has to have support in the | |
502 | driver itself. | |
503 | ||
504 | If unsure, say "N" here. The driver works fine in PIO mode. | |
505 | ||
506 | config USB_NET2272 | |
507 | tristate | |
508 | depends on USB_GADGET_NET2272 | |
509 | default USB_GADGET | |
510 | select USB_GADGET_SELECTED | |
511 | ||
a7a19fac DB |
512 | config USB_GADGET_NET2280 |
513 | boolean "NetChip 228x" | |
514 | depends on PCI | |
515 | select USB_GADGET_DUALSPEED | |
516 | help | |
517 | NetChip 2280 / 2282 is a PCI based USB peripheral controller which | |
518 | supports both full and high speed USB 2.0 data transfers. | |
3fc154b6 | 519 | |
a7a19fac DB |
520 | It has six configurable endpoints, as well as endpoint zero |
521 | (for control transfers) and several endpoints with dedicated | |
522 | functions. | |
523 | ||
524 | Say "y" to link the driver statically, or "m" to build a | |
525 | dynamically linked module called "net2280" and force all | |
526 | gadget drivers to also be dynamically linked. | |
527 | ||
528 | config USB_NET2280 | |
529 | tristate | |
530 | depends on USB_GADGET_NET2280 | |
531 | default USB_GADGET | |
bae4bd84 | 532 | select USB_GADGET_SELECTED |
a7a19fac DB |
533 | |
534 | config USB_GADGET_GOKU | |
535 | boolean "Toshiba TC86C001 'Goku-S'" | |
536 | depends on PCI | |
bae4bd84 | 537 | help |
a7a19fac DB |
538 | The Toshiba TC86C001 is a PCI device which includes controllers |
539 | for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI). | |
540 | ||
541 | The device controller has three configurable (bulk or interrupt) | |
542 | endpoints, plus endpoint zero (for control transfers). | |
bae4bd84 DB |
543 | |
544 | Say "y" to link the driver statically, or "m" to build a | |
a7a19fac | 545 | dynamically linked module called "goku_udc" and to force all |
bae4bd84 DB |
546 | gadget drivers to also be dynamically linked. |
547 | ||
a7a19fac | 548 | config USB_GOKU |
bae4bd84 | 549 | tristate |
a7a19fac | 550 | depends on USB_GADGET_GOKU |
bae4bd84 | 551 | default USB_GADGET |
a7a19fac DB |
552 | select USB_GADGET_SELECTED |
553 | ||
5be19a9d XS |
554 | config USB_GADGET_LANGWELL |
555 | boolean "Intel Langwell USB Device Controller" | |
556 | depends on PCI | |
557 | select USB_GADGET_DUALSPEED | |
558 | help | |
559 | Intel Langwell USB Device Controller is a High-Speed USB | |
560 | On-The-Go device controller. | |
561 | ||
562 | The number of programmable endpoints is different through | |
563 | controller revision. | |
564 | ||
565 | Say "y" to link the driver statically, or "m" to build a | |
566 | dynamically linked module called "langwell_udc" and force all | |
567 | gadget drivers to also be dynamically linked. | |
568 | ||
569 | config USB_LANGWELL | |
570 | tristate | |
571 | depends on USB_GADGET_LANGWELL | |
572 | default USB_GADGET | |
573 | select USB_GADGET_SELECTED | |
574 | ||
f646cf94 | 575 | config USB_GADGET_EG20T |
06f1b971 | 576 | boolean "Intel EG20T PCH/OKI SEMICONDUCTOR ML7213 IOH UDC" |
f646cf94 TO |
577 | depends on PCI |
578 | select USB_GADGET_DUALSPEED | |
579 | help | |
580 | This is a USB device driver for EG20T PCH. | |
581 | EG20T PCH is the platform controller hub that is used in Intel's | |
582 | general embedded platform. EG20T PCH has USB device interface. | |
583 | Using this interface, it is able to access system devices connected | |
584 | to USB device. | |
585 | This driver enables USB device function. | |
586 | USB device is a USB peripheral controller which | |
587 | supports both full and high speed USB 2.0 data transfers. | |
588 | This driver supports both control transfer and bulk transfer modes. | |
589 | This driver dose not support interrupt transfer or isochronous | |
590 | transfer modes. | |
591 | ||
06f1b971 TM |
592 | This driver also can be used for OKI SEMICONDUCTOR's ML7213 which is |
593 | for IVI(In-Vehicle Infotainment) use. | |
594 | ML7213 is companion chip for Intel Atom E6xx series. | |
595 | ML7213 is completely compatible for Intel EG20T PCH. | |
596 | ||
f646cf94 TO |
597 | config USB_EG20T |
598 | tristate | |
599 | depends on USB_GADGET_EG20T | |
600 | default USB_GADGET | |
601 | select USB_GADGET_SELECTED | |
a7a19fac | 602 | |
33f82f38 PK |
603 | config USB_GADGET_CI13XXX_MSM |
604 | boolean "MIPS USB CI13xxx for MSM" | |
605 | depends on ARCH_MSM | |
606 | select USB_GADGET_DUALSPEED | |
dfb2130c | 607 | select USB_MSM_OTG |
33f82f38 PK |
608 | help |
609 | MSM SoC has chipidea USB controller. This driver uses | |
610 | ci13xxx_udc core. | |
611 | This driver depends on OTG driver for PHY initialization, | |
612 | clock management, powering up VBUS, and power management. | |
8cf28f1f PK |
613 | This driver is not supported on boards like trout which |
614 | has an external PHY. | |
33f82f38 PK |
615 | |
616 | Say "y" to link the driver statically, or "m" to build a | |
617 | dynamically linked module called "ci13xxx_msm" and force all | |
618 | gadget drivers to also be dynamically linked. | |
619 | ||
620 | config USB_CI13XXX_MSM | |
621 | tristate | |
622 | depends on USB_GADGET_CI13XXX_MSM | |
623 | default USB_GADGET | |
624 | select USB_GADGET_SELECTED | |
a7a19fac DB |
625 | |
626 | # | |
627 | # LAST -- dummy/emulated controller | |
628 | # | |
1da177e4 LT |
629 | |
630 | config USB_GADGET_DUMMY_HCD | |
631 | boolean "Dummy HCD (DEVELOPMENT)" | |
afd0e0f2 | 632 | depends on USB=y || (USB=m && USB_GADGET=m) |
1da177e4 | 633 | select USB_GADGET_DUALSPEED |
1cd8fd28 | 634 | select USB_GADGET_SUPERSPEED |
1da177e4 LT |
635 | help |
636 | This host controller driver emulates USB, looping all data transfer | |
637 | requests back to a USB "gadget driver" in the same host. The host | |
638 | side is the master; the gadget side is the slave. Gadget drivers | |
639 | can be high, full, or low speed; and they have access to endpoints | |
640 | like those from NET2280, PXA2xx, or SA1100 hardware. | |
641 | ||
642 | This may help in some stages of creating a driver to embed in a | |
643 | Linux device, since it lets you debug several parts of the gadget | |
644 | driver without its hardware or drivers being involved. | |
645 | ||
646 | Since such a gadget side driver needs to interoperate with a host | |
647 | side Linux-USB device driver, this may help to debug both sides | |
648 | of a USB protocol stack. | |
649 | ||
650 | Say "y" to link the driver statically, or "m" to build a | |
651 | dynamically linked module called "dummy_hcd" and force all | |
652 | gadget drivers to also be dynamically linked. | |
653 | ||
654 | config USB_DUMMY_HCD | |
655 | tristate | |
656 | depends on USB_GADGET_DUMMY_HCD | |
657 | default USB_GADGET | |
028b271b | 658 | select USB_GADGET_SELECTED |
1da177e4 LT |
659 | |
660 | # NOTE: Please keep dummy_hcd LAST so that "real hardware" appears | |
661 | # first and will be selected by default. | |
662 | ||
663 | endchoice | |
664 | ||
97b2f900 | 665 | # Selected by UDC drivers that support high-speed operation. |
1da177e4 LT |
666 | config USB_GADGET_DUALSPEED |
667 | bool | |
668 | depends on USB_GADGET | |
1da177e4 | 669 | |
bdb64d72 TB |
670 | # Selected by UDC drivers that support super-speed opperation |
671 | config USB_GADGET_SUPERSPEED | |
672 | bool | |
673 | depends on USB_GADGET | |
674 | depends on USB_GADGET_DUALSPEED | |
675 | ||
1da177e4 LT |
676 | # |
677 | # USB Gadget Drivers | |
678 | # | |
679 | choice | |
680 | tristate "USB Gadget Drivers" | |
028b271b | 681 | depends on USB_GADGET && USB_GADGET_SELECTED |
1da177e4 LT |
682 | default USB_ETH |
683 | help | |
684 | A Linux "Gadget Driver" talks to the USB Peripheral Controller | |
685 | driver through the abstract "gadget" API. Some other operating | |
686 | systems call these "client" drivers, of which "class drivers" | |
687 | are a subset (implementing a USB device class specification). | |
688 | A gadget driver implements one or more USB functions using | |
689 | the peripheral hardware. | |
690 | ||
691 | Gadget drivers are hardware-neutral, or "platform independent", | |
692 | except that they sometimes must understand quirks or limitations | |
693 | of the particular controllers they work with. For example, when | |
694 | a controller doesn't support alternate configurations or provide | |
695 | enough of the right types of endpoints, the gadget driver might | |
696 | not be able work with that controller, or might need to implement | |
697 | a less common variant of a device class protocol. | |
698 | ||
699 | # this first set of drivers all depend on bulk-capable hardware. | |
700 | ||
701 | config USB_ZERO | |
702 | tristate "Gadget Zero (DEVELOPMENT)" | |
1da177e4 LT |
703 | help |
704 | Gadget Zero is a two-configuration device. It either sinks and | |
705 | sources bulk data; or it loops back a configurable number of | |
706 | transfers. It also implements control requests, for "chapter 9" | |
707 | conformance. The driver needs only two bulk-capable endpoints, so | |
708 | it can work on top of most device-side usb controllers. It's | |
709 | useful for testing, and is also a working example showing how | |
710 | USB "gadget drivers" can be written. | |
711 | ||
712 | Make this be the first driver you try using on top of any new | |
713 | USB peripheral controller driver. Then you can use host-side | |
714 | test software, like the "usbtest" driver, to put your hardware | |
715 | and its driver through a basic set of functional tests. | |
716 | ||
717 | Gadget Zero also works with the host-side "usb-skeleton" driver, | |
718 | and with many kinds of host-side test software. You may need | |
719 | to tweak product and vendor IDs before host software knows about | |
720 | this device, and arrange to select an appropriate configuration. | |
721 | ||
722 | Say "y" to link the driver statically, or "m" to build a | |
723 | dynamically linked module called "g_zero". | |
724 | ||
725 | config USB_ZERO_HNPTEST | |
726 | boolean "HNP Test Device" | |
727 | depends on USB_ZERO && USB_OTG | |
728 | help | |
729 | You can configure this device to enumerate using the device | |
730 | identifiers of the USB-OTG test device. That means that when | |
731 | this gadget connects to another OTG device, with this one using | |
732 | the "B-Peripheral" role, that device will use HNP to let this | |
733 | one serve as the USB host instead (in the "B-Host" role). | |
734 | ||
c6994e6f BW |
735 | config USB_AUDIO |
736 | tristate "Audio Gadget (EXPERIMENTAL)" | |
737 | depends on SND | |
04950737 | 738 | select SND_PCM |
c6994e6f BW |
739 | help |
740 | Gadget Audio is compatible with USB Audio Class specification 1.0. | |
741 | It will include at least one AudioControl interface, zero or more | |
742 | AudioStream interface and zero or more MIDIStream interface. | |
743 | ||
744 | Gadget Audio will use on-board ALSA (CONFIG_SND) audio card to | |
745 | playback or capture audio stream. | |
746 | ||
747 | Say "y" to link the driver statically, or "m" to build a | |
748 | dynamically linked module called "g_audio". | |
749 | ||
1da177e4 LT |
750 | config USB_ETH |
751 | tristate "Ethernet Gadget (with CDC Ethernet support)" | |
752 | depends on NET | |
9e221be8 | 753 | select CRC32 |
1da177e4 | 754 | help |
9b39e9dd BN |
755 | This driver implements Ethernet style communication, in one of |
756 | several ways: | |
1da177e4 LT |
757 | |
758 | - The "Communication Device Class" (CDC) Ethernet Control Model. | |
759 | That protocol is often avoided with pure Ethernet adapters, in | |
760 | favor of simpler vendor-specific hardware, but is widely | |
761 | supported by firmware for smart network devices. | |
762 | ||
763 | - On hardware can't implement that protocol, a simple CDC subset | |
764 | is used, placing fewer demands on USB. | |
765 | ||
9b39e9dd BN |
766 | - CDC Ethernet Emulation Model (EEM) is a newer standard that has |
767 | a simpler interface that can be used by more USB hardware. | |
768 | ||
769 | RNDIS support is an additional option, more demanding than than | |
770 | subset. | |
1da177e4 LT |
771 | |
772 | Within the USB device, this gadget driver exposes a network device | |
773 | "usbX", where X depends on what other networking devices you have. | |
774 | Treat it like a two-node Ethernet link: host, and gadget. | |
775 | ||
776 | The Linux-USB host-side "usbnet" driver interoperates with this | |
777 | driver, so that deep I/O queues can be supported. On 2.4 kernels, | |
778 | use "CDCEther" instead, if you're using the CDC option. That CDC | |
779 | mode should also interoperate with standard CDC Ethernet class | |
780 | drivers on other host operating systems. | |
781 | ||
782 | Say "y" to link the driver statically, or "m" to build a | |
783 | dynamically linked module called "g_ether". | |
784 | ||
785 | config USB_ETH_RNDIS | |
afd0e0f2 RD |
786 | bool "RNDIS support" |
787 | depends on USB_ETH | |
1da177e4 LT |
788 | default y |
789 | help | |
790 | Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol, | |
791 | and Microsoft provides redistributable binary RNDIS drivers for | |
792 | older versions of Windows. | |
793 | ||
794 | If you say "y" here, the Ethernet gadget driver will try to provide | |
795 | a second device configuration, supporting RNDIS to talk to such | |
796 | Microsoft USB hosts. | |
797 | ||
798 | To make MS-Windows work with this, use Documentation/usb/linux.inf | |
799 | as the "driver info file". For versions of MS-Windows older than | |
800 | XP, you'll need to download drivers from Microsoft's website; a URL | |
801 | is given in comments found in that info file. | |
802 | ||
9b39e9dd BN |
803 | config USB_ETH_EEM |
804 | bool "Ethernet Emulation Model (EEM) support" | |
805 | depends on USB_ETH | |
806 | default n | |
807 | help | |
808 | CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM | |
809 | and therefore can be supported by more hardware. Technically ECM and | |
810 | EEM are designed for different applications. The ECM model extends | |
811 | the network interface to the target (e.g. a USB cable modem), and the | |
812 | EEM model is for mobile devices to communicate with hosts using | |
813 | ethernet over USB. For Linux gadgets, however, the interface with | |
814 | the host is the same (a usbX device), so the differences are minimal. | |
815 | ||
816 | If you say "y" here, the Ethernet gadget driver will use the EEM | |
817 | protocol rather than ECM. If unsure, say "n". | |
818 | ||
6c34d288 YK |
819 | config USB_G_NCM |
820 | tristate "Network Control Model (NCM) support" | |
821 | depends on NET | |
822 | select CRC32 | |
823 | help | |
824 | This driver implements USB CDC NCM subclass standard. NCM is | |
825 | an advanced protocol for Ethernet encapsulation, allows grouping | |
826 | of several ethernet frames into one USB transfer and diffferent | |
827 | alignment possibilities. | |
828 | ||
829 | Say "y" to link the driver statically, or "m" to build a | |
830 | dynamically linked module called "g_ncm". | |
831 | ||
1da177e4 LT |
832 | config USB_GADGETFS |
833 | tristate "Gadget Filesystem (EXPERIMENTAL)" | |
834 | depends on EXPERIMENTAL | |
835 | help | |
836 | This driver provides a filesystem based API that lets user mode | |
837 | programs implement a single-configuration USB device, including | |
838 | endpoint I/O and control requests that don't relate to enumeration. | |
839 | All endpoints, transfer speeds, and transfer types supported by | |
840 | the hardware are available, through read() and write() calls. | |
841 | ||
afd0e0f2 RD |
842 | Currently, this option is still labelled as EXPERIMENTAL because |
843 | of existing race conditions in the underlying in-kernel AIO core. | |
844 | ||
1da177e4 LT |
845 | Say "y" to link the driver statically, or "m" to build a |
846 | dynamically linked module called "gadgetfs". | |
847 | ||
c6c56008 MN |
848 | config USB_FUNCTIONFS |
849 | tristate "Function Filesystem (EXPERIMENTAL)" | |
850 | depends on EXPERIMENTAL | |
f8dae531 | 851 | select USB_FUNCTIONFS_GENERIC if !(USB_FUNCTIONFS_ETH || USB_FUNCTIONFS_RNDIS) |
c6c56008 | 852 | help |
eabf0f5f MP |
853 | The Function Filesystem (FunctionFS) lets one create USB |
854 | composite functions in user space in the same way GadgetFS | |
c6c56008 MN |
855 | lets one create USB gadgets in user space. This allows creation |
856 | of composite gadgets such that some of the functions are | |
857 | implemented in kernel space (for instance Ethernet, serial or | |
858 | mass storage) and other are implemented in user space. | |
859 | ||
f8dae531 MN |
860 | If you say "y" or "m" here you will be able what kind of |
861 | configurations the gadget will provide. | |
862 | ||
c6c56008 MN |
863 | Say "y" to link the driver statically, or "m" to build |
864 | a dynamically linked module called "g_ffs". | |
865 | ||
866 | config USB_FUNCTIONFS_ETH | |
f8dae531 | 867 | bool "Include configuration with CDC ECM (Ethernet)" |
17b2765e | 868 | depends on USB_FUNCTIONFS && NET |
c6c56008 | 869 | help |
eabf0f5f MP |
870 | Include a configuration with CDC ECM function (Ethernet) and the |
871 | Function Filesystem. | |
c6c56008 MN |
872 | |
873 | config USB_FUNCTIONFS_RNDIS | |
f8dae531 | 874 | bool "Include configuration with RNDIS (Ethernet)" |
17b2765e | 875 | depends on USB_FUNCTIONFS && NET |
c6c56008 | 876 | help |
eabf0f5f | 877 | Include a configuration with RNDIS function (Ethernet) and the Filesystem. |
c6c56008 MN |
878 | |
879 | config USB_FUNCTIONFS_GENERIC | |
880 | bool "Include 'pure' configuration" | |
f8dae531 | 881 | depends on USB_FUNCTIONFS |
c6c56008 | 882 | help |
f8dae531 MN |
883 | Include a configuration with the Function Filesystem alone with |
884 | no Ethernet interface. | |
c6c56008 | 885 | |
1da177e4 | 886 | config USB_FILE_STORAGE |
664a51a8 | 887 | tristate "File-backed Storage Gadget (DEPRECATED)" |
87840289 | 888 | depends on BLOCK |
1da177e4 LT |
889 | help |
890 | The File-backed Storage Gadget acts as a USB Mass Storage | |
891 | disk drive. As its storage repository it can use a regular | |
892 | file or a block device (in much the same way as the "loop" | |
893 | device driver), specified as a module parameter. | |
894 | ||
895 | Say "y" to link the driver statically, or "m" to build a | |
896 | dynamically linked module called "g_file_storage". | |
897 | ||
664a51a8 AS |
898 | NOTE: This driver is deprecated. Its replacement is the |
899 | Mass Storage Gadget. | |
900 | ||
1da177e4 LT |
901 | config USB_FILE_STORAGE_TEST |
902 | bool "File-backed Storage Gadget testing version" | |
903 | depends on USB_FILE_STORAGE | |
904 | default n | |
905 | help | |
906 | Say "y" to generate the larger testing version of the | |
907 | File-backed Storage Gadget, useful for probing the | |
908 | behavior of USB Mass Storage hosts. Not needed for | |
909 | normal operation. | |
910 | ||
d23b0f08 MN |
911 | config USB_MASS_STORAGE |
912 | tristate "Mass Storage Gadget" | |
913 | depends on BLOCK | |
914 | help | |
915 | The Mass Storage Gadget acts as a USB Mass Storage disk drive. | |
916 | As its storage repository it can use a regular file or a block | |
917 | device (in much the same way as the "loop" device driver), | |
918 | specified as a module parameter or sysfs option. | |
919 | ||
664a51a8 AS |
920 | This driver is an updated replacement for the deprecated |
921 | File-backed Storage Gadget (g_file_storage). | |
d23b0f08 MN |
922 | |
923 | Say "y" to link the driver statically, or "m" to build | |
664a51a8 | 924 | a dynamically linked module called "g_mass_storage". |
d23b0f08 | 925 | |
1da177e4 | 926 | config USB_G_SERIAL |
3086775a | 927 | tristate "Serial Gadget (with CDC ACM and CDC OBEX support)" |
1da177e4 LT |
928 | help |
929 | The Serial Gadget talks to the Linux-USB generic serial driver. | |
930 | This driver supports a CDC-ACM module option, which can be used | |
931 | to interoperate with MS-Windows hosts or with the Linux-USB | |
932 | "cdc-acm" driver. | |
933 | ||
3086775a FB |
934 | This driver also supports a CDC-OBEX option. You will need a |
935 | user space OBEX server talking to /dev/ttyGS*, since the kernel | |
936 | itself doesn't implement the OBEX protocol. | |
937 | ||
1da177e4 LT |
938 | Say "y" to link the driver statically, or "m" to build a |
939 | dynamically linked module called "g_serial". | |
940 | ||
941 | For more information, see Documentation/usb/gadget_serial.txt | |
942 | which includes instructions and a "driver info file" needed to | |
3086775a | 943 | make MS-Windows work with CDC ACM. |
1da177e4 | 944 | |
f2ebf92c BW |
945 | config USB_MIDI_GADGET |
946 | tristate "MIDI Gadget (EXPERIMENTAL)" | |
947 | depends on SND && EXPERIMENTAL | |
948 | select SND_RAWMIDI | |
949 | help | |
950 | The MIDI Gadget acts as a USB Audio device, with one MIDI | |
951 | input and one MIDI output. These MIDI jacks appear as | |
952 | a sound "card" in the ALSA sound system. Other MIDI | |
953 | connections can then be made on the gadget system, using | |
954 | ALSA's aconnect utility etc. | |
955 | ||
956 | Say "y" to link the driver statically, or "m" to build a | |
957 | dynamically linked module called "g_midi". | |
958 | ||
25a010c8 CN |
959 | config USB_G_PRINTER |
960 | tristate "Printer Gadget" | |
961 | help | |
962 | The Printer Gadget channels data between the USB host and a | |
963 | userspace program driving the print engine. The user space | |
964 | program reads and writes the device file /dev/g_printer to | |
965 | receive or send printer data. It can use ioctl calls to | |
966 | the device file to get or set printer status. | |
967 | ||
968 | Say "y" to link the driver statically, or "m" to build a | |
969 | dynamically linked module called "g_printer". | |
970 | ||
971 | For more information, see Documentation/usb/gadget_printer.txt | |
972 | which includes sample code for accessing the device file. | |
1da177e4 | 973 | |
19e20680 DB |
974 | config USB_CDC_COMPOSITE |
975 | tristate "CDC Composite Device (Ethernet and ACM)" | |
4ddd9ec1 | 976 | depends on NET |
19e20680 DB |
977 | help |
978 | This driver provides two functions in one configuration: | |
979 | a CDC Ethernet (ECM) link, and a CDC ACM (serial port) link. | |
980 | ||
981 | This driver requires four bulk and two interrupt endpoints, | |
982 | plus the ability to handle altsettings. Not all peripheral | |
983 | controllers are that capable. | |
984 | ||
985 | Say "y" to link the driver statically, or "m" to build a | |
986 | dynamically linked module. | |
987 | ||
f358f5b4 FB |
988 | config USB_G_NOKIA |
989 | tristate "Nokia composite gadget" | |
990 | depends on PHONET | |
991 | help | |
992 | The Nokia composite gadget provides support for acm, obex | |
993 | and phonet in only one composite gadget driver. | |
994 | ||
995 | It's only really useful for N900 hardware. If you're building | |
996 | a kernel for N900, say Y or M here. If unsure, say N. | |
997 | ||
f176a5d8 MN |
998 | config USB_G_MULTI |
999 | tristate "Multifunction Composite Gadget (EXPERIMENTAL)" | |
5791e103 | 1000 | depends on BLOCK && NET |
279cc49a | 1001 | select USB_G_MULTI_CDC if !USB_G_MULTI_RNDIS |
f176a5d8 MN |
1002 | help |
1003 | The Multifunction Composite Gadget provides Ethernet (RNDIS | |
1004 | and/or CDC Ethernet), mass storage and ACM serial link | |
1005 | interfaces. | |
1006 | ||
5791e103 | 1007 | You will be asked to choose which of the two configurations is |
f176a5d8 | 1008 | to be available in the gadget. At least one configuration must |
5791e103 | 1009 | be chosen to make the gadget usable. Selecting more than one |
f176a5d8 | 1010 | configuration will prevent Windows from automatically detecting |
5791e103 | 1011 | the gadget as a composite gadget, so an INF file will be needed to |
f176a5d8 MN |
1012 | use the gadget. |
1013 | ||
1014 | Say "y" to link the driver statically, or "m" to build a | |
1015 | dynamically linked module called "g_multi". | |
1016 | ||
1017 | config USB_G_MULTI_RNDIS | |
1018 | bool "RNDIS + CDC Serial + Storage configuration" | |
1019 | depends on USB_G_MULTI | |
1020 | default y | |
1021 | help | |
1022 | This option enables a configuration with RNDIS, CDC Serial and | |
1023 | Mass Storage functions available in the Multifunction Composite | |
5791e103 RD |
1024 | Gadget. This is the configuration dedicated for Windows since RNDIS |
1025 | is Microsoft's protocol. | |
f176a5d8 MN |
1026 | |
1027 | If unsure, say "y". | |
1028 | ||
1029 | config USB_G_MULTI_CDC | |
1030 | bool "CDC Ethernet + CDC Serial + Storage configuration" | |
1031 | depends on USB_G_MULTI | |
1032 | default n | |
1033 | help | |
1034 | This option enables a configuration with CDC Ethernet (ECM), CDC | |
1035 | Serial and Mass Storage functions available in the Multifunction | |
5791e103 | 1036 | Composite Gadget. |
f176a5d8 MN |
1037 | |
1038 | If unsure, say "y". | |
1039 | ||
71adf118 FC |
1040 | config USB_G_HID |
1041 | tristate "HID Gadget" | |
1042 | help | |
1043 | The HID gadget driver provides generic emulation of USB | |
1044 | Human Interface Devices (HID). | |
1045 | ||
1046 | For more information, see Documentation/usb/gadget_hid.txt which | |
1047 | includes sample code for accessing the device files. | |
1048 | ||
1049 | Say "y" to link the driver statically, or "m" to build a | |
1050 | dynamically linked module called "g_hid". | |
f176a5d8 | 1051 | |
f6c826a9 | 1052 | config USB_G_DBGP |
1053 | tristate "EHCI Debug Device Gadget" | |
1054 | help | |
1055 | This gadget emulates an EHCI Debug device. This is useful when you want | |
1056 | to interact with an EHCI Debug Port. | |
1057 | ||
1058 | Say "y" to link the driver statically, or "m" to build a | |
1059 | dynamically linked module called "g_dbgp". | |
1060 | ||
1061 | if USB_G_DBGP | |
1062 | choice | |
1063 | prompt "EHCI Debug Device mode" | |
1064 | default USB_G_DBGP_SERIAL | |
1065 | ||
1066 | config USB_G_DBGP_PRINTK | |
1067 | depends on USB_G_DBGP | |
1068 | bool "printk" | |
1069 | help | |
1070 | Directly printk() received data. No interaction. | |
1071 | ||
1072 | config USB_G_DBGP_SERIAL | |
1073 | depends on USB_G_DBGP | |
1074 | bool "serial" | |
1075 | help | |
1076 | Userland can interact using /dev/ttyGSxxx. | |
1077 | endchoice | |
1078 | endif | |
1079 | ||
1da177e4 LT |
1080 | # put drivers that need isochronous transfer support (for audio |
1081 | # or video class gadget drivers), or specific hardware, here. | |
a9914127 LP |
1082 | config USB_G_WEBCAM |
1083 | tristate "USB Webcam Gadget" | |
24337c13 | 1084 | depends on VIDEO_DEV |
a9914127 LP |
1085 | help |
1086 | The Webcam Gadget acts as a composite USB Audio and Video Class | |
1087 | device. It provides a userspace API to process UVC control requests | |
1088 | and stream video data to the host. | |
1da177e4 | 1089 | |
a9914127 LP |
1090 | Say "y" to link the driver statically, or "m" to build a |
1091 | dynamically linked module called "g_webcam". | |
1da177e4 LT |
1092 | |
1093 | endchoice | |
1094 | ||
b75be4ab | 1095 | endif # USB_GADGET |