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.
190 tristate "Faraday FUSB300 USB Peripheral Controller"
191 depends on !PHYS_ADDR_T_64BIT
193 Faraday usb device controller FUSB300 driver
196 tristate "OMAP USB Device Controller"
197 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
338 tristate "Renesas M66592 USB Peripheral Controller"
340 M66592 is a discrete USB peripheral controller chip that
341 supports both full and high speed USB 2.0 data transfers.
342 It has seven configurable endpoints, and endpoint zero.
344 Say "y" to link the driver statically, or "m" to build a
345 dynamically linked module called "m66592_udc" and force all
346 gadget drivers to also be dynamically linked.
349 # Controllers available only in discrete form (and all PCI controllers)
352 config USB_AMD5536UDC
353 tristate "AMD5536 UDC"
356 The AMD5536 UDC is part of the AMD Geode CS5536, an x86 southbridge.
357 It is a USB Highspeed DMA capable USB device controller. Beside ep0
358 it provides 4 IN and 4 OUT endpoints (bulk or interrupt type).
359 The UDC port supports OTG operation, and may be used as a host port
360 if it's not being used to implement peripheral or OTG roles.
362 Say "y" to link the driver statically, or "m" to build a
363 dynamically linked module called "amd5536udc" and force all
364 gadget drivers to also be dynamically linked.
367 tristate "Freescale QE/CPM USB Device Controller"
368 depends on FSL_SOC && (QUICC_ENGINE || CPM)
370 Some of Freescale PowerPC processors have a Full Speed
371 QE/CPM2 USB controller, which support device mode with 4
372 programmable endpoints. This driver supports the
373 controller in the MPC8360 and MPC8272, and should work with
374 controllers having QE or CPM2, given minor tweaks.
376 Set CONFIG_USB_GADGET to "m" to build this driver as a
377 dynamically linked module called "fsl_qe_udc".
380 tristate "PLX NET2272"
382 PLX NET2272 is a USB peripheral controller which supports
383 both full and high speed USB 2.0 data transfers.
385 It has three configurable endpoints, as well as endpoint zero
386 (for control transfer).
387 Say "y" to link the driver statically, or "m" to build a
388 dynamically linked module called "net2272" and force all
389 gadget drivers to also be dynamically linked.
391 config USB_NET2272_DMA
392 boolean "Support external DMA controller"
393 depends on USB_NET2272
395 The NET2272 part can optionally support an external DMA
396 controller, but your board has to have support in the
399 If unsure, say "N" here. The driver works fine in PIO mode.
402 tristate "NetChip 228x"
405 NetChip 2280 / 2282 is a PCI based USB peripheral controller which
406 supports both full and high speed USB 2.0 data transfers.
408 It has six configurable endpoints, as well as endpoint zero
409 (for control transfers) and several endpoints with dedicated
412 Say "y" to link the driver statically, or "m" to build a
413 dynamically linked module called "net2280" and force all
414 gadget drivers to also be dynamically linked.
417 tristate "Toshiba TC86C001 'Goku-S'"
420 The Toshiba TC86C001 is a PCI device which includes controllers
421 for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI).
423 The device controller has three configurable (bulk or interrupt)
424 endpoints, plus endpoint zero (for control transfers).
426 Say "y" to link the driver statically, or "m" to build a
427 dynamically linked module called "goku_udc" and to force all
428 gadget drivers to also be dynamically linked.
431 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7213/ML7831) UDC"
432 depends on PCI && GENERIC_HARDIRQS
434 This is a USB device driver for EG20T PCH.
435 EG20T PCH is the platform controller hub that is used in Intel's
436 general embedded platform. EG20T PCH has USB device interface.
437 Using this interface, it is able to access system devices connected
439 This driver enables USB device function.
440 USB device is a USB peripheral controller which
441 supports both full and high speed USB 2.0 data transfers.
442 This driver supports both control transfer and bulk transfer modes.
443 This driver dose not support interrupt transfer or isochronous
446 This driver also can be used for LAPIS Semiconductor's ML7213 which is
447 for IVI(In-Vehicle Infotainment) use.
448 ML7831 is for general purpose use.
449 ML7213/ML7831 is companion chip for Intel Atom E6xx series.
450 ML7213/ML7831 is completely compatible for Intel EG20T PCH.
453 # LAST -- dummy/emulated controller
457 tristate "Dummy HCD (DEVELOPMENT)"
458 depends on USB=y || (USB=m && USB_GADGET=m)
460 This host controller driver emulates USB, looping all data transfer
461 requests back to a USB "gadget driver" in the same host. The host
462 side is the master; the gadget side is the slave. Gadget drivers
463 can be high, full, or low speed; and they have access to endpoints
464 like those from NET2280, PXA2xx, or SA1100 hardware.
466 This may help in some stages of creating a driver to embed in a
467 Linux device, since it lets you debug several parts of the gadget
468 driver without its hardware or drivers being involved.
470 Since such a gadget side driver needs to interoperate with a host
471 side Linux-USB device driver, this may help to debug both sides
472 of a USB protocol stack.
474 Say "y" to link the driver statically, or "m" to build a
475 dynamically linked module called "dummy_hcd" and force all
476 gadget drivers to also be dynamically linked.
478 # NOTE: Please keep dummy_hcd LAST so that "real hardware" appears
479 # first and will be selected by default.
487 # composite based drivers
488 config USB_LIBCOMPOSITE
491 depends on USB_GADGET
530 tristate "USB Gadget Drivers"
533 A Linux "Gadget Driver" talks to the USB Peripheral Controller
534 driver through the abstract "gadget" API. Some other operating
535 systems call these "client" drivers, of which "class drivers"
536 are a subset (implementing a USB device class specification).
537 A gadget driver implements one or more USB functions using
538 the peripheral hardware.
540 Gadget drivers are hardware-neutral, or "platform independent",
541 except that they sometimes must understand quirks or limitations
542 of the particular controllers they work with. For example, when
543 a controller doesn't support alternate configurations or provide
544 enough of the right types of endpoints, the gadget driver might
545 not be able work with that controller, or might need to implement
546 a less common variant of a device class protocol.
548 # this first set of drivers all depend on bulk-capable hardware.
550 config USB_CONFIGFS_EEM
551 bool "Ethernet Emulation Model (EEM)"
552 depends on USB_CONFIGFS
557 CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM
558 and therefore can be supported by more hardware. Technically ECM and
559 EEM are designed for different applications. The ECM model extends
560 the network interface to the target (e.g. a USB cable modem), and the
561 EEM model is for mobile devices to communicate with hosts using
562 ethernet over USB. For Linux gadgets, however, the interface with
563 the host is the same (a usbX device), so the differences are minimal.
565 config USB_CONFIGFS_PHONET
566 boolean "Phonet protocol"
567 depends on USB_CONFIGFS
573 The Phonet protocol implementation for USB device.
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
649 This driver implements Ethernet style communication, in one of
652 - The "Communication Device Class" (CDC) Ethernet Control Model.
653 That protocol is often avoided with pure Ethernet adapters, in
654 favor of simpler vendor-specific hardware, but is widely
655 supported by firmware for smart network devices.
657 - On hardware can't implement that protocol, a simple CDC subset
658 is used, placing fewer demands on USB.
660 - CDC Ethernet Emulation Model (EEM) is a newer standard that has
661 a simpler interface that can be used by more USB hardware.
663 RNDIS support is an additional option, more demanding than than
666 Within the USB device, this gadget driver exposes a network device
667 "usbX", where X depends on what other networking devices you have.
668 Treat it like a two-node Ethernet link: host, and gadget.
670 The Linux-USB host-side "usbnet" driver interoperates with this
671 driver, so that deep I/O queues can be supported. On 2.4 kernels,
672 use "CDCEther" instead, if you're using the CDC option. That CDC
673 mode should also interoperate with standard CDC Ethernet class
674 drivers on other host operating systems.
676 Say "y" to link the driver statically, or "m" to build a
677 dynamically linked module called "g_ether".
682 select USB_LIBCOMPOSITE
685 Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol,
686 and Microsoft provides redistributable binary RNDIS drivers for
687 older versions of Windows.
689 If you say "y" here, the Ethernet gadget driver will try to provide
690 a second device configuration, supporting RNDIS to talk to such
693 To make MS-Windows work with this, use Documentation/usb/linux.inf
694 as the "driver info file". For versions of MS-Windows older than
695 XP, you'll need to download drivers from Microsoft's website; a URL
696 is given in comments found in that info file.
699 bool "Ethernet Emulation Model (EEM) support"
701 select USB_LIBCOMPOSITE
705 CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM
706 and therefore can be supported by more hardware. Technically ECM and
707 EEM are designed for different applications. The ECM model extends
708 the network interface to the target (e.g. a USB cable modem), and the
709 EEM model is for mobile devices to communicate with hosts using
710 ethernet over USB. For Linux gadgets, however, the interface with
711 the host is the same (a usbX device), so the differences are minimal.
713 If you say "y" here, the Ethernet gadget driver will use the EEM
714 protocol rather than ECM. If unsure, say "n".
717 tristate "Network Control Model (NCM) support"
719 select USB_LIBCOMPOSITE
724 This driver implements USB CDC NCM subclass standard. NCM is
725 an advanced protocol for Ethernet encapsulation, allows grouping
726 of several ethernet frames into one USB transfer and different
727 alignment possibilities.
729 Say "y" to link the driver statically, or "m" to build a
730 dynamically linked module called "g_ncm".
733 tristate "Gadget Filesystem"
735 This driver provides a filesystem based API that lets user mode
736 programs implement a single-configuration USB device, including
737 endpoint I/O and control requests that don't relate to enumeration.
738 All endpoints, transfer speeds, and transfer types supported by
739 the hardware are available, through read() and write() calls.
741 Say "y" to link the driver statically, or "m" to build a
742 dynamically linked module called "gadgetfs".
744 config USB_FUNCTIONFS
745 tristate "Function Filesystem"
746 select USB_LIBCOMPOSITE
747 select USB_FUNCTIONFS_GENERIC if !(USB_FUNCTIONFS_ETH || USB_FUNCTIONFS_RNDIS)
749 The Function Filesystem (FunctionFS) lets one create USB
750 composite functions in user space in the same way GadgetFS
751 lets one create USB gadgets in user space. This allows creation
752 of composite gadgets such that some of the functions are
753 implemented in kernel space (for instance Ethernet, serial or
754 mass storage) and other are implemented in user space.
756 If you say "y" or "m" here you will be able what kind of
757 configurations the gadget will provide.
759 Say "y" to link the driver statically, or "m" to build
760 a dynamically linked module called "g_ffs".
762 config USB_FUNCTIONFS_ETH
763 bool "Include configuration with CDC ECM (Ethernet)"
764 depends on USB_FUNCTIONFS && NET
767 Include a configuration with CDC ECM function (Ethernet) and the
770 config USB_FUNCTIONFS_RNDIS
771 bool "Include configuration with RNDIS (Ethernet)"
772 depends on USB_FUNCTIONFS && NET
776 Include a configuration with RNDIS function (Ethernet) and the Filesystem.
778 config USB_FUNCTIONFS_GENERIC
779 bool "Include 'pure' configuration"
780 depends on USB_FUNCTIONFS
782 Include a configuration with the Function Filesystem alone with
783 no Ethernet interface.
785 config USB_MASS_STORAGE
786 tristate "Mass Storage Gadget"
788 select USB_LIBCOMPOSITE
790 The Mass Storage Gadget acts as a USB Mass Storage disk drive.
791 As its storage repository it can use a regular file or a block
792 device (in much the same way as the "loop" device driver),
793 specified as a module parameter or sysfs option.
795 This driver is a replacement for now removed File-backed
796 Storage Gadget (g_file_storage).
798 Say "y" to link the driver statically, or "m" to build
799 a dynamically linked module called "g_mass_storage".
801 config USB_GADGET_TARGET
802 tristate "USB Gadget Target Fabric Module"
803 depends on TARGET_CORE
804 select USB_LIBCOMPOSITE
806 This fabric is an USB gadget. Two USB protocols are supported that is
807 BBB or BOT (Bulk Only Transport) and UAS (USB Attached SCSI). BOT is
808 advertised on alternative interface 0 (primary) and UAS is on
809 alternative interface 1. Both protocols can work on USB2.0 and USB3.0.
810 UAS utilizes the USB 3.0 feature called streams support.
813 tristate "Serial Gadget (with CDC ACM and CDC OBEX support)"
819 select USB_LIBCOMPOSITE
821 The Serial Gadget talks to the Linux-USB generic serial driver.
822 This driver supports a CDC-ACM module option, which can be used
823 to interoperate with MS-Windows hosts or with the Linux-USB
826 This driver also supports a CDC-OBEX option. You will need a
827 user space OBEX server talking to /dev/ttyGS*, since the kernel
828 itself doesn't implement the OBEX protocol.
830 Say "y" to link the driver statically, or "m" to build a
831 dynamically linked module called "g_serial".
833 For more information, see Documentation/usb/gadget_serial.txt
834 which includes instructions and a "driver info file" needed to
835 make MS-Windows work with CDC ACM.
837 config USB_MIDI_GADGET
838 tristate "MIDI Gadget"
840 select USB_LIBCOMPOSITE
843 The MIDI Gadget acts as a USB Audio device, with one MIDI
844 input and one MIDI output. These MIDI jacks appear as
845 a sound "card" in the ALSA sound system. Other MIDI
846 connections can then be made on the gadget system, using
847 ALSA's aconnect utility etc.
849 Say "y" to link the driver statically, or "m" to build a
850 dynamically linked module called "g_midi".
853 tristate "Printer Gadget"
854 select USB_LIBCOMPOSITE
856 The Printer Gadget channels data between the USB host and a
857 userspace program driving the print engine. The user space
858 program reads and writes the device file /dev/g_printer to
859 receive or send printer data. It can use ioctl calls to
860 the device file to get or set printer status.
862 Say "y" to link the driver statically, or "m" to build a
863 dynamically linked module called "g_printer".
865 For more information, see Documentation/usb/gadget_printer.txt
866 which includes sample code for accessing the device file.
870 config USB_CDC_COMPOSITE
871 tristate "CDC Composite Device (Ethernet and ACM)"
873 select USB_LIBCOMPOSITE
879 This driver provides two functions in one configuration:
880 a CDC Ethernet (ECM) link, and a CDC ACM (serial port) link.
882 This driver requires four bulk and two interrupt endpoints,
883 plus the ability to handle altsettings. Not all peripheral
884 controllers are that capable.
886 Say "y" to link the driver statically, or "m" to build a
887 dynamically linked module.
890 tristate "Nokia composite gadget"
892 select USB_LIBCOMPOSITE
900 The Nokia composite gadget provides support for acm, obex
901 and phonet in only one composite gadget driver.
903 It's only really useful for N900 hardware. If you're building
904 a kernel for N900, say Y or M here. If unsure, say N.
907 tristate "CDC Composite Device (ACM and mass storage)"
909 select USB_LIBCOMPOSITE
913 This driver provides two functions in one configuration:
914 a mass storage, and a CDC ACM (serial port) link.
916 Say "y" to link the driver statically, or "m" to build a
917 dynamically linked module called "g_acm_ms".
920 tristate "Multifunction Composite Gadget"
921 depends on BLOCK && NET
922 select USB_G_MULTI_CDC if !USB_G_MULTI_RNDIS
923 select USB_LIBCOMPOSITE
929 The Multifunction Composite Gadget provides Ethernet (RNDIS
930 and/or CDC Ethernet), mass storage and ACM serial link
933 You will be asked to choose which of the two configurations is
934 to be available in the gadget. At least one configuration must
935 be chosen to make the gadget usable. Selecting more than one
936 configuration will prevent Windows from automatically detecting
937 the gadget as a composite gadget, so an INF file will be needed to
940 Say "y" to link the driver statically, or "m" to build a
941 dynamically linked module called "g_multi".
943 config USB_G_MULTI_RNDIS
944 bool "RNDIS + CDC Serial + Storage configuration"
945 depends on USB_G_MULTI
948 This option enables a configuration with RNDIS, CDC Serial and
949 Mass Storage functions available in the Multifunction Composite
950 Gadget. This is the configuration dedicated for Windows since RNDIS
951 is Microsoft's protocol.
955 config USB_G_MULTI_CDC
956 bool "CDC Ethernet + CDC Serial + Storage configuration"
957 depends on USB_G_MULTI
960 This option enables a configuration with CDC Ethernet (ECM), CDC
961 Serial and Mass Storage functions available in the Multifunction
969 tristate "HID Gadget"
970 select USB_LIBCOMPOSITE
972 The HID gadget driver provides generic emulation of USB
973 Human Interface Devices (HID).
975 For more information, see Documentation/usb/gadget_hid.txt which
976 includes sample code for accessing the device files.
978 Say "y" to link the driver statically, or "m" to build a
979 dynamically linked module called "g_hid".
981 # Standalone / single function gadgets
983 tristate "EHCI Debug Device Gadget"
985 select USB_LIBCOMPOSITE
987 This gadget emulates an EHCI Debug device. This is useful when you want
988 to interact with an EHCI Debug Port.
990 Say "y" to link the driver statically, or "m" to build a
991 dynamically linked module called "g_dbgp".
995 prompt "EHCI Debug Device mode"
996 default USB_G_DBGP_SERIAL
998 config USB_G_DBGP_PRINTK
999 depends on USB_G_DBGP
1002 Directly printk() received data. No interaction.
1004 config USB_G_DBGP_SERIAL
1005 depends on USB_G_DBGP
1009 Userland can interact using /dev/ttyGSxxx.
1013 # put drivers that need isochronous transfer support (for audio
1014 # or video class gadget drivers), or specific hardware, here.
1016 tristate "USB Webcam Gadget"
1017 depends on VIDEO_DEV
1018 select USB_LIBCOMPOSITE
1019 select VIDEOBUF2_VMALLOC
1021 The Webcam Gadget acts as a composite USB Audio and Video Class
1022 device. It provides a userspace API to process UVC control requests
1023 and stream video data to the host.
1025 Say "y" to link the driver statically, or "m" to build a
1026 dynamically linked module called "g_webcam".