2 # USB Gadget support on a system involves
3 # (a) a peripheral controller, and
4 # (b) the gadget driver using it.
6 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
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.
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).
17 tristate "USB Gadget Support"
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.
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
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.)
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).
42 For more information, see <http://www.linux-usb.org/gadget> and
43 the kernel DocBook documentation for this API.
47 config USB_GADGET_DEBUG
48 boolean "Debugging messages (DEVELOPMENT)"
49 depends on DEBUG_KERNEL
51 Many controller and gadget drivers will print some debugging
52 messages if you use this option to ask for those messages.
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
61 config USB_GADGET_DEBUG_FILES
62 boolean "Debugging information files (DEVELOPMENT)"
65 Some of the drivers in the "gadget" framework can expose
66 debugging information in files such as /proc/driver/udc
67 (for a peripheral controller). The information in these
68 files may help when you're troubleshooting or bringing up a
69 driver on a new board. Enable these files by choosing "Y"
70 here. If in doubt, or to conserve kernel memory, say "N".
72 config USB_GADGET_DEBUG_FS
73 boolean "Debugging information files in debugfs (DEVELOPMENT)"
76 Some of the drivers in the "gadget" framework can expose
77 debugging information in files under /sys/kernel/debug/.
78 The information in these files may help when you're
79 troubleshooting or bringing up a driver on a new board.
80 Enable these files by choosing "Y" here. If in doubt, or
81 to conserve kernel memory, say "N".
83 config USB_GADGET_VBUS_DRAW
84 int "Maximum VBUS Power usage (2-500 mA)"
88 Some devices need to draw power from USB when they are
89 configured, perhaps to operate circuitry or to recharge
90 batteries. This is in addition to any local power supply,
91 such as an AC adapter or batteries.
93 Enter the maximum power your device draws through USB, in
94 milliAmperes. The permitted range of values is 2 - 500 mA;
95 0 mA would be legal, but can make some hosts misbehave.
97 This value will be used except for system-specific gadget
98 drivers that have more specific information.
100 config USB_GADGET_STORAGE_NUM_BUFFERS
101 int "Number of storage pipeline buffers"
105 Usually 2 buffers are enough to establish a good buffering
106 pipeline. The number may be increased in order to compensate
107 for a bursty VFS behaviour. For instance there may be CPU wake up
108 latencies that makes the VFS to appear bursty in a system with
109 an CPU on-demand governor. Especially if DMA is doing IO to
110 offload the CPU. In this case the CPU will go into power
111 save often and spin up occasionally to move data within VFS.
112 If selecting USB_GADGET_DEBUG_FILES this value may be set by
113 a module parameter as well.
117 # USB Peripheral Controller Support
119 # The order here is alphabetical, except that integrated controllers go
120 # before discrete ones so they will be the initial/default value:
121 # - integrated/SOC controllers first
122 # - licensed IP used in both SOC and discrete versions
123 # - discrete ones (including all PCI-only controllers)
124 # - debug/dummy gadget+hcd is last.
126 menu "USB Peripheral Controller"
129 # Integrated controllers
133 tristate "Atmel AT91 USB Device Port"
136 Many Atmel AT91 processors (such as the AT91RM2000) have a
137 full speed USB Device Port with support for five configurable
138 endpoints (plus endpoint zero).
140 Say "y" to link the driver statically, or "m" to build a
141 dynamically linked module called "at91_udc" and force all
142 gadget drivers to also be dynamically linked.
145 tristate "LPC32XX USB Peripheral Controller"
146 depends on ARCH_LPC32XX
151 This option selects the USB device controller in the LPC32xx SoC.
153 Say "y" to link the driver statically, or "m" to build a
154 dynamically linked module called "lpc32xx_udc" and force all
155 gadget drivers to also be dynamically linked.
157 config USB_ATMEL_USBA
158 tristate "Atmel USBA"
159 depends on AVR32 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
161 USBA is the integrated high-speed USB Device controller on
162 the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel.
164 config USB_BCM63XX_UDC
165 tristate "Broadcom BCM63xx Peripheral Controller"
168 Many Broadcom BCM63xx chipsets (such as the BCM6328) have a
169 high speed USB Device Port with support for four fixed endpoints
170 (plus endpoint zero).
172 Say "y" to link the driver statically, or "m" to build a
173 dynamically linked module called "bcm63xx_udc".
176 tristate "Freescale Highspeed USB DR Peripheral Controller"
177 depends on FSL_SOC || ARCH_MXC
178 select USB_FSL_MPH_DR_OF if OF
180 Some of Freescale PowerPC and i.MX processors have a High Speed
181 Dual-Role(DR) USB controller, which supports device mode.
183 The number of programmable endpoints is different through
186 Say "y" to link the driver statically, or "m" to build a
187 dynamically linked module called "fsl_usb2_udc" and force
188 all gadget drivers to also be dynamically linked.
191 tristate "Faraday FUSB300 USB Peripheral Controller"
192 depends on !PHYS_ADDR_T_64BIT
194 Faraday usb device controller FUSB300 driver
197 tristate "OMAP USB Device Controller"
198 depends on ARCH_OMAP1
199 select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_H4_OTG
201 Many Texas Instruments OMAP processors have flexible full
202 speed USB device controllers, with support for up to 30
203 endpoints (plus endpoint zero). This driver supports the
204 controller in the OMAP 1611, and should work with controllers
205 in other OMAP processors too, given minor tweaks.
207 Say "y" to link the driver statically, or "m" to build a
208 dynamically linked module called "omap_udc" and force all
209 gadget drivers to also be dynamically linked.
212 tristate "PXA 25x or IXP 4xx"
213 depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX
215 Intel's PXA 25x series XScale ARM-5TE processors include
216 an integrated full speed USB 1.1 device controller. The
217 controller in the IXP 4xx series is register-compatible.
219 It has fifteen fixed-function endpoints, as well as endpoint
220 zero (for control transfers).
222 Say "y" to link the driver statically, or "m" to build a
223 dynamically linked module called "pxa25x_udc" and force all
224 gadget drivers to also be dynamically linked.
226 # if there's only one gadget driver, using only two bulk endpoints,
227 # don't waste memory for the other endpoints
228 config USB_PXA25X_SMALL
229 depends on USB_PXA25X
231 default n if USB_ETH_RNDIS
232 default y if USB_ZERO
234 default y if USB_G_SERIAL
237 tristate "Renesas R8A66597 USB Peripheral Controller"
239 R8A66597 is a discrete USB host and peripheral controller chip that
240 supports both full and high speed USB 2.0 data transfers.
241 It has nine configurable endpoints, and endpoint zero.
243 Say "y" to link the driver statically, or "m" to build a
244 dynamically linked module called "r8a66597_udc" and force all
245 gadget drivers to also be dynamically linked.
247 config USB_RENESAS_USBHS_UDC
248 tristate 'Renesas USBHS controller'
249 depends on USB_RENESAS_USBHS
251 Renesas USBHS is a discrete USB host and peripheral controller chip
252 that supports both full and high speed USB 2.0 data transfers.
253 It has nine or more configurable endpoints, and endpoint zero.
255 Say "y" to link the driver statically, or "m" to build a
256 dynamically linked module called "renesas_usbhs" and force all
257 gadget drivers to also be dynamically linked.
262 Intel's PXA 27x series XScale ARM v5TE processors include
263 an integrated full speed USB 1.1 device controller.
265 It has up to 23 endpoints, as well as endpoint zero (for
268 Say "y" to link the driver statically, or "m" to build a
269 dynamically linked module called "pxa27x_udc" and force all
270 gadget drivers to also be dynamically linked.
273 tristate "S3C HS/OtG USB Device controller"
274 depends on S3C_DEV_USB_HSOTG
276 The Samsung S3C64XX USB2.0 high-speed gadget controller
277 integrated into the S3C64XX series SoC.
280 tristate "Freescale i.MX1 USB Peripheral Controller"
284 Freescale's i.MX1 includes an integrated full speed
285 USB 1.1 device controller.
287 It has Six fixed-function endpoints, as well as endpoint
288 zero (for control transfers).
290 Say "y" to link the driver statically, or "m" to build a
291 dynamically linked module called "imx_udc" and force all
292 gadget drivers to also be dynamically linked.
295 tristate "S3C2410 USB Device Controller"
296 depends on ARCH_S3C24XX
298 Samsung's S3C2410 is an ARM-4 processor with an integrated
299 full speed USB 1.1 device controller. It has 4 configurable
300 endpoints, as well as endpoint zero (for control transfers).
302 This driver has been tested on the S3C2410, S3C2412, and
305 config USB_S3C2410_DEBUG
306 boolean "S3C2410 udc debug messages"
307 depends on USB_S3C2410
310 tristate "S3C2416, S3C2443 and S3C2450 USB Device Controller"
311 depends on ARCH_S3C24XX
313 Samsung's S3C2416, S3C2443 and S3C2450 is an ARM9 based SoC
314 integrated with dual speed USB 2.0 device controller. It has
315 8 endpoints, as well as endpoint zero.
317 This driver has been tested on S3C2416 and S3C2450 processors.
320 tristate "Marvell USB2.0 Device Controller"
321 depends on GENERIC_HARDIRQS
323 Marvell Socs (including PXA and MMP series) include a high speed
324 USB2.0 OTG controller, which can be configured as high speed or
325 full speed USB peripheral.
328 tristate "MARVELL PXA2128 USB 3.0 controller"
330 MARVELL PXA2128 Processor series include a super speed USB3.0 device
331 controller, which support super speed USB peripheral.
334 # Controllers available in both integrated and discrete versions
337 # musb builds in ../musb along with host support
338 config USB_GADGET_MUSB_HDRC
339 tristate "Inventra HDRC USB Peripheral (TI, ADI, ...)"
340 depends on USB_MUSB_HDRC
342 This OTG-capable silicon IP is used in dual designs including
343 the TI DaVinci, OMAP 243x, OMAP 343x, TUSB 6010, and ADI Blackfin
346 tristate "Renesas M66592 USB Peripheral Controller"
348 M66592 is a discrete USB peripheral controller chip that
349 supports both full and high speed USB 2.0 data transfers.
350 It has seven configurable endpoints, and endpoint zero.
352 Say "y" to link the driver statically, or "m" to build a
353 dynamically linked module called "m66592_udc" and force all
354 gadget drivers to also be dynamically linked.
357 # Controllers available only in discrete form (and all PCI controllers)
360 config USB_AMD5536UDC
361 tristate "AMD5536 UDC"
364 The AMD5536 UDC is part of the AMD Geode CS5536, an x86 southbridge.
365 It is a USB Highspeed DMA capable USB device controller. Beside ep0
366 it provides 4 IN and 4 OUT endpoints (bulk or interrupt type).
367 The UDC port supports OTG operation, and may be used as a host port
368 if it's not being used to implement peripheral or OTG roles.
370 Say "y" to link the driver statically, or "m" to build a
371 dynamically linked module called "amd5536udc" and force all
372 gadget drivers to also be dynamically linked.
375 tristate "Freescale QE/CPM USB Device Controller"
376 depends on FSL_SOC && (QUICC_ENGINE || CPM)
378 Some of Freescale PowerPC processors have a Full Speed
379 QE/CPM2 USB controller, which support device mode with 4
380 programmable endpoints. This driver supports the
381 controller in the MPC8360 and MPC8272, and should work with
382 controllers having QE or CPM2, given minor tweaks.
384 Set CONFIG_USB_GADGET to "m" to build this driver as a
385 dynamically linked module called "fsl_qe_udc".
388 tristate "PLX NET2272"
390 PLX NET2272 is a USB peripheral controller which supports
391 both full and high speed USB 2.0 data transfers.
393 It has three configurable endpoints, as well as endpoint zero
394 (for control transfer).
395 Say "y" to link the driver statically, or "m" to build a
396 dynamically linked module called "net2272" and force all
397 gadget drivers to also be dynamically linked.
399 config USB_NET2272_DMA
400 boolean "Support external DMA controller"
401 depends on USB_NET2272
403 The NET2272 part can optionally support an external DMA
404 controller, but your board has to have support in the
407 If unsure, say "N" here. The driver works fine in PIO mode.
410 tristate "NetChip 228x"
413 NetChip 2280 / 2282 is a PCI based USB peripheral controller which
414 supports both full and high speed USB 2.0 data transfers.
416 It has six configurable endpoints, as well as endpoint zero
417 (for control transfers) and several endpoints with dedicated
420 Say "y" to link the driver statically, or "m" to build a
421 dynamically linked module called "net2280" and force all
422 gadget drivers to also be dynamically linked.
425 tristate "Toshiba TC86C001 'Goku-S'"
428 The Toshiba TC86C001 is a PCI device which includes controllers
429 for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI).
431 The device controller has three configurable (bulk or interrupt)
432 endpoints, plus endpoint zero (for control transfers).
434 Say "y" to link the driver statically, or "m" to build a
435 dynamically linked module called "goku_udc" and to force all
436 gadget drivers to also be dynamically linked.
439 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7213/ML7831) UDC"
440 depends on PCI && GENERIC_HARDIRQS
442 This is a USB device driver for EG20T PCH.
443 EG20T PCH is the platform controller hub that is used in Intel's
444 general embedded platform. EG20T PCH has USB device interface.
445 Using this interface, it is able to access system devices connected
447 This driver enables USB device function.
448 USB device is a USB peripheral controller which
449 supports both full and high speed USB 2.0 data transfers.
450 This driver supports both control transfer and bulk transfer modes.
451 This driver dose not support interrupt transfer or isochronous
454 This driver also can be used for LAPIS Semiconductor's ML7213 which is
455 for IVI(In-Vehicle Infotainment) use.
456 ML7831 is for general purpose use.
457 ML7213/ML7831 is companion chip for Intel Atom E6xx series.
458 ML7213/ML7831 is completely compatible for Intel EG20T PCH.
461 # LAST -- dummy/emulated controller
465 tristate "Dummy HCD (DEVELOPMENT)"
466 depends on USB=y || (USB=m && USB_GADGET=m)
468 This host controller driver emulates USB, looping all data transfer
469 requests back to a USB "gadget driver" in the same host. The host
470 side is the master; the gadget side is the slave. Gadget drivers
471 can be high, full, or low speed; and they have access to endpoints
472 like those from NET2280, PXA2xx, or SA1100 hardware.
474 This may help in some stages of creating a driver to embed in a
475 Linux device, since it lets you debug several parts of the gadget
476 driver without its hardware or drivers being involved.
478 Since such a gadget side driver needs to interoperate with a host
479 side Linux-USB device driver, this may help to debug both sides
480 of a USB protocol stack.
482 Say "y" to link the driver statically, or "m" to build a
483 dynamically linked module called "dummy_hcd" and force all
484 gadget drivers to also be dynamically linked.
486 # NOTE: Please keep dummy_hcd LAST so that "real hardware" appears
487 # first and will be selected by default.
495 # composite based drivers
496 config USB_LIBCOMPOSITE
499 depends on USB_GADGET
517 tristate "USB Gadget Drivers"
520 A Linux "Gadget Driver" talks to the USB Peripheral Controller
521 driver through the abstract "gadget" API. Some other operating
522 systems call these "client" drivers, of which "class drivers"
523 are a subset (implementing a USB device class specification).
524 A gadget driver implements one or more USB functions using
525 the peripheral hardware.
527 Gadget drivers are hardware-neutral, or "platform independent",
528 except that they sometimes must understand quirks or limitations
529 of the particular controllers they work with. For example, when
530 a controller doesn't support alternate configurations or provide
531 enough of the right types of endpoints, the gadget driver might
532 not be able work with that controller, or might need to implement
533 a less common variant of a device class protocol.
535 # this first set of drivers all depend on bulk-capable hardware.
538 tristate "Gadget Zero (DEVELOPMENT)"
539 select USB_LIBCOMPOSITE
542 Gadget Zero is a two-configuration device. It either sinks and
543 sources bulk data; or it loops back a configurable number of
544 transfers. It also implements control requests, for "chapter 9"
545 conformance. The driver needs only two bulk-capable endpoints, so
546 it can work on top of most device-side usb controllers. It's
547 useful for testing, and is also a working example showing how
548 USB "gadget drivers" can be written.
550 Make this be the first driver you try using on top of any new
551 USB peripheral controller driver. Then you can use host-side
552 test software, like the "usbtest" driver, to put your hardware
553 and its driver through a basic set of functional tests.
555 Gadget Zero also works with the host-side "usb-skeleton" driver,
556 and with many kinds of host-side test software. You may need
557 to tweak product and vendor IDs before host software knows about
558 this device, and arrange to select an appropriate configuration.
560 Say "y" to link the driver statically, or "m" to build a
561 dynamically linked module called "g_zero".
563 config USB_ZERO_HNPTEST
564 boolean "HNP Test Device"
565 depends on USB_ZERO && USB_OTG
567 You can configure this device to enumerate using the device
568 identifiers of the USB-OTG test device. That means that when
569 this gadget connects to another OTG device, with this one using
570 the "B-Peripheral" role, that device will use HNP to let this
571 one serve as the USB host instead (in the "B-Host" role).
574 tristate "Audio Gadget"
576 select USB_LIBCOMPOSITE
579 This Gadget Audio driver is compatible with USB Audio Class
580 specification 2.0. It implements 1 AudioControl interface,
581 1 AudioStreaming Interface each for USB-OUT and USB-IN.
582 Number of channels, sample rate and sample size can be
583 specified as module parameters.
584 This driver doesn't expect any real Audio codec to be present
585 on the device - the audio streams are simply sinked to and
586 sourced from a virtual ALSA sound card created. The user-space
587 application may choose to do whatever it wants with the data
588 received from the USB Host and choose to provide whatever it
589 wants as audio data to the USB Host.
591 Say "y" to link the driver statically, or "m" to build a
592 dynamically linked module called "g_audio".
595 bool "UAC 1.0 (Legacy)"
598 If you instead want older UAC Spec-1.0 driver that also has audio
599 paths hardwired to the Audio codec chip on-board and doesn't work
603 tristate "Ethernet Gadget (with CDC Ethernet support)"
605 select USB_LIBCOMPOSITE
608 This driver implements Ethernet style communication, in one of
611 - The "Communication Device Class" (CDC) Ethernet Control Model.
612 That protocol is often avoided with pure Ethernet adapters, in
613 favor of simpler vendor-specific hardware, but is widely
614 supported by firmware for smart network devices.
616 - On hardware can't implement that protocol, a simple CDC subset
617 is used, placing fewer demands on USB.
619 - CDC Ethernet Emulation Model (EEM) is a newer standard that has
620 a simpler interface that can be used by more USB hardware.
622 RNDIS support is an additional option, more demanding than than
625 Within the USB device, this gadget driver exposes a network device
626 "usbX", where X depends on what other networking devices you have.
627 Treat it like a two-node Ethernet link: host, and gadget.
629 The Linux-USB host-side "usbnet" driver interoperates with this
630 driver, so that deep I/O queues can be supported. On 2.4 kernels,
631 use "CDCEther" instead, if you're using the CDC option. That CDC
632 mode should also interoperate with standard CDC Ethernet class
633 drivers on other host operating systems.
635 Say "y" to link the driver statically, or "m" to build a
636 dynamically linked module called "g_ether".
641 select USB_LIBCOMPOSITE
644 Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol,
645 and Microsoft provides redistributable binary RNDIS drivers for
646 older versions of Windows.
648 If you say "y" here, the Ethernet gadget driver will try to provide
649 a second device configuration, supporting RNDIS to talk to such
652 To make MS-Windows work with this, use Documentation/usb/linux.inf
653 as the "driver info file". For versions of MS-Windows older than
654 XP, you'll need to download drivers from Microsoft's website; a URL
655 is given in comments found in that info file.
658 bool "Ethernet Emulation Model (EEM) support"
660 select USB_LIBCOMPOSITE
663 CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM
664 and therefore can be supported by more hardware. Technically ECM and
665 EEM are designed for different applications. The ECM model extends
666 the network interface to the target (e.g. a USB cable modem), and the
667 EEM model is for mobile devices to communicate with hosts using
668 ethernet over USB. For Linux gadgets, however, the interface with
669 the host is the same (a usbX device), so the differences are minimal.
671 If you say "y" here, the Ethernet gadget driver will use the EEM
672 protocol rather than ECM. If unsure, say "n".
675 tristate "Network Control Model (NCM) support"
677 select USB_LIBCOMPOSITE
680 This driver implements USB CDC NCM subclass standard. NCM is
681 an advanced protocol for Ethernet encapsulation, allows grouping
682 of several ethernet frames into one USB transfer and different
683 alignment possibilities.
685 Say "y" to link the driver statically, or "m" to build a
686 dynamically linked module called "g_ncm".
689 tristate "Gadget Filesystem"
691 This driver provides a filesystem based API that lets user mode
692 programs implement a single-configuration USB device, including
693 endpoint I/O and control requests that don't relate to enumeration.
694 All endpoints, transfer speeds, and transfer types supported by
695 the hardware are available, through read() and write() calls.
697 Say "y" to link the driver statically, or "m" to build a
698 dynamically linked module called "gadgetfs".
700 config USB_FUNCTIONFS
701 tristate "Function Filesystem"
702 select USB_LIBCOMPOSITE
703 select USB_FUNCTIONFS_GENERIC if !(USB_FUNCTIONFS_ETH || USB_FUNCTIONFS_RNDIS)
705 The Function Filesystem (FunctionFS) lets one create USB
706 composite functions in user space in the same way GadgetFS
707 lets one create USB gadgets in user space. This allows creation
708 of composite gadgets such that some of the functions are
709 implemented in kernel space (for instance Ethernet, serial or
710 mass storage) and other are implemented in user space.
712 If you say "y" or "m" here you will be able what kind of
713 configurations the gadget will provide.
715 Say "y" to link the driver statically, or "m" to build
716 a dynamically linked module called "g_ffs".
718 config USB_FUNCTIONFS_ETH
719 bool "Include configuration with CDC ECM (Ethernet)"
720 depends on USB_FUNCTIONFS && NET
722 Include a configuration with CDC ECM function (Ethernet) and the
725 config USB_FUNCTIONFS_RNDIS
726 bool "Include configuration with RNDIS (Ethernet)"
727 depends on USB_FUNCTIONFS && NET
729 Include a configuration with RNDIS function (Ethernet) and the Filesystem.
731 config USB_FUNCTIONFS_GENERIC
732 bool "Include 'pure' configuration"
733 depends on USB_FUNCTIONFS
735 Include a configuration with the Function Filesystem alone with
736 no Ethernet interface.
738 config USB_MASS_STORAGE
739 tristate "Mass Storage Gadget"
741 select USB_LIBCOMPOSITE
743 The Mass Storage Gadget acts as a USB Mass Storage disk drive.
744 As its storage repository it can use a regular file or a block
745 device (in much the same way as the "loop" device driver),
746 specified as a module parameter or sysfs option.
748 This driver is a replacement for now removed File-backed
749 Storage Gadget (g_file_storage).
751 Say "y" to link the driver statically, or "m" to build
752 a dynamically linked module called "g_mass_storage".
754 config USB_GADGET_TARGET
755 tristate "USB Gadget Target Fabric Module"
756 depends on TARGET_CORE
757 select USB_LIBCOMPOSITE
759 This fabric is an USB gadget. Two USB protocols are supported that is
760 BBB or BOT (Bulk Only Transport) and UAS (USB Attached SCSI). BOT is
761 advertised on alternative interface 0 (primary) and UAS is on
762 alternative interface 1. Both protocols can work on USB2.0 and USB3.0.
763 UAS utilizes the USB 3.0 feature called streams support.
766 tristate "Serial Gadget (with CDC ACM and CDC OBEX support)"
772 select USB_LIBCOMPOSITE
774 The Serial Gadget talks to the Linux-USB generic serial driver.
775 This driver supports a CDC-ACM module option, which can be used
776 to interoperate with MS-Windows hosts or with the Linux-USB
779 This driver also supports a CDC-OBEX option. You will need a
780 user space OBEX server talking to /dev/ttyGS*, since the kernel
781 itself doesn't implement the OBEX protocol.
783 Say "y" to link the driver statically, or "m" to build a
784 dynamically linked module called "g_serial".
786 For more information, see Documentation/usb/gadget_serial.txt
787 which includes instructions and a "driver info file" needed to
788 make MS-Windows work with CDC ACM.
790 config USB_MIDI_GADGET
791 tristate "MIDI Gadget"
793 select USB_LIBCOMPOSITE
796 The MIDI Gadget acts as a USB Audio device, with one MIDI
797 input and one MIDI output. These MIDI jacks appear as
798 a sound "card" in the ALSA sound system. Other MIDI
799 connections can then be made on the gadget system, using
800 ALSA's aconnect utility etc.
802 Say "y" to link the driver statically, or "m" to build a
803 dynamically linked module called "g_midi".
806 tristate "Printer Gadget"
807 select USB_LIBCOMPOSITE
809 The Printer Gadget channels data between the USB host and a
810 userspace program driving the print engine. The user space
811 program reads and writes the device file /dev/g_printer to
812 receive or send printer data. It can use ioctl calls to
813 the device file to get or set printer status.
815 Say "y" to link the driver statically, or "m" to build a
816 dynamically linked module called "g_printer".
818 For more information, see Documentation/usb/gadget_printer.txt
819 which includes sample code for accessing the device file.
823 config USB_CDC_COMPOSITE
824 tristate "CDC Composite Device (Ethernet and ACM)"
826 select USB_LIBCOMPOSITE
830 This driver provides two functions in one configuration:
831 a CDC Ethernet (ECM) link, and a CDC ACM (serial port) link.
833 This driver requires four bulk and two interrupt endpoints,
834 plus the ability to handle altsettings. Not all peripheral
835 controllers are that capable.
837 Say "y" to link the driver statically, or "m" to build a
838 dynamically linked module.
841 tristate "Nokia composite gadget"
843 select USB_LIBCOMPOSITE
847 The Nokia composite gadget provides support for acm, obex
848 and phonet in only one composite gadget driver.
850 It's only really useful for N900 hardware. If you're building
851 a kernel for N900, say Y or M here. If unsure, say N.
854 tristate "CDC Composite Device (ACM and mass storage)"
856 select USB_LIBCOMPOSITE
860 This driver provides two functions in one configuration:
861 a mass storage, and a CDC ACM (serial port) link.
863 Say "y" to link the driver statically, or "m" to build a
864 dynamically linked module called "g_acm_ms".
867 tristate "Multifunction Composite Gadget"
868 depends on BLOCK && NET
869 select USB_G_MULTI_CDC if !USB_G_MULTI_RNDIS
870 select USB_LIBCOMPOSITE
874 The Multifunction Composite Gadget provides Ethernet (RNDIS
875 and/or CDC Ethernet), mass storage and ACM serial link
878 You will be asked to choose which of the two configurations is
879 to be available in the gadget. At least one configuration must
880 be chosen to make the gadget usable. Selecting more than one
881 configuration will prevent Windows from automatically detecting
882 the gadget as a composite gadget, so an INF file will be needed to
885 Say "y" to link the driver statically, or "m" to build a
886 dynamically linked module called "g_multi".
888 config USB_G_MULTI_RNDIS
889 bool "RNDIS + CDC Serial + Storage configuration"
890 depends on USB_G_MULTI
893 This option enables a configuration with RNDIS, CDC Serial and
894 Mass Storage functions available in the Multifunction Composite
895 Gadget. This is the configuration dedicated for Windows since RNDIS
896 is Microsoft's protocol.
900 config USB_G_MULTI_CDC
901 bool "CDC Ethernet + CDC Serial + Storage configuration"
902 depends on USB_G_MULTI
905 This option enables a configuration with CDC Ethernet (ECM), CDC
906 Serial and Mass Storage functions available in the Multifunction
914 tristate "HID Gadget"
915 select USB_LIBCOMPOSITE
917 The HID gadget driver provides generic emulation of USB
918 Human Interface Devices (HID).
920 For more information, see Documentation/usb/gadget_hid.txt which
921 includes sample code for accessing the device files.
923 Say "y" to link the driver statically, or "m" to build a
924 dynamically linked module called "g_hid".
926 # Standalone / single function gadgets
928 tristate "EHCI Debug Device Gadget"
930 select USB_LIBCOMPOSITE
932 This gadget emulates an EHCI Debug device. This is useful when you want
933 to interact with an EHCI Debug Port.
935 Say "y" to link the driver statically, or "m" to build a
936 dynamically linked module called "g_dbgp".
940 prompt "EHCI Debug Device mode"
941 default USB_G_DBGP_SERIAL
943 config USB_G_DBGP_PRINTK
944 depends on USB_G_DBGP
947 Directly printk() received data. No interaction.
949 config USB_G_DBGP_SERIAL
950 depends on USB_G_DBGP
954 Userland can interact using /dev/ttyGSxxx.
958 # put drivers that need isochronous transfer support (for audio
959 # or video class gadget drivers), or specific hardware, here.
961 tristate "USB Webcam Gadget"
963 select USB_LIBCOMPOSITE
964 select VIDEOBUF2_VMALLOC
966 The Webcam Gadget acts as a composite USB Audio and Video Class
967 device. It provides a userspace API to process UVC control requests
968 and stream video data to the host.
970 Say "y" to link the driver statically, or "m" to build a
971 dynamically linked module called "g_webcam".