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