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
149 This option selects the USB device controller in the LPC32xx SoC.
151 Say "y" to link the driver statically, or "m" to build a
152 dynamically linked module called "lpc32xx_udc" and force all
153 gadget drivers to also be dynamically linked.
155 config USB_ATMEL_USBA
156 tristate "Atmel USBA"
157 depends on AVR32 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
159 USBA is the integrated high-speed USB Device controller on
160 the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel.
162 config USB_BCM63XX_UDC
163 tristate "Broadcom BCM63xx Peripheral Controller"
166 Many Broadcom BCM63xx chipsets (such as the BCM6328) have a
167 high speed USB Device Port with support for four fixed endpoints
168 (plus endpoint zero).
170 Say "y" to link the driver statically, or "m" to build a
171 dynamically linked module called "bcm63xx_udc".
174 tristate "Freescale Highspeed USB DR Peripheral Controller"
175 depends on FSL_SOC || ARCH_MXC
176 select USB_FSL_MPH_DR_OF if OF
178 Some of Freescale PowerPC and i.MX processors have a High Speed
179 Dual-Role(DR) USB controller, which supports device mode.
181 The number of programmable endpoints is different through
184 Say "y" to link the driver statically, or "m" to build a
185 dynamically linked module called "fsl_usb2_udc" and force
186 all gadget drivers to also be dynamically linked.
189 tristate "Faraday FUSB300 USB Peripheral Controller"
190 depends on !PHYS_ADDR_T_64BIT
192 Faraday usb device controller FUSB300 driver
195 tristate "OMAP USB Device Controller"
196 depends on ARCH_OMAP1
197 select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_H4_OTG
199 Many Texas Instruments OMAP processors have flexible full
200 speed USB device controllers, with support for up to 30
201 endpoints (plus endpoint zero). This driver supports the
202 controller in the OMAP 1611, and should work with controllers
203 in other OMAP processors too, given minor tweaks.
205 Say "y" to link the driver statically, or "m" to build a
206 dynamically linked module called "omap_udc" and force all
207 gadget drivers to also be dynamically linked.
210 tristate "PXA 25x or IXP 4xx"
211 depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX
213 Intel's PXA 25x series XScale ARM-5TE processors include
214 an integrated full speed USB 1.1 device controller. The
215 controller in the IXP 4xx series is register-compatible.
217 It has fifteen fixed-function endpoints, as well as endpoint
218 zero (for control transfers).
220 Say "y" to link the driver statically, or "m" to build a
221 dynamically linked module called "pxa25x_udc" and force all
222 gadget drivers to also be dynamically linked.
224 # if there's only one gadget driver, using only two bulk endpoints,
225 # don't waste memory for the other endpoints
226 config USB_PXA25X_SMALL
227 depends on USB_PXA25X
229 default n if USB_ETH_RNDIS
230 default y if USB_ZERO
232 default y if USB_G_SERIAL
235 tristate "Renesas R8A66597 USB Peripheral Controller"
237 R8A66597 is a discrete USB host and peripheral controller chip that
238 supports both full and high speed USB 2.0 data transfers.
239 It has nine configurable endpoints, and endpoint zero.
241 Say "y" to link the driver statically, or "m" to build a
242 dynamically linked module called "r8a66597_udc" and force all
243 gadget drivers to also be dynamically linked.
245 config USB_RENESAS_USBHS_UDC
246 tristate 'Renesas USBHS controller'
247 depends on USB_RENESAS_USBHS
249 Renesas USBHS is a discrete USB host and peripheral controller chip
250 that supports both full and high speed USB 2.0 data transfers.
251 It has nine or more configurable endpoints, and endpoint zero.
253 Say "y" to link the driver statically, or "m" to build a
254 dynamically linked module called "renesas_usbhs" and force all
255 gadget drivers to also be dynamically linked.
260 Intel's PXA 27x series XScale ARM v5TE processors include
261 an integrated full speed USB 1.1 device controller.
263 It has up to 23 endpoints, as well as endpoint zero (for
266 Say "y" to link the driver statically, or "m" to build a
267 dynamically linked module called "pxa27x_udc" and force all
268 gadget drivers to also be dynamically linked.
271 tristate "S3C HS/OtG USB Device controller"
272 depends on S3C_DEV_USB_HSOTG
274 The Samsung S3C64XX USB2.0 high-speed gadget controller
275 integrated into the S3C64XX series SoC.
278 tristate "Freescale i.MX1 USB Peripheral Controller"
282 Freescale's i.MX1 includes an integrated full speed
283 USB 1.1 device controller.
285 It has Six fixed-function endpoints, as well as endpoint
286 zero (for control transfers).
288 Say "y" to link the driver statically, or "m" to build a
289 dynamically linked module called "imx_udc" and force all
290 gadget drivers to also be dynamically linked.
293 tristate "S3C2410 USB Device Controller"
294 depends on ARCH_S3C24XX
296 Samsung's S3C2410 is an ARM-4 processor with an integrated
297 full speed USB 1.1 device controller. It has 4 configurable
298 endpoints, as well as endpoint zero (for control transfers).
300 This driver has been tested on the S3C2410, S3C2412, and
303 config USB_S3C2410_DEBUG
304 boolean "S3C2410 udc debug messages"
305 depends on USB_S3C2410
308 tristate "S3C2416, S3C2443 and S3C2450 USB Device Controller"
309 depends on ARCH_S3C24XX
311 Samsung's S3C2416, S3C2443 and S3C2450 is an ARM9 based SoC
312 integrated with dual speed USB 2.0 device controller. It has
313 8 endpoints, as well as endpoint zero.
315 This driver has been tested on S3C2416 and S3C2450 processors.
318 tristate "Marvell USB2.0 Device Controller"
319 depends on GENERIC_HARDIRQS
321 Marvell Socs (including PXA and MMP series) include a high speed
322 USB2.0 OTG controller, which can be configured as high speed or
323 full speed USB peripheral.
326 tristate "MARVELL PXA2128 USB 3.0 controller"
328 MARVELL PXA2128 Processor series include a super speed USB3.0 device
329 controller, which support super speed USB peripheral.
332 # Controllers available in both integrated and discrete versions
335 # musb builds in ../musb along with host support
336 config USB_GADGET_MUSB_HDRC
337 tristate "Inventra HDRC USB Peripheral (TI, ADI, ...)"
338 depends on USB_MUSB_HDRC
340 This OTG-capable silicon IP is used in dual designs including
341 the TI DaVinci, OMAP 243x, OMAP 343x, TUSB 6010, and ADI Blackfin
344 tristate "Renesas M66592 USB Peripheral Controller"
346 M66592 is a discrete USB peripheral controller chip that
347 supports both full and high speed USB 2.0 data transfers.
348 It has seven configurable endpoints, and endpoint zero.
350 Say "y" to link the driver statically, or "m" to build a
351 dynamically linked module called "m66592_udc" and force all
352 gadget drivers to also be dynamically linked.
355 # Controllers available only in discrete form (and all PCI controllers)
358 config USB_AMD5536UDC
359 tristate "AMD5536 UDC"
362 The AMD5536 UDC is part of the AMD Geode CS5536, an x86 southbridge.
363 It is a USB Highspeed DMA capable USB device controller. Beside ep0
364 it provides 4 IN and 4 OUT endpoints (bulk or interrupt type).
365 The UDC port supports OTG operation, and may be used as a host port
366 if it's not being used to implement peripheral or OTG roles.
368 Say "y" to link the driver statically, or "m" to build a
369 dynamically linked module called "amd5536udc" and force all
370 gadget drivers to also be dynamically linked.
373 tristate "Freescale QE/CPM USB Device Controller"
374 depends on FSL_SOC && (QUICC_ENGINE || CPM)
376 Some of Freescale PowerPC processors have a Full Speed
377 QE/CPM2 USB controller, which support device mode with 4
378 programmable endpoints. This driver supports the
379 controller in the MPC8360 and MPC8272, and should work with
380 controllers having QE or CPM2, given minor tweaks.
382 Set CONFIG_USB_GADGET to "m" to build this driver as a
383 dynamically linked module called "fsl_qe_udc".
386 tristate "PLX NET2272"
388 PLX NET2272 is a USB peripheral controller which supports
389 both full and high speed USB 2.0 data transfers.
391 It has three configurable endpoints, as well as endpoint zero
392 (for control transfer).
393 Say "y" to link the driver statically, or "m" to build a
394 dynamically linked module called "net2272" and force all
395 gadget drivers to also be dynamically linked.
397 config USB_NET2272_DMA
398 boolean "Support external DMA controller"
399 depends on USB_NET2272
401 The NET2272 part can optionally support an external DMA
402 controller, but your board has to have support in the
405 If unsure, say "N" here. The driver works fine in PIO mode.
408 tristate "NetChip 228x"
411 NetChip 2280 / 2282 is a PCI based USB peripheral controller which
412 supports both full and high speed USB 2.0 data transfers.
414 It has six configurable endpoints, as well as endpoint zero
415 (for control transfers) and several endpoints with dedicated
418 Say "y" to link the driver statically, or "m" to build a
419 dynamically linked module called "net2280" and force all
420 gadget drivers to also be dynamically linked.
423 tristate "Toshiba TC86C001 'Goku-S'"
426 The Toshiba TC86C001 is a PCI device which includes controllers
427 for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI).
429 The device controller has three configurable (bulk or interrupt)
430 endpoints, plus endpoint zero (for control transfers).
432 Say "y" to link the driver statically, or "m" to build a
433 dynamically linked module called "goku_udc" and to force all
434 gadget drivers to also be dynamically linked.
437 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7213/ML7831) UDC"
438 depends on PCI && GENERIC_HARDIRQS
440 This is a USB device driver for EG20T PCH.
441 EG20T PCH is the platform controller hub that is used in Intel's
442 general embedded platform. EG20T PCH has USB device interface.
443 Using this interface, it is able to access system devices connected
445 This driver enables USB device function.
446 USB device is a USB peripheral controller which
447 supports both full and high speed USB 2.0 data transfers.
448 This driver supports both control transfer and bulk transfer modes.
449 This driver dose not support interrupt transfer or isochronous
452 This driver also can be used for LAPIS Semiconductor's ML7213 which is
453 for IVI(In-Vehicle Infotainment) use.
454 ML7831 is for general purpose use.
455 ML7213/ML7831 is companion chip for Intel Atom E6xx series.
456 ML7213/ML7831 is completely compatible for Intel EG20T PCH.
459 # LAST -- dummy/emulated controller
463 tristate "Dummy HCD (DEVELOPMENT)"
464 depends on USB=y || (USB=m && USB_GADGET=m)
466 This host controller driver emulates USB, looping all data transfer
467 requests back to a USB "gadget driver" in the same host. The host
468 side is the master; the gadget side is the slave. Gadget drivers
469 can be high, full, or low speed; and they have access to endpoints
470 like those from NET2280, PXA2xx, or SA1100 hardware.
472 This may help in some stages of creating a driver to embed in a
473 Linux device, since it lets you debug several parts of the gadget
474 driver without its hardware or drivers being involved.
476 Since such a gadget side driver needs to interoperate with a host
477 side Linux-USB device driver, this may help to debug both sides
478 of a USB protocol stack.
480 Say "y" to link the driver statically, or "m" to build a
481 dynamically linked module called "dummy_hcd" and force all
482 gadget drivers to also be dynamically linked.
484 # NOTE: Please keep dummy_hcd LAST so that "real hardware" appears
485 # first and will be selected by default.
493 # composite based drivers
494 config USB_LIBCOMPOSITE
497 depends on USB_GADGET
515 tristate "USB Gadget Drivers"
518 A Linux "Gadget Driver" talks to the USB Peripheral Controller
519 driver through the abstract "gadget" API. Some other operating
520 systems call these "client" drivers, of which "class drivers"
521 are a subset (implementing a USB device class specification).
522 A gadget driver implements one or more USB functions using
523 the peripheral hardware.
525 Gadget drivers are hardware-neutral, or "platform independent",
526 except that they sometimes must understand quirks or limitations
527 of the particular controllers they work with. For example, when
528 a controller doesn't support alternate configurations or provide
529 enough of the right types of endpoints, the gadget driver might
530 not be able work with that controller, or might need to implement
531 a less common variant of a device class protocol.
533 # this first set of drivers all depend on bulk-capable hardware.
536 tristate "Gadget Zero (DEVELOPMENT)"
537 select USB_LIBCOMPOSITE
540 Gadget Zero is a two-configuration device. It either sinks and
541 sources bulk data; or it loops back a configurable number of
542 transfers. It also implements control requests, for "chapter 9"
543 conformance. The driver needs only two bulk-capable endpoints, so
544 it can work on top of most device-side usb controllers. It's
545 useful for testing, and is also a working example showing how
546 USB "gadget drivers" can be written.
548 Make this be the first driver you try using on top of any new
549 USB peripheral controller driver. Then you can use host-side
550 test software, like the "usbtest" driver, to put your hardware
551 and its driver through a basic set of functional tests.
553 Gadget Zero also works with the host-side "usb-skeleton" driver,
554 and with many kinds of host-side test software. You may need
555 to tweak product and vendor IDs before host software knows about
556 this device, and arrange to select an appropriate configuration.
558 Say "y" to link the driver statically, or "m" to build a
559 dynamically linked module called "g_zero".
561 config USB_ZERO_HNPTEST
562 boolean "HNP Test Device"
563 depends on USB_ZERO && USB_OTG
565 You can configure this device to enumerate using the device
566 identifiers of the USB-OTG test device. That means that when
567 this gadget connects to another OTG device, with this one using
568 the "B-Peripheral" role, that device will use HNP to let this
569 one serve as the USB host instead (in the "B-Host" role).
572 tristate "Audio Gadget"
574 select USB_LIBCOMPOSITE
577 This Gadget Audio driver is compatible with USB Audio Class
578 specification 2.0. It implements 1 AudioControl interface,
579 1 AudioStreaming Interface each for USB-OUT and USB-IN.
580 Number of channels, sample rate and sample size can be
581 specified as module parameters.
582 This driver doesn't expect any real Audio codec to be present
583 on the device - the audio streams are simply sinked to and
584 sourced from a virtual ALSA sound card created. The user-space
585 application may choose to do whatever it wants with the data
586 received from the USB Host and choose to provide whatever it
587 wants as audio data to the USB Host.
589 Say "y" to link the driver statically, or "m" to build a
590 dynamically linked module called "g_audio".
593 bool "UAC 1.0 (Legacy)"
596 If you instead want older UAC Spec-1.0 driver that also has audio
597 paths hardwired to the Audio codec chip on-board and doesn't work
601 tristate "Ethernet Gadget (with CDC Ethernet support)"
603 select USB_LIBCOMPOSITE
606 This driver implements Ethernet style communication, in one of
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.
614 - On hardware can't implement that protocol, a simple CDC subset
615 is used, placing fewer demands on USB.
617 - CDC Ethernet Emulation Model (EEM) is a newer standard that has
618 a simpler interface that can be used by more USB hardware.
620 RNDIS support is an additional option, more demanding than than
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.
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.
633 Say "y" to link the driver statically, or "m" to build a
634 dynamically linked module called "g_ether".
639 select USB_LIBCOMPOSITE
642 Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol,
643 and Microsoft provides redistributable binary RNDIS drivers for
644 older versions of Windows.
646 If you say "y" here, the Ethernet gadget driver will try to provide
647 a second device configuration, supporting RNDIS to talk to such
650 To make MS-Windows work with this, use Documentation/usb/linux.inf
651 as the "driver info file". For versions of MS-Windows older than
652 XP, you'll need to download drivers from Microsoft's website; a URL
653 is given in comments found in that info file.
656 bool "Ethernet Emulation Model (EEM) support"
658 select USB_LIBCOMPOSITE
661 CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM
662 and therefore can be supported by more hardware. Technically ECM and
663 EEM are designed for different applications. The ECM model extends
664 the network interface to the target (e.g. a USB cable modem), and the
665 EEM model is for mobile devices to communicate with hosts using
666 ethernet over USB. For Linux gadgets, however, the interface with
667 the host is the same (a usbX device), so the differences are minimal.
669 If you say "y" here, the Ethernet gadget driver will use the EEM
670 protocol rather than ECM. If unsure, say "n".
673 tristate "Network Control Model (NCM) support"
675 select USB_LIBCOMPOSITE
678 This driver implements USB CDC NCM subclass standard. NCM is
679 an advanced protocol for Ethernet encapsulation, allows grouping
680 of several ethernet frames into one USB transfer and different
681 alignment possibilities.
683 Say "y" to link the driver statically, or "m" to build a
684 dynamically linked module called "g_ncm".
687 tristate "Gadget Filesystem"
689 This driver provides a filesystem based API that lets user mode
690 programs implement a single-configuration USB device, including
691 endpoint I/O and control requests that don't relate to enumeration.
692 All endpoints, transfer speeds, and transfer types supported by
693 the hardware are available, through read() and write() calls.
695 Say "y" to link the driver statically, or "m" to build a
696 dynamically linked module called "gadgetfs".
698 config USB_FUNCTIONFS
699 tristate "Function Filesystem"
700 select USB_LIBCOMPOSITE
701 select USB_FUNCTIONFS_GENERIC if !(USB_FUNCTIONFS_ETH || USB_FUNCTIONFS_RNDIS)
703 The Function Filesystem (FunctionFS) lets one create USB
704 composite functions in user space in the same way GadgetFS
705 lets one create USB gadgets in user space. This allows creation
706 of composite gadgets such that some of the functions are
707 implemented in kernel space (for instance Ethernet, serial or
708 mass storage) and other are implemented in user space.
710 If you say "y" or "m" here you will be able what kind of
711 configurations the gadget will provide.
713 Say "y" to link the driver statically, or "m" to build
714 a dynamically linked module called "g_ffs".
716 config USB_FUNCTIONFS_ETH
717 bool "Include configuration with CDC ECM (Ethernet)"
718 depends on USB_FUNCTIONFS && NET
720 Include a configuration with CDC ECM function (Ethernet) and the
723 config USB_FUNCTIONFS_RNDIS
724 bool "Include configuration with RNDIS (Ethernet)"
725 depends on USB_FUNCTIONFS && NET
727 Include a configuration with RNDIS function (Ethernet) and the Filesystem.
729 config USB_FUNCTIONFS_GENERIC
730 bool "Include 'pure' configuration"
731 depends on USB_FUNCTIONFS
733 Include a configuration with the Function Filesystem alone with
734 no Ethernet interface.
736 config USB_MASS_STORAGE
737 tristate "Mass Storage Gadget"
739 select USB_LIBCOMPOSITE
741 The Mass Storage Gadget acts as a USB Mass Storage disk drive.
742 As its storage repository it can use a regular file or a block
743 device (in much the same way as the "loop" device driver),
744 specified as a module parameter or sysfs option.
746 This driver is a replacement for now removed File-backed
747 Storage Gadget (g_file_storage).
749 Say "y" to link the driver statically, or "m" to build
750 a dynamically linked module called "g_mass_storage".
752 config USB_GADGET_TARGET
753 tristate "USB Gadget Target Fabric Module"
754 depends on TARGET_CORE
755 select USB_LIBCOMPOSITE
757 This fabric is an USB gadget. Two USB protocols are supported that is
758 BBB or BOT (Bulk Only Transport) and UAS (USB Attached SCSI). BOT is
759 advertised on alternative interface 0 (primary) and UAS is on
760 alternative interface 1. Both protocols can work on USB2.0 and USB3.0.
761 UAS utilizes the USB 3.0 feature called streams support.
764 tristate "Serial Gadget (with CDC ACM and CDC OBEX support)"
769 select USB_LIBCOMPOSITE
771 The Serial Gadget talks to the Linux-USB generic serial driver.
772 This driver supports a CDC-ACM module option, which can be used
773 to interoperate with MS-Windows hosts or with the Linux-USB
776 This driver also supports a CDC-OBEX option. You will need a
777 user space OBEX server talking to /dev/ttyGS*, since the kernel
778 itself doesn't implement the OBEX protocol.
780 Say "y" to link the driver statically, or "m" to build a
781 dynamically linked module called "g_serial".
783 For more information, see Documentation/usb/gadget_serial.txt
784 which includes instructions and a "driver info file" needed to
785 make MS-Windows work with CDC ACM.
787 config USB_MIDI_GADGET
788 tristate "MIDI Gadget"
790 select USB_LIBCOMPOSITE
793 The MIDI Gadget acts as a USB Audio device, with one MIDI
794 input and one MIDI output. These MIDI jacks appear as
795 a sound "card" in the ALSA sound system. Other MIDI
796 connections can then be made on the gadget system, using
797 ALSA's aconnect utility etc.
799 Say "y" to link the driver statically, or "m" to build a
800 dynamically linked module called "g_midi".
803 tristate "Printer Gadget"
804 select USB_LIBCOMPOSITE
806 The Printer Gadget channels data between the USB host and a
807 userspace program driving the print engine. The user space
808 program reads and writes the device file /dev/g_printer to
809 receive or send printer data. It can use ioctl calls to
810 the device file to get or set printer status.
812 Say "y" to link the driver statically, or "m" to build a
813 dynamically linked module called "g_printer".
815 For more information, see Documentation/usb/gadget_printer.txt
816 which includes sample code for accessing the device file.
820 config USB_CDC_COMPOSITE
821 tristate "CDC Composite Device (Ethernet and ACM)"
823 select USB_LIBCOMPOSITE
827 This driver provides two functions in one configuration:
828 a CDC Ethernet (ECM) link, and a CDC ACM (serial port) link.
830 This driver requires four bulk and two interrupt endpoints,
831 plus the ability to handle altsettings. Not all peripheral
832 controllers are that capable.
834 Say "y" to link the driver statically, or "m" to build a
835 dynamically linked module.
838 tristate "Nokia composite gadget"
840 select USB_LIBCOMPOSITE
844 The Nokia composite gadget provides support for acm, obex
845 and phonet in only one composite gadget driver.
847 It's only really useful for N900 hardware. If you're building
848 a kernel for N900, say Y or M here. If unsure, say N.
851 tristate "CDC Composite Device (ACM and mass storage)"
853 select USB_LIBCOMPOSITE
857 This driver provides two functions in one configuration:
858 a mass storage, and a CDC ACM (serial port) link.
860 Say "y" to link the driver statically, or "m" to build a
861 dynamically linked module called "g_acm_ms".
864 tristate "Multifunction Composite Gadget"
865 depends on BLOCK && NET
866 select USB_G_MULTI_CDC if !USB_G_MULTI_RNDIS
867 select USB_LIBCOMPOSITE
871 The Multifunction Composite Gadget provides Ethernet (RNDIS
872 and/or CDC Ethernet), mass storage and ACM serial link
875 You will be asked to choose which of the two configurations is
876 to be available in the gadget. At least one configuration must
877 be chosen to make the gadget usable. Selecting more than one
878 configuration will prevent Windows from automatically detecting
879 the gadget as a composite gadget, so an INF file will be needed to
882 Say "y" to link the driver statically, or "m" to build a
883 dynamically linked module called "g_multi".
885 config USB_G_MULTI_RNDIS
886 bool "RNDIS + CDC Serial + Storage configuration"
887 depends on USB_G_MULTI
890 This option enables a configuration with RNDIS, CDC Serial and
891 Mass Storage functions available in the Multifunction Composite
892 Gadget. This is the configuration dedicated for Windows since RNDIS
893 is Microsoft's protocol.
897 config USB_G_MULTI_CDC
898 bool "CDC Ethernet + CDC Serial + Storage configuration"
899 depends on USB_G_MULTI
902 This option enables a configuration with CDC Ethernet (ECM), CDC
903 Serial and Mass Storage functions available in the Multifunction
911 tristate "HID Gadget"
912 select USB_LIBCOMPOSITE
914 The HID gadget driver provides generic emulation of USB
915 Human Interface Devices (HID).
917 For more information, see Documentation/usb/gadget_hid.txt which
918 includes sample code for accessing the device files.
920 Say "y" to link the driver statically, or "m" to build a
921 dynamically linked module called "g_hid".
923 # Standalone / single function gadgets
925 tristate "EHCI Debug Device Gadget"
927 select USB_LIBCOMPOSITE
929 This gadget emulates an EHCI Debug device. This is useful when you want
930 to interact with an EHCI Debug Port.
932 Say "y" to link the driver statically, or "m" to build a
933 dynamically linked module called "g_dbgp".
937 prompt "EHCI Debug Device mode"
938 default USB_G_DBGP_SERIAL
940 config USB_G_DBGP_PRINTK
941 depends on USB_G_DBGP
944 Directly printk() received data. No interaction.
946 config USB_G_DBGP_SERIAL
947 depends on USB_G_DBGP
951 Userland can interact using /dev/ttyGSxxx.
955 # put drivers that need isochronous transfer support (for audio
956 # or video class gadget drivers), or specific hardware, here.
958 tristate "USB Webcam Gadget"
960 select USB_LIBCOMPOSITE
961 select VIDEOBUF2_VMALLOC
963 The Webcam Gadget acts as a composite USB Audio and Video Class
964 device. It provides a userspace API to process UVC control requests
965 and stream video data to the host.
967 Say "y" to link the driver statically, or "m" to build a
968 dynamically linked module called "g_webcam".