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
150 This option selects the USB device controller in the LPC32xx SoC.
152 Say "y" to link the driver statically, or "m" to build a
153 dynamically linked module called "lpc32xx_udc" and force all
154 gadget drivers to also be dynamically linked.
156 config USB_ATMEL_USBA
157 tristate "Atmel USBA"
158 depends on AVR32 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
160 USBA is the integrated high-speed USB Device controller on
161 the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel.
163 config USB_BCM63XX_UDC
164 tristate "Broadcom BCM63xx Peripheral Controller"
167 Many Broadcom BCM63xx chipsets (such as the BCM6328) have a
168 high speed USB Device Port with support for four fixed endpoints
169 (plus endpoint zero).
171 Say "y" to link the driver statically, or "m" to build a
172 dynamically linked module called "bcm63xx_udc".
175 tristate "Freescale Highspeed USB DR Peripheral Controller"
176 depends on FSL_SOC || ARCH_MXC
177 select USB_FSL_MPH_DR_OF if OF
179 Some of Freescale PowerPC and i.MX processors have a High Speed
180 Dual-Role(DR) USB controller, which supports device mode.
182 The number of programmable endpoints is different through
185 Say "y" to link the driver statically, or "m" to build a
186 dynamically linked module called "fsl_usb2_udc" and force
187 all gadget drivers to also be dynamically linked.
189 config USB_GADGET_XUSBPS
190 tristate "Xilinx PS Highspeed USB DR Peripheral Controller"
192 select USB_GADGET_DUALSPEED
193 select USB_XUSBPS_DR_OF if OF
195 Xilinx PS USB controller core supports device mode.
197 Say "y" to link the driver statically, or "m" to build a
198 dynamically linked module called "xilinx_usbps_udc" and
199 force all gadget drivers to also be dynamically linked.
201 config XUSBPS_ERRATA_DT654401
202 bool "USB Errata: Adding a dTD to a Primed Endpoint May Not Get Recognized"
203 depends on USB_GADGET_XUSBPS
205 There is an issue with the add dTD tripwire semaphore (ATDTW bit
206 in USBCMD register) that can cause the controller to ignore a dTD
207 that is added to a primed endpoint. When this happens, the software
208 can read the tripwire bit and the status bit at '1' even though
209 the endpoint is unprimed.
211 This issue is only applicable for the Zynq silicon revisions < 3.0.
212 For silicon versions 3.0 and higher, disable this option.
216 depends on USB_GADGET_XUSBPS
218 select USB_GADGET_SELECTED
221 tristate "Faraday FUSB300 USB Peripheral Controller"
222 depends on !PHYS_ADDR_T_64BIT
224 Faraday usb device controller FUSB300 driver
227 tristate "OMAP USB Device Controller"
228 depends on ARCH_OMAP1
230 select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_H4_OTG
232 Many Texas Instruments OMAP processors have flexible full
233 speed USB device controllers, with support for up to 30
234 endpoints (plus endpoint zero). This driver supports the
235 controller in the OMAP 1611, and should work with controllers
236 in other OMAP processors too, given minor tweaks.
238 Say "y" to link the driver statically, or "m" to build a
239 dynamically linked module called "omap_udc" and force all
240 gadget drivers to also be dynamically linked.
243 tristate "PXA 25x or IXP 4xx"
244 depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX
246 Intel's PXA 25x series XScale ARM-5TE processors include
247 an integrated full speed USB 1.1 device controller. The
248 controller in the IXP 4xx series is register-compatible.
250 It has fifteen fixed-function endpoints, as well as endpoint
251 zero (for control transfers).
253 Say "y" to link the driver statically, or "m" to build a
254 dynamically linked module called "pxa25x_udc" and force all
255 gadget drivers to also be dynamically linked.
257 # if there's only one gadget driver, using only two bulk endpoints,
258 # don't waste memory for the other endpoints
259 config USB_PXA25X_SMALL
260 depends on USB_PXA25X
262 default n if USB_ETH_RNDIS
263 default y if USB_ZERO
265 default y if USB_G_SERIAL
268 tristate "Renesas R8A66597 USB Peripheral Controller"
270 R8A66597 is a discrete USB host and peripheral controller chip that
271 supports both full and high speed USB 2.0 data transfers.
272 It has nine configurable endpoints, and endpoint zero.
274 Say "y" to link the driver statically, or "m" to build a
275 dynamically linked module called "r8a66597_udc" and force all
276 gadget drivers to also be dynamically linked.
278 config USB_GADGET_XILINX
279 boolean "Xilinx USB Driver"
280 depends on (XILINX_VIRTEX || MICROBLAZE || ARCH_ZYNQ)
281 select USB_GADGET_DUALSPEED
283 Sample USB gadget driver
285 config USB_RENESAS_USBHS_UDC
286 tristate 'Renesas USBHS controller'
287 depends on USB_RENESAS_USBHS
289 Renesas USBHS is a discrete USB host and peripheral controller chip
290 that supports both full and high speed USB 2.0 data transfers.
291 It has nine or more configurable endpoints, and endpoint zero.
293 Say "y" to link the driver statically, or "m" to build a
294 dynamically linked module called "renesas_usbhs" and force all
295 gadget drivers to also be dynamically linked.
300 Intel's PXA 27x series XScale ARM v5TE processors include
301 an integrated full speed USB 1.1 device controller.
303 It has up to 23 endpoints, as well as endpoint zero (for
306 Say "y" to link the driver statically, or "m" to build a
307 dynamically linked module called "pxa27x_udc" and force all
308 gadget drivers to also be dynamically linked.
311 tristate "S3C HS/OtG USB Device controller"
312 depends on S3C_DEV_USB_HSOTG
314 The Samsung S3C64XX USB2.0 high-speed gadget controller
315 integrated into the S3C64XX series SoC.
318 tristate "Freescale i.MX1 USB Peripheral Controller"
322 Freescale's i.MX1 includes an integrated full speed
323 USB 1.1 device controller.
325 It has Six fixed-function endpoints, as well as endpoint
326 zero (for control transfers).
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.
333 tristate "S3C2410 USB Device Controller"
334 depends on ARCH_S3C24XX
336 Samsung's S3C2410 is an ARM-4 processor with an integrated
337 full speed USB 1.1 device controller. It has 4 configurable
338 endpoints, as well as endpoint zero (for control transfers).
340 This driver has been tested on the S3C2410, S3C2412, and
343 config USB_S3C2410_DEBUG
344 boolean "S3C2410 udc debug messages"
345 depends on USB_S3C2410
348 tristate "S3C2416, S3C2443 and S3C2450 USB Device Controller"
349 depends on ARCH_S3C24XX
351 Samsung's S3C2416, S3C2443 and S3C2450 is an ARM9 based SoC
352 integrated with dual speed USB 2.0 device controller. It has
353 8 endpoints, as well as endpoint zero.
355 This driver has been tested on S3C2416 and S3C2450 processors.
358 tristate "Marvell USB2.0 Device Controller"
359 depends on GENERIC_HARDIRQS
361 Marvell Socs (including PXA and MMP series) include a high speed
362 USB2.0 OTG controller, which can be configured as high speed or
363 full speed USB peripheral.
366 tristate "MARVELL PXA2128 USB 3.0 controller"
368 MARVELL PXA2128 Processor series include a super speed USB3.0 device
369 controller, which support super speed USB peripheral.
372 # Controllers available in both integrated and discrete versions
375 # musb builds in ../musb along with host support
376 config USB_GADGET_MUSB_HDRC
377 tristate "Inventra HDRC USB Peripheral (TI, ADI, ...)"
378 depends on USB_MUSB_HDRC
380 This OTG-capable silicon IP is used in dual designs including
381 the TI DaVinci, OMAP 243x, OMAP 343x, TUSB 6010, and ADI Blackfin
384 tristate "Renesas M66592 USB Peripheral Controller"
386 M66592 is a discrete USB peripheral controller chip that
387 supports both full and high speed USB 2.0 data transfers.
388 It has seven configurable endpoints, and endpoint zero.
390 Say "y" to link the driver statically, or "m" to build a
391 dynamically linked module called "m66592_udc" and force all
392 gadget drivers to also be dynamically linked.
395 # Controllers available only in discrete form (and all PCI controllers)
398 config USB_AMD5536UDC
399 tristate "AMD5536 UDC"
402 The AMD5536 UDC is part of the AMD Geode CS5536, an x86 southbridge.
403 It is a USB Highspeed DMA capable USB device controller. Beside ep0
404 it provides 4 IN and 4 OUT endpoints (bulk or interrupt type).
405 The UDC port supports OTG operation, and may be used as a host port
406 if it's not being used to implement peripheral or OTG roles.
408 Say "y" to link the driver statically, or "m" to build a
409 dynamically linked module called "amd5536udc" and force all
410 gadget drivers to also be dynamically linked.
413 tristate "Freescale QE/CPM USB Device Controller"
414 depends on FSL_SOC && (QUICC_ENGINE || CPM)
416 Some of Freescale PowerPC processors have a Full Speed
417 QE/CPM2 USB controller, which support device mode with 4
418 programmable endpoints. This driver supports the
419 controller in the MPC8360 and MPC8272, and should work with
420 controllers having QE or CPM2, given minor tweaks.
422 Set CONFIG_USB_GADGET to "m" to build this driver as a
423 dynamically linked module called "fsl_qe_udc".
426 tristate "PLX NET2272"
428 PLX NET2272 is a USB peripheral controller which supports
429 both full and high speed USB 2.0 data transfers.
431 It has three configurable endpoints, as well as endpoint zero
432 (for control transfer).
433 Say "y" to link the driver statically, or "m" to build a
434 dynamically linked module called "net2272" and force all
435 gadget drivers to also be dynamically linked.
437 config USB_NET2272_DMA
438 boolean "Support external DMA controller"
439 depends on USB_NET2272
441 The NET2272 part can optionally support an external DMA
442 controller, but your board has to have support in the
445 If unsure, say "N" here. The driver works fine in PIO mode.
448 tristate "NetChip 228x"
451 NetChip 2280 / 2282 is a PCI based USB peripheral controller which
452 supports both full and high speed USB 2.0 data transfers.
454 It has six configurable endpoints, as well as endpoint zero
455 (for control transfers) and several endpoints with dedicated
458 Say "y" to link the driver statically, or "m" to build a
459 dynamically linked module called "net2280" and force all
460 gadget drivers to also be dynamically linked.
463 tristate "Toshiba TC86C001 'Goku-S'"
466 The Toshiba TC86C001 is a PCI device which includes controllers
467 for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI).
469 The device controller has three configurable (bulk or interrupt)
470 endpoints, plus endpoint zero (for control transfers).
472 Say "y" to link the driver statically, or "m" to build a
473 dynamically linked module called "goku_udc" and to force all
474 gadget drivers to also be dynamically linked.
477 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7213/ML7831) UDC"
478 depends on PCI && GENERIC_HARDIRQS
480 This is a USB device driver for EG20T PCH.
481 EG20T PCH is the platform controller hub that is used in Intel's
482 general embedded platform. EG20T PCH has USB device interface.
483 Using this interface, it is able to access system devices connected
485 This driver enables USB device function.
486 USB device is a USB peripheral controller which
487 supports both full and high speed USB 2.0 data transfers.
488 This driver supports both control transfer and bulk transfer modes.
489 This driver dose not support interrupt transfer or isochronous
492 This driver also can be used for LAPIS Semiconductor's ML7213 which is
493 for IVI(In-Vehicle Infotainment) use.
494 ML7831 is for general purpose use.
495 ML7213/ML7831 is companion chip for Intel Atom E6xx series.
496 ML7213/ML7831 is completely compatible for Intel EG20T PCH.
499 # LAST -- dummy/emulated controller
503 tristate "Dummy HCD (DEVELOPMENT)"
504 depends on USB=y || (USB=m && USB_GADGET=m)
506 This host controller driver emulates USB, looping all data transfer
507 requests back to a USB "gadget driver" in the same host. The host
508 side is the master; the gadget side is the slave. Gadget drivers
509 can be high, full, or low speed; and they have access to endpoints
510 like those from NET2280, PXA2xx, or SA1100 hardware.
512 This may help in some stages of creating a driver to embed in a
513 Linux device, since it lets you debug several parts of the gadget
514 driver without its hardware or drivers being involved.
516 Since such a gadget side driver needs to interoperate with a host
517 side Linux-USB device driver, this may help to debug both sides
518 of a USB protocol stack.
520 Say "y" to link the driver statically, or "m" to build a
521 dynamically linked module called "dummy_hcd" and force all
522 gadget drivers to also be dynamically linked.
524 # NOTE: Please keep dummy_hcd LAST so that "real hardware" appears
525 # first and will be selected by default.
533 # composite based drivers
534 config USB_LIBCOMPOSITE
537 depends on USB_GADGET
555 tristate "USB Gadget Drivers"
558 A Linux "Gadget Driver" talks to the USB Peripheral Controller
559 driver through the abstract "gadget" API. Some other operating
560 systems call these "client" drivers, of which "class drivers"
561 are a subset (implementing a USB device class specification).
562 A gadget driver implements one or more USB functions using
563 the peripheral hardware.
565 Gadget drivers are hardware-neutral, or "platform independent",
566 except that they sometimes must understand quirks or limitations
567 of the particular controllers they work with. For example, when
568 a controller doesn't support alternate configurations or provide
569 enough of the right types of endpoints, the gadget driver might
570 not be able work with that controller, or might need to implement
571 a less common variant of a device class protocol.
573 # this first set of drivers all depend on bulk-capable hardware.
576 tristate "Gadget Zero (DEVELOPMENT)"
577 select USB_LIBCOMPOSITE
580 Gadget Zero is a two-configuration device. It either sinks and
581 sources bulk data; or it loops back a configurable number of
582 transfers. It also implements control requests, for "chapter 9"
583 conformance. The driver needs only two bulk-capable endpoints, so
584 it can work on top of most device-side usb controllers. It's
585 useful for testing, and is also a working example showing how
586 USB "gadget drivers" can be written.
588 Make this be the first driver you try using on top of any new
589 USB peripheral controller driver. Then you can use host-side
590 test software, like the "usbtest" driver, to put your hardware
591 and its driver through a basic set of functional tests.
593 Gadget Zero also works with the host-side "usb-skeleton" driver,
594 and with many kinds of host-side test software. You may need
595 to tweak product and vendor IDs before host software knows about
596 this device, and arrange to select an appropriate configuration.
598 Say "y" to link the driver statically, or "m" to build a
599 dynamically linked module called "g_zero".
601 config USB_ZERO_HNPTEST
602 boolean "HNP Test Device"
603 depends on USB_ZERO && USB_OTG
605 You can configure this device to enumerate using the device
606 identifiers of the USB-OTG test device. That means that when
607 this gadget connects to another OTG device, with this one using
608 the "B-Peripheral" role, that device will use HNP to let this
609 one serve as the USB host instead (in the "B-Host" role).
612 tristate "Audio Gadget"
614 select USB_LIBCOMPOSITE
617 This Gadget Audio driver is compatible with USB Audio Class
618 specification 2.0. It implements 1 AudioControl interface,
619 1 AudioStreaming Interface each for USB-OUT and USB-IN.
620 Number of channels, sample rate and sample size can be
621 specified as module parameters.
622 This driver doesn't expect any real Audio codec to be present
623 on the device - the audio streams are simply sinked to and
624 sourced from a virtual ALSA sound card created. The user-space
625 application may choose to do whatever it wants with the data
626 received from the USB Host and choose to provide whatever it
627 wants as audio data to the USB Host.
629 Say "y" to link the driver statically, or "m" to build a
630 dynamically linked module called "g_audio".
633 bool "UAC 1.0 (Legacy)"
636 If you instead want older UAC Spec-1.0 driver that also has audio
637 paths hardwired to the Audio codec chip on-board and doesn't work
641 tristate "Ethernet Gadget (with CDC Ethernet support)"
643 select USB_LIBCOMPOSITE
646 This driver implements Ethernet style communication, in one of
649 - The "Communication Device Class" (CDC) Ethernet Control Model.
650 That protocol is often avoided with pure Ethernet adapters, in
651 favor of simpler vendor-specific hardware, but is widely
652 supported by firmware for smart network devices.
654 - On hardware can't implement that protocol, a simple CDC subset
655 is used, placing fewer demands on USB.
657 - CDC Ethernet Emulation Model (EEM) is a newer standard that has
658 a simpler interface that can be used by more USB hardware.
660 RNDIS support is an additional option, more demanding than than
663 Within the USB device, this gadget driver exposes a network device
664 "usbX", where X depends on what other networking devices you have.
665 Treat it like a two-node Ethernet link: host, and gadget.
667 The Linux-USB host-side "usbnet" driver interoperates with this
668 driver, so that deep I/O queues can be supported. On 2.4 kernels,
669 use "CDCEther" instead, if you're using the CDC option. That CDC
670 mode should also interoperate with standard CDC Ethernet class
671 drivers on other host operating systems.
673 Say "y" to link the driver statically, or "m" to build a
674 dynamically linked module called "g_ether".
679 select USB_LIBCOMPOSITE
682 Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol,
683 and Microsoft provides redistributable binary RNDIS drivers for
684 older versions of Windows.
686 If you say "y" here, the Ethernet gadget driver will try to provide
687 a second device configuration, supporting RNDIS to talk to such
690 To make MS-Windows work with this, use Documentation/usb/linux.inf
691 as the "driver info file". For versions of MS-Windows older than
692 XP, you'll need to download drivers from Microsoft's website; a URL
693 is given in comments found in that info file.
696 bool "Ethernet Emulation Model (EEM) support"
698 select USB_LIBCOMPOSITE
701 CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM
702 and therefore can be supported by more hardware. Technically ECM and
703 EEM are designed for different applications. The ECM model extends
704 the network interface to the target (e.g. a USB cable modem), and the
705 EEM model is for mobile devices to communicate with hosts using
706 ethernet over USB. For Linux gadgets, however, the interface with
707 the host is the same (a usbX device), so the differences are minimal.
709 If you say "y" here, the Ethernet gadget driver will use the EEM
710 protocol rather than ECM. If unsure, say "n".
713 tristate "Network Control Model (NCM) support"
715 select USB_LIBCOMPOSITE
718 This driver implements USB CDC NCM subclass standard. NCM is
719 an advanced protocol for Ethernet encapsulation, allows grouping
720 of several ethernet frames into one USB transfer and different
721 alignment possibilities.
723 Say "y" to link the driver statically, or "m" to build a
724 dynamically linked module called "g_ncm".
727 tristate "Gadget Filesystem"
729 This driver provides a filesystem based API that lets user mode
730 programs implement a single-configuration USB device, including
731 endpoint I/O and control requests that don't relate to enumeration.
732 All endpoints, transfer speeds, and transfer types supported by
733 the hardware are available, through read() and write() calls.
735 Say "y" to link the driver statically, or "m" to build a
736 dynamically linked module called "gadgetfs".
738 config USB_FUNCTIONFS
739 tristate "Function Filesystem"
740 select USB_LIBCOMPOSITE
741 select USB_FUNCTIONFS_GENERIC if !(USB_FUNCTIONFS_ETH || USB_FUNCTIONFS_RNDIS)
743 The Function Filesystem (FunctionFS) lets one create USB
744 composite functions in user space in the same way GadgetFS
745 lets one create USB gadgets in user space. This allows creation
746 of composite gadgets such that some of the functions are
747 implemented in kernel space (for instance Ethernet, serial or
748 mass storage) and other are implemented in user space.
750 If you say "y" or "m" here you will be able what kind of
751 configurations the gadget will provide.
753 Say "y" to link the driver statically, or "m" to build
754 a dynamically linked module called "g_ffs".
756 config USB_FUNCTIONFS_ETH
757 bool "Include configuration with CDC ECM (Ethernet)"
758 depends on USB_FUNCTIONFS && NET
760 Include a configuration with CDC ECM function (Ethernet) and the
763 config USB_FUNCTIONFS_RNDIS
764 bool "Include configuration with RNDIS (Ethernet)"
765 depends on USB_FUNCTIONFS && NET
767 Include a configuration with RNDIS function (Ethernet) and the Filesystem.
769 config USB_FUNCTIONFS_GENERIC
770 bool "Include 'pure' configuration"
771 depends on USB_FUNCTIONFS
773 Include a configuration with the Function Filesystem alone with
774 no Ethernet interface.
776 config USB_MASS_STORAGE
777 tristate "Mass Storage Gadget"
779 select USB_LIBCOMPOSITE
781 The Mass Storage Gadget acts as a USB Mass Storage disk drive.
782 As its storage repository it can use a regular file or a block
783 device (in much the same way as the "loop" device driver),
784 specified as a module parameter or sysfs option.
786 This driver is a replacement for now removed File-backed
787 Storage Gadget (g_file_storage).
789 Say "y" to link the driver statically, or "m" to build
790 a dynamically linked module called "g_mass_storage".
792 config USB_GADGET_TARGET
793 tristate "USB Gadget Target Fabric Module"
794 depends on TARGET_CORE
795 select USB_LIBCOMPOSITE
797 This fabric is an USB gadget. Two USB protocols are supported that is
798 BBB or BOT (Bulk Only Transport) and UAS (USB Attached SCSI). BOT is
799 advertised on alternative interface 0 (primary) and UAS is on
800 alternative interface 1. Both protocols can work on USB2.0 and USB3.0.
801 UAS utilizes the USB 3.0 feature called streams support.
804 tristate "Serial Gadget (with CDC ACM and CDC OBEX support)"
810 select USB_LIBCOMPOSITE
812 The Serial Gadget talks to the Linux-USB generic serial driver.
813 This driver supports a CDC-ACM module option, which can be used
814 to interoperate with MS-Windows hosts or with the Linux-USB
817 This driver also supports a CDC-OBEX option. You will need a
818 user space OBEX server talking to /dev/ttyGS*, since the kernel
819 itself doesn't implement the OBEX protocol.
821 Say "y" to link the driver statically, or "m" to build a
822 dynamically linked module called "g_serial".
824 For more information, see Documentation/usb/gadget_serial.txt
825 which includes instructions and a "driver info file" needed to
826 make MS-Windows work with CDC ACM.
828 config USB_MIDI_GADGET
829 tristate "MIDI Gadget"
831 select USB_LIBCOMPOSITE
834 The MIDI Gadget acts as a USB Audio device, with one MIDI
835 input and one MIDI output. These MIDI jacks appear as
836 a sound "card" in the ALSA sound system. Other MIDI
837 connections can then be made on the gadget system, using
838 ALSA's aconnect utility etc.
840 Say "y" to link the driver statically, or "m" to build a
841 dynamically linked module called "g_midi".
844 tristate "Printer Gadget"
845 select USB_LIBCOMPOSITE
847 The Printer Gadget channels data between the USB host and a
848 userspace program driving the print engine. The user space
849 program reads and writes the device file /dev/g_printer to
850 receive or send printer data. It can use ioctl calls to
851 the device file to get or set printer status.
853 Say "y" to link the driver statically, or "m" to build a
854 dynamically linked module called "g_printer".
856 For more information, see Documentation/usb/gadget_printer.txt
857 which includes sample code for accessing the device file.
861 config USB_CDC_COMPOSITE
862 tristate "CDC Composite Device (Ethernet and ACM)"
864 select USB_LIBCOMPOSITE
868 This driver provides two functions in one configuration:
869 a CDC Ethernet (ECM) link, and a CDC ACM (serial port) link.
871 This driver requires four bulk and two interrupt endpoints,
872 plus the ability to handle altsettings. Not all peripheral
873 controllers are that capable.
875 Say "y" to link the driver statically, or "m" to build a
876 dynamically linked module.
879 tristate "Nokia composite gadget"
881 select USB_LIBCOMPOSITE
885 The Nokia composite gadget provides support for acm, obex
886 and phonet in only one composite gadget driver.
888 It's only really useful for N900 hardware. If you're building
889 a kernel for N900, say Y or M here. If unsure, say N.
892 tristate "CDC Composite Device (ACM and mass storage)"
894 select USB_LIBCOMPOSITE
898 This driver provides two functions in one configuration:
899 a mass storage, and a CDC ACM (serial port) link.
901 Say "y" to link the driver statically, or "m" to build a
902 dynamically linked module called "g_acm_ms".
905 tristate "Multifunction Composite Gadget"
906 depends on BLOCK && NET
907 select USB_G_MULTI_CDC if !USB_G_MULTI_RNDIS
908 select USB_LIBCOMPOSITE
912 The Multifunction Composite Gadget provides Ethernet (RNDIS
913 and/or CDC Ethernet), mass storage and ACM serial link
916 You will be asked to choose which of the two configurations is
917 to be available in the gadget. At least one configuration must
918 be chosen to make the gadget usable. Selecting more than one
919 configuration will prevent Windows from automatically detecting
920 the gadget as a composite gadget, so an INF file will be needed to
923 Say "y" to link the driver statically, or "m" to build a
924 dynamically linked module called "g_multi".
926 config USB_G_MULTI_RNDIS
927 bool "RNDIS + CDC Serial + Storage configuration"
928 depends on USB_G_MULTI
931 This option enables a configuration with RNDIS, CDC Serial and
932 Mass Storage functions available in the Multifunction Composite
933 Gadget. This is the configuration dedicated for Windows since RNDIS
934 is Microsoft's protocol.
938 config USB_G_MULTI_CDC
939 bool "CDC Ethernet + CDC Serial + Storage configuration"
940 depends on USB_G_MULTI
943 This option enables a configuration with CDC Ethernet (ECM), CDC
944 Serial and Mass Storage functions available in the Multifunction
952 tristate "HID Gadget"
953 select USB_LIBCOMPOSITE
955 The HID gadget driver provides generic emulation of USB
956 Human Interface Devices (HID).
958 For more information, see Documentation/usb/gadget_hid.txt which
959 includes sample code for accessing the device files.
961 Say "y" to link the driver statically, or "m" to build a
962 dynamically linked module called "g_hid".
964 # Standalone / single function gadgets
966 tristate "EHCI Debug Device Gadget"
968 select USB_LIBCOMPOSITE
970 This gadget emulates an EHCI Debug device. This is useful when you want
971 to interact with an EHCI Debug Port.
973 Say "y" to link the driver statically, or "m" to build a
974 dynamically linked module called "g_dbgp".
978 prompt "EHCI Debug Device mode"
979 default USB_G_DBGP_SERIAL
981 config USB_G_DBGP_PRINTK
982 depends on USB_G_DBGP
985 Directly printk() received data. No interaction.
987 config USB_G_DBGP_SERIAL
988 depends on USB_G_DBGP
992 Userland can interact using /dev/ttyGSxxx.
996 # put drivers that need isochronous transfer support (for audio
997 # or video class gadget drivers), or specific hardware, here.
999 tristate "USB Webcam Gadget"
1000 depends on VIDEO_DEV
1001 select USB_LIBCOMPOSITE
1002 select VIDEOBUF2_VMALLOC
1004 The Webcam Gadget acts as a composite USB Audio and Video Class
1005 device. It provides a userspace API to process UVC control requests
1006 and stream video data to the host.
1008 Say "y" to link the driver statically, or "m" to build a
1009 dynamically linked module called "g_webcam".