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"
19 USB is a master/slave protocol, organized with one master
20 host (such as a PC) controlling up to 127 peripheral devices.
21 The USB hardware is asymmetric, which makes it easier to set up:
22 you can't connect a "to-the-host" connector to a peripheral.
24 Linux can run in the host, or in the peripheral. In both cases
25 you need a low level bus controller driver, and some software
26 talking to it. Peripheral controllers are often discrete silicon,
27 or are integrated with the CPU in a microcontroller. The more
28 familiar host side controllers have names like "EHCI", "OHCI",
29 or "UHCI", and are usually integrated into southbridges on PC
32 Enable this configuration option if you want to run Linux inside
33 a USB peripheral device. Configure one hardware driver for your
34 peripheral/device side bus controller, and a "gadget driver" for
35 your peripheral protocol. (If you use modular gadget drivers,
36 you may configure more than one.)
38 If in doubt, say "N" and don't enable these drivers; most people
39 don't have this kind of hardware (except maybe inside Linux PDAs).
41 For more information, see <http://www.linux-usb.org/gadget> and
42 the kernel DocBook documentation for this API.
46 config USB_GADGET_DEBUG
47 boolean "Debugging messages (DEVELOPMENT)"
48 depends on DEBUG_KERNEL
50 Many controller and gadget drivers will print some debugging
51 messages if you use this option to ask for those messages.
53 Avoid enabling these messages, even if you're actively
54 debugging such a driver. Many drivers will emit so many
55 messages that the driver timings are affected, which will
56 either create new failure modes or remove the one you're
57 trying to track down. Never enable these messages for a
60 config USB_GADGET_DEBUG_FILES
61 boolean "Debugging information files (DEVELOPMENT)"
64 Some of the drivers in the "gadget" framework can expose
65 debugging information in files such as /proc/driver/udc
66 (for a peripheral controller). The information in these
67 files may help when you're troubleshooting or bringing up a
68 driver on a new board. Enable these files by choosing "Y"
69 here. If in doubt, or to conserve kernel memory, say "N".
71 config USB_GADGET_DEBUG_FS
72 boolean "Debugging information files in debugfs (DEVELOPMENT)"
75 Some of the drivers in the "gadget" framework can expose
76 debugging information in files under /sys/kernel/debug/.
77 The information in these files may help when you're
78 troubleshooting or bringing up a driver on a new board.
79 Enable these files by choosing "Y" here. If in doubt, or
80 to conserve kernel memory, say "N".
82 config USB_GADGET_VBUS_DRAW
83 int "Maximum VBUS Power usage (2-500 mA)"
87 Some devices need to draw power from USB when they are
88 configured, perhaps to operate circuitry or to recharge
89 batteries. This is in addition to any local power supply,
90 such as an AC adapter or batteries.
92 Enter the maximum power your device draws through USB, in
93 milliAmperes. The permitted range of values is 2 - 500 mA;
94 0 mA would be legal, but can make some hosts misbehave.
96 This value will be used except for system-specific gadget
97 drivers that have more specific information.
99 config USB_GADGET_SELECTED
103 # USB Peripheral Controller Support
105 # The order here is alphabetical, except that integrated controllers go
106 # before discrete ones so they will be the initial/default value:
107 # - integrated/SOC controllers first
108 # - licensed IP used in both SOC and discrete versions
109 # - discrete ones (including all PCI-only controllers)
110 # - debug/dummy gadget+hcd is last.
113 prompt "USB Peripheral Controller"
114 depends on USB_GADGET
116 A USB device uses a controller to talk to its host.
117 Systems should have only one such upstream link.
118 Many controller drivers are platform-specific; these
119 often need board-specific hooks.
122 # Integrated controllers
125 config USB_GADGET_AT91
126 boolean "Atmel AT91 USB Device Port"
127 depends on ARCH_AT91 && !ARCH_AT91SAM9RL && !ARCH_AT91CAP9 && !ARCH_AT91SAM9G45
128 select USB_GADGET_SELECTED
130 Many Atmel AT91 processors (such as the AT91RM2000) have a
131 full speed USB Device Port with support for five configurable
132 endpoints (plus endpoint zero).
134 Say "y" to link the driver statically, or "m" to build a
135 dynamically linked module called "at91_udc" and force all
136 gadget drivers to also be dynamically linked.
140 depends on USB_GADGET_AT91
143 config USB_GADGET_ATMEL_USBA
145 select USB_GADGET_DUALSPEED
146 depends on AVR32 || ARCH_AT91CAP9 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
148 USBA is the integrated high-speed USB Device controller on
149 the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel.
151 config USB_ATMEL_USBA
153 depends on USB_GADGET_ATMEL_USBA
155 select USB_GADGET_SELECTED
157 config USB_GADGET_FSL_USB2
158 boolean "Freescale Highspeed USB DR Peripheral Controller"
159 depends on FSL_SOC || ARCH_MXC
160 select USB_GADGET_DUALSPEED
161 select USB_FSL_MPH_DR_OF if OF
163 Some of Freescale PowerPC processors have a High Speed
164 Dual-Role(DR) USB controller, which supports device mode.
166 The number of programmable endpoints is different through
169 Say "y" to link the driver statically, or "m" to build a
170 dynamically linked module called "fsl_usb2_udc" and force
171 all gadget drivers to also be dynamically linked.
175 depends on USB_GADGET_FSL_USB2
177 select USB_GADGET_SELECTED
179 config USB_GADGET_FUSB300
180 boolean "Faraday FUSB300 USB Peripheral Controller"
181 select USB_GADGET_DUALSPEED
183 Faraday usb device controller FUSB300 driver
187 depends on USB_GADGET_FUSB300
189 select USB_GADGET_SELECTED
191 config USB_GADGET_OMAP
192 boolean "OMAP USB Device Controller"
194 select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_H4_OTG
195 select USB_OTG_UTILS if ARCH_OMAP
197 Many Texas Instruments OMAP processors have flexible full
198 speed USB device controllers, with support for up to 30
199 endpoints (plus endpoint zero). This driver supports the
200 controller in the OMAP 1611, and should work with controllers
201 in other OMAP processors too, given minor tweaks.
203 Say "y" to link the driver statically, or "m" to build a
204 dynamically linked module called "omap_udc" and force all
205 gadget drivers to also be dynamically linked.
209 depends on USB_GADGET_OMAP
211 select USB_GADGET_SELECTED
213 config USB_GADGET_PXA25X
214 boolean "PXA 25x or IXP 4xx"
215 depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX
218 Intel's PXA 25x series XScale ARM-5TE processors include
219 an integrated full speed USB 1.1 device controller. The
220 controller in the IXP 4xx series is register-compatible.
222 It has fifteen fixed-function endpoints, as well as endpoint
223 zero (for control transfers).
225 Say "y" to link the driver statically, or "m" to build a
226 dynamically linked module called "pxa25x_udc" and force all
227 gadget drivers to also be dynamically linked.
231 depends on USB_GADGET_PXA25X
233 select USB_GADGET_SELECTED
235 # if there's only one gadget driver, using only two bulk endpoints,
236 # don't waste memory for the other endpoints
237 config USB_PXA25X_SMALL
238 depends on USB_GADGET_PXA25X
240 default n if USB_ETH_RNDIS
241 default y if USB_ZERO
243 default y if USB_G_SERIAL
245 config USB_GADGET_R8A66597
246 boolean "Renesas R8A66597 USB Peripheral Controller"
247 select USB_GADGET_DUALSPEED
249 R8A66597 is a discrete USB host and peripheral controller chip that
250 supports both full and high speed USB 2.0 data transfers.
251 It has nine configurable endpoints, and endpoint zero.
253 Say "y" to link the driver statically, or "m" to build a
254 dynamically linked module called "r8a66597_udc" and force all
255 gadget drivers to also be dynamically linked.
259 depends on USB_GADGET_R8A66597
261 select USB_GADGET_SELECTED
263 config USB_GADGET_PXA27X
265 depends on ARCH_PXA && (PXA27x || PXA3xx)
268 Intel's PXA 27x series XScale ARM v5TE processors include
269 an integrated full speed USB 1.1 device controller.
271 It has up to 23 endpoints, as well as endpoint zero (for
274 Say "y" to link the driver statically, or "m" to build a
275 dynamically linked module called "pxa27x_udc" and force all
276 gadget drivers to also be dynamically linked.
280 depends on USB_GADGET_PXA27X
282 select USB_GADGET_SELECTED
284 config USB_GADGET_S3C_HSOTG
285 boolean "S3C HS/OtG USB Device controller"
286 depends on S3C_DEV_USB_HSOTG
287 select USB_GADGET_S3C_HSOTG_PIO
288 select USB_GADGET_DUALSPEED
290 The Samsung S3C64XX USB2.0 high-speed gadget controller
291 integrated into the S3C64XX series SoC.
295 depends on USB_GADGET_S3C_HSOTG
297 select USB_GADGET_SELECTED
299 config USB_GADGET_IMX
300 boolean "Freescale IMX USB Peripheral Controller"
303 Freescale's IMX series include an integrated full speed
304 USB 1.1 device controller. The controller in the IMX series
305 is register-compatible.
307 It has Six fixed-function endpoints, as well as endpoint
308 zero (for control transfers).
310 Say "y" to link the driver statically, or "m" to build a
311 dynamically linked module called "imx_udc" and force all
312 gadget drivers to also be dynamically linked.
316 depends on USB_GADGET_IMX
318 select USB_GADGET_SELECTED
320 config USB_GADGET_S3C2410
321 boolean "S3C2410 USB Device Controller"
322 depends on ARCH_S3C2410
324 Samsung's S3C2410 is an ARM-4 processor with an integrated
325 full speed USB 1.1 device controller. It has 4 configurable
326 endpoints, as well as endpoint zero (for control transfers).
328 This driver has been tested on the S3C2410, S3C2412, and
333 depends on USB_GADGET_S3C2410
335 select USB_GADGET_SELECTED
337 config USB_S3C2410_DEBUG
338 boolean "S3C2410 udc debug messages"
339 depends on USB_GADGET_S3C2410
341 config USB_GADGET_PXA_U2O
342 boolean "PXA9xx Processor USB2.0 controller"
343 select USB_GADGET_DUALSPEED
345 PXA9xx Processor series include a high speed USB2.0 device
346 controller, which support high speed and full speed USB peripheral.
350 depends on USB_GADGET_PXA_U2O
352 select USB_GADGET_SELECTED
355 # Controllers available in both integrated and discrete versions
358 # musb builds in ../musb along with host support
359 config USB_GADGET_MUSB_HDRC
360 boolean "Inventra HDRC USB Peripheral (TI, ADI, ...)"
361 depends on USB_MUSB_HDRC && (USB_MUSB_PERIPHERAL || USB_MUSB_OTG)
362 select USB_GADGET_DUALSPEED
363 select USB_GADGET_SELECTED
365 This OTG-capable silicon IP is used in dual designs including
366 the TI DaVinci, OMAP 243x, OMAP 343x, TUSB 6010, and ADI Blackfin
368 config USB_GADGET_M66592
369 boolean "Renesas M66592 USB Peripheral Controller"
370 select USB_GADGET_DUALSPEED
372 M66592 is a discrete USB peripheral controller chip that
373 supports both full and high speed USB 2.0 data transfers.
374 It has seven configurable endpoints, and endpoint zero.
376 Say "y" to link the driver statically, or "m" to build a
377 dynamically linked module called "m66592_udc" and force all
378 gadget drivers to also be dynamically linked.
382 depends on USB_GADGET_M66592
384 select USB_GADGET_SELECTED
387 # Controllers available only in discrete form (and all PCI controllers)
390 config USB_GADGET_AMD5536UDC
391 boolean "AMD5536 UDC"
393 select USB_GADGET_DUALSPEED
395 The AMD5536 UDC is part of the AMD Geode CS5536, an x86 southbridge.
396 It is a USB Highspeed DMA capable USB device controller. Beside ep0
397 it provides 4 IN and 4 OUT endpoints (bulk or interrupt type).
398 The UDC port supports OTG operation, and may be used as a host port
399 if it's not being used to implement peripheral or OTG roles.
401 Say "y" to link the driver statically, or "m" to build a
402 dynamically linked module called "amd5536udc" and force all
403 gadget drivers to also be dynamically linked.
405 config USB_AMD5536UDC
407 depends on USB_GADGET_AMD5536UDC
409 select USB_GADGET_SELECTED
411 config USB_GADGET_FSL_QE
412 boolean "Freescale QE/CPM USB Device Controller"
413 depends on FSL_SOC && (QUICC_ENGINE || CPM)
415 Some of Freescale PowerPC processors have a Full Speed
416 QE/CPM2 USB controller, which support device mode with 4
417 programmable endpoints. This driver supports the
418 controller in the MPC8360 and MPC8272, and should work with
419 controllers having QE or CPM2, given minor tweaks.
421 Set CONFIG_USB_GADGET to "m" to build this driver as a
422 dynamically linked module called "fsl_qe_udc".
426 depends on USB_GADGET_FSL_QE
428 select USB_GADGET_SELECTED
430 config USB_GADGET_CI13XXX_PCI
431 boolean "MIPS USB CI13xxx PCI UDC"
433 select USB_GADGET_DUALSPEED
435 MIPS USB IP core family device controller
436 Currently it only supports IP part number CI13412
438 Say "y" to link the driver statically, or "m" to build a
439 dynamically linked module called "ci13xxx_udc" and force all
440 gadget drivers to also be dynamically linked.
442 config USB_CI13XXX_PCI
444 depends on USB_GADGET_CI13XXX_PCI
446 select USB_GADGET_SELECTED
448 config USB_GADGET_NET2280
449 boolean "NetChip 228x"
451 select USB_GADGET_DUALSPEED
453 NetChip 2280 / 2282 is a PCI based USB peripheral controller which
454 supports both full and high speed USB 2.0 data transfers.
456 It has six configurable endpoints, as well as endpoint zero
457 (for control transfers) and several endpoints with dedicated
460 Say "y" to link the driver statically, or "m" to build a
461 dynamically linked module called "net2280" and force all
462 gadget drivers to also be dynamically linked.
466 depends on USB_GADGET_NET2280
468 select USB_GADGET_SELECTED
470 config USB_GADGET_GOKU
471 boolean "Toshiba TC86C001 'Goku-S'"
474 The Toshiba TC86C001 is a PCI device which includes controllers
475 for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI).
477 The device controller has three configurable (bulk or interrupt)
478 endpoints, plus endpoint zero (for control transfers).
480 Say "y" to link the driver statically, or "m" to build a
481 dynamically linked module called "goku_udc" and to force all
482 gadget drivers to also be dynamically linked.
486 depends on USB_GADGET_GOKU
488 select USB_GADGET_SELECTED
490 config USB_GADGET_LANGWELL
491 boolean "Intel Langwell USB Device Controller"
493 select USB_GADGET_DUALSPEED
495 Intel Langwell USB Device Controller is a High-Speed USB
496 On-The-Go device controller.
498 The number of programmable endpoints is different through
501 Say "y" to link the driver statically, or "m" to build a
502 dynamically linked module called "langwell_udc" and force all
503 gadget drivers to also be dynamically linked.
507 depends on USB_GADGET_LANGWELL
509 select USB_GADGET_SELECTED
511 config USB_GADGET_EG20T
512 boolean "Intel EG20T PCH/OKI SEMICONDUCTOR ML7213 IOH UDC"
514 select USB_GADGET_DUALSPEED
516 This is a USB device driver for EG20T PCH.
517 EG20T PCH is the platform controller hub that is used in Intel's
518 general embedded platform. EG20T PCH has USB device interface.
519 Using this interface, it is able to access system devices connected
521 This driver enables USB device function.
522 USB device is a USB peripheral controller which
523 supports both full and high speed USB 2.0 data transfers.
524 This driver supports both control transfer and bulk transfer modes.
525 This driver dose not support interrupt transfer or isochronous
528 This driver also can be used for OKI SEMICONDUCTOR's ML7213 which is
529 for IVI(In-Vehicle Infotainment) use.
530 ML7213 is companion chip for Intel Atom E6xx series.
531 ML7213 is completely compatible for Intel EG20T PCH.
535 depends on USB_GADGET_EG20T
537 select USB_GADGET_SELECTED
539 config USB_GADGET_CI13XXX_MSM
540 boolean "MIPS USB CI13xxx for MSM"
542 select USB_GADGET_DUALSPEED
545 MSM SoC has chipidea USB controller. This driver uses
547 This driver depends on OTG driver for PHY initialization,
548 clock management, powering up VBUS, and power management.
549 This driver is not supported on boards like trout which
552 Say "y" to link the driver statically, or "m" to build a
553 dynamically linked module called "ci13xxx_msm" and force all
554 gadget drivers to also be dynamically linked.
556 config USB_CI13XXX_MSM
558 depends on USB_GADGET_CI13XXX_MSM
560 select USB_GADGET_SELECTED
563 # LAST -- dummy/emulated controller
566 config USB_GADGET_DUMMY_HCD
567 boolean "Dummy HCD (DEVELOPMENT)"
568 depends on USB=y || (USB=m && USB_GADGET=m)
569 select USB_GADGET_DUALSPEED
571 This host controller driver emulates USB, looping all data transfer
572 requests back to a USB "gadget driver" in the same host. The host
573 side is the master; the gadget side is the slave. Gadget drivers
574 can be high, full, or low speed; and they have access to endpoints
575 like those from NET2280, PXA2xx, or SA1100 hardware.
577 This may help in some stages of creating a driver to embed in a
578 Linux device, since it lets you debug several parts of the gadget
579 driver without its hardware or drivers being involved.
581 Since such a gadget side driver needs to interoperate with a host
582 side Linux-USB device driver, this may help to debug both sides
583 of a USB protocol stack.
585 Say "y" to link the driver statically, or "m" to build a
586 dynamically linked module called "dummy_hcd" and force all
587 gadget drivers to also be dynamically linked.
591 depends on USB_GADGET_DUMMY_HCD
593 select USB_GADGET_SELECTED
595 # NOTE: Please keep dummy_hcd LAST so that "real hardware" appears
596 # first and will be selected by default.
600 config USB_GADGET_DUALSPEED
602 depends on USB_GADGET
605 Means that gadget drivers should include extra descriptors
606 and code to handle dual-speed controllers.
612 tristate "USB Gadget Drivers"
613 depends on USB_GADGET && USB_GADGET_SELECTED
616 A Linux "Gadget Driver" talks to the USB Peripheral Controller
617 driver through the abstract "gadget" API. Some other operating
618 systems call these "client" drivers, of which "class drivers"
619 are a subset (implementing a USB device class specification).
620 A gadget driver implements one or more USB functions using
621 the peripheral hardware.
623 Gadget drivers are hardware-neutral, or "platform independent",
624 except that they sometimes must understand quirks or limitations
625 of the particular controllers they work with. For example, when
626 a controller doesn't support alternate configurations or provide
627 enough of the right types of endpoints, the gadget driver might
628 not be able work with that controller, or might need to implement
629 a less common variant of a device class protocol.
631 # this first set of drivers all depend on bulk-capable hardware.
634 tristate "Gadget Zero (DEVELOPMENT)"
636 Gadget Zero is a two-configuration device. It either sinks and
637 sources bulk data; or it loops back a configurable number of
638 transfers. It also implements control requests, for "chapter 9"
639 conformance. The driver needs only two bulk-capable endpoints, so
640 it can work on top of most device-side usb controllers. It's
641 useful for testing, and is also a working example showing how
642 USB "gadget drivers" can be written.
644 Make this be the first driver you try using on top of any new
645 USB peripheral controller driver. Then you can use host-side
646 test software, like the "usbtest" driver, to put your hardware
647 and its driver through a basic set of functional tests.
649 Gadget Zero also works with the host-side "usb-skeleton" driver,
650 and with many kinds of host-side test software. You may need
651 to tweak product and vendor IDs before host software knows about
652 this device, and arrange to select an appropriate configuration.
654 Say "y" to link the driver statically, or "m" to build a
655 dynamically linked module called "g_zero".
657 config USB_ZERO_HNPTEST
658 boolean "HNP Test Device"
659 depends on USB_ZERO && USB_OTG
661 You can configure this device to enumerate using the device
662 identifiers of the USB-OTG test device. That means that when
663 this gadget connects to another OTG device, with this one using
664 the "B-Peripheral" role, that device will use HNP to let this
665 one serve as the USB host instead (in the "B-Host" role).
668 tristate "Audio Gadget (EXPERIMENTAL)"
672 Gadget Audio is compatible with USB Audio Class specification 1.0.
673 It will include at least one AudioControl interface, zero or more
674 AudioStream interface and zero or more MIDIStream interface.
676 Gadget Audio will use on-board ALSA (CONFIG_SND) audio card to
677 playback or capture audio stream.
679 Say "y" to link the driver statically, or "m" to build a
680 dynamically linked module called "g_audio".
683 tristate "Ethernet Gadget (with CDC Ethernet support)"
687 This driver implements Ethernet style communication, in one of
690 - The "Communication Device Class" (CDC) Ethernet Control Model.
691 That protocol is often avoided with pure Ethernet adapters, in
692 favor of simpler vendor-specific hardware, but is widely
693 supported by firmware for smart network devices.
695 - On hardware can't implement that protocol, a simple CDC subset
696 is used, placing fewer demands on USB.
698 - CDC Ethernet Emulation Model (EEM) is a newer standard that has
699 a simpler interface that can be used by more USB hardware.
701 RNDIS support is an additional option, more demanding than than
704 Within the USB device, this gadget driver exposes a network device
705 "usbX", where X depends on what other networking devices you have.
706 Treat it like a two-node Ethernet link: host, and gadget.
708 The Linux-USB host-side "usbnet" driver interoperates with this
709 driver, so that deep I/O queues can be supported. On 2.4 kernels,
710 use "CDCEther" instead, if you're using the CDC option. That CDC
711 mode should also interoperate with standard CDC Ethernet class
712 drivers on other host operating systems.
714 Say "y" to link the driver statically, or "m" to build a
715 dynamically linked module called "g_ether".
722 Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol,
723 and Microsoft provides redistributable binary RNDIS drivers for
724 older versions of Windows.
726 If you say "y" here, the Ethernet gadget driver will try to provide
727 a second device configuration, supporting RNDIS to talk to such
730 To make MS-Windows work with this, use Documentation/usb/linux.inf
731 as the "driver info file". For versions of MS-Windows older than
732 XP, you'll need to download drivers from Microsoft's website; a URL
733 is given in comments found in that info file.
736 bool "Ethernet Emulation Model (EEM) support"
740 CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM
741 and therefore can be supported by more hardware. Technically ECM and
742 EEM are designed for different applications. The ECM model extends
743 the network interface to the target (e.g. a USB cable modem), and the
744 EEM model is for mobile devices to communicate with hosts using
745 ethernet over USB. For Linux gadgets, however, the interface with
746 the host is the same (a usbX device), so the differences are minimal.
748 If you say "y" here, the Ethernet gadget driver will use the EEM
749 protocol rather than ECM. If unsure, say "n".
752 tristate "Network Control Model (NCM) support"
756 This driver implements USB CDC NCM subclass standard. NCM is
757 an advanced protocol for Ethernet encapsulation, allows grouping
758 of several ethernet frames into one USB transfer and diffferent
759 alignment possibilities.
761 Say "y" to link the driver statically, or "m" to build a
762 dynamically linked module called "g_ncm".
765 tristate "Gadget Filesystem (EXPERIMENTAL)"
766 depends on EXPERIMENTAL
768 This driver provides a filesystem based API that lets user mode
769 programs implement a single-configuration USB device, including
770 endpoint I/O and control requests that don't relate to enumeration.
771 All endpoints, transfer speeds, and transfer types supported by
772 the hardware are available, through read() and write() calls.
774 Currently, this option is still labelled as EXPERIMENTAL because
775 of existing race conditions in the underlying in-kernel AIO core.
777 Say "y" to link the driver statically, or "m" to build a
778 dynamically linked module called "gadgetfs".
780 config USB_FUNCTIONFS
781 tristate "Function Filesystem (EXPERIMENTAL)"
782 depends on EXPERIMENTAL
783 select USB_FUNCTIONFS_GENERIC if !(USB_FUNCTIONFS_ETH || USB_FUNCTIONFS_RNDIS)
785 The Function Filesystem (FunctionFS) lets one create USB
786 composite functions in user space in the same way GadgetFS
787 lets one create USB gadgets in user space. This allows creation
788 of composite gadgets such that some of the functions are
789 implemented in kernel space (for instance Ethernet, serial or
790 mass storage) and other are implemented in user space.
792 If you say "y" or "m" here you will be able what kind of
793 configurations the gadget will provide.
795 Say "y" to link the driver statically, or "m" to build
796 a dynamically linked module called "g_ffs".
798 config USB_FUNCTIONFS_ETH
799 bool "Include configuration with CDC ECM (Ethernet)"
800 depends on USB_FUNCTIONFS && NET
802 Include a configuration with CDC ECM function (Ethernet) and the
805 config USB_FUNCTIONFS_RNDIS
806 bool "Include configuration with RNDIS (Ethernet)"
807 depends on USB_FUNCTIONFS && NET
809 Include a configuration with RNDIS function (Ethernet) and the Filesystem.
811 config USB_FUNCTIONFS_GENERIC
812 bool "Include 'pure' configuration"
813 depends on USB_FUNCTIONFS
815 Include a configuration with the Function Filesystem alone with
816 no Ethernet interface.
818 config USB_FILE_STORAGE
819 tristate "File-backed Storage Gadget"
822 The File-backed Storage Gadget acts as a USB Mass Storage
823 disk drive. As its storage repository it can use a regular
824 file or a block device (in much the same way as the "loop"
825 device driver), specified as a module parameter.
827 Say "y" to link the driver statically, or "m" to build a
828 dynamically linked module called "g_file_storage".
830 config USB_FILE_STORAGE_TEST
831 bool "File-backed Storage Gadget testing version"
832 depends on USB_FILE_STORAGE
835 Say "y" to generate the larger testing version of the
836 File-backed Storage Gadget, useful for probing the
837 behavior of USB Mass Storage hosts. Not needed for
840 config USB_MASS_STORAGE
841 tristate "Mass Storage Gadget"
844 The Mass Storage Gadget acts as a USB Mass Storage disk drive.
845 As its storage repository it can use a regular file or a block
846 device (in much the same way as the "loop" device driver),
847 specified as a module parameter or sysfs option.
849 This is heavily based on File-backed Storage Gadget and in most
850 cases you will want to use FSG instead. This gadget is mostly
851 here to test the functionality of the Mass Storage Function
852 which may be used with composite framework.
854 Say "y" to link the driver statically, or "m" to build
855 a dynamically linked module called "g_mass_storage". If unsure,
856 consider File-backed Storage Gadget.
859 tristate "Serial Gadget (with CDC ACM and CDC OBEX support)"
861 The Serial Gadget talks to the Linux-USB generic serial driver.
862 This driver supports a CDC-ACM module option, which can be used
863 to interoperate with MS-Windows hosts or with the Linux-USB
866 This driver also supports a CDC-OBEX option. You will need a
867 user space OBEX server talking to /dev/ttyGS*, since the kernel
868 itself doesn't implement the OBEX protocol.
870 Say "y" to link the driver statically, or "m" to build a
871 dynamically linked module called "g_serial".
873 For more information, see Documentation/usb/gadget_serial.txt
874 which includes instructions and a "driver info file" needed to
875 make MS-Windows work with CDC ACM.
877 config USB_MIDI_GADGET
878 tristate "MIDI Gadget (EXPERIMENTAL)"
879 depends on SND && EXPERIMENTAL
882 The MIDI Gadget acts as a USB Audio device, with one MIDI
883 input and one MIDI output. These MIDI jacks appear as
884 a sound "card" in the ALSA sound system. Other MIDI
885 connections can then be made on the gadget system, using
886 ALSA's aconnect utility etc.
888 Say "y" to link the driver statically, or "m" to build a
889 dynamically linked module called "g_midi".
892 tristate "Printer Gadget"
894 The Printer Gadget channels data between the USB host and a
895 userspace program driving the print engine. The user space
896 program reads and writes the device file /dev/g_printer to
897 receive or send printer data. It can use ioctl calls to
898 the device file to get or set printer status.
900 Say "y" to link the driver statically, or "m" to build a
901 dynamically linked module called "g_printer".
903 For more information, see Documentation/usb/gadget_printer.txt
904 which includes sample code for accessing the device file.
906 config USB_CDC_COMPOSITE
907 tristate "CDC Composite Device (Ethernet and ACM)"
910 This driver provides two functions in one configuration:
911 a CDC Ethernet (ECM) link, and a CDC ACM (serial port) link.
913 This driver requires four bulk and two interrupt endpoints,
914 plus the ability to handle altsettings. Not all peripheral
915 controllers are that capable.
917 Say "y" to link the driver statically, or "m" to build a
918 dynamically linked module.
921 tristate "Nokia composite gadget"
924 The Nokia composite gadget provides support for acm, obex
925 and phonet in only one composite gadget driver.
927 It's only really useful for N900 hardware. If you're building
928 a kernel for N900, say Y or M here. If unsure, say N.
931 tristate "Multifunction Composite Gadget (EXPERIMENTAL)"
932 depends on BLOCK && NET
933 select USB_G_MULTI_CDC if !USB_G_MULTI_RNDIS
935 The Multifunction Composite Gadget provides Ethernet (RNDIS
936 and/or CDC Ethernet), mass storage and ACM serial link
939 You will be asked to choose which of the two configurations is
940 to be available in the gadget. At least one configuration must
941 be chosen to make the gadget usable. Selecting more than one
942 configuration will prevent Windows from automatically detecting
943 the gadget as a composite gadget, so an INF file will be needed to
946 Say "y" to link the driver statically, or "m" to build a
947 dynamically linked module called "g_multi".
949 config USB_G_MULTI_RNDIS
950 bool "RNDIS + CDC Serial + Storage configuration"
951 depends on USB_G_MULTI
954 This option enables a configuration with RNDIS, CDC Serial and
955 Mass Storage functions available in the Multifunction Composite
956 Gadget. This is the configuration dedicated for Windows since RNDIS
957 is Microsoft's protocol.
961 config USB_G_MULTI_CDC
962 bool "CDC Ethernet + CDC Serial + Storage configuration"
963 depends on USB_G_MULTI
966 This option enables a configuration with CDC Ethernet (ECM), CDC
967 Serial and Mass Storage functions available in the Multifunction
973 tristate "HID Gadget"
975 The HID gadget driver provides generic emulation of USB
976 Human Interface Devices (HID).
978 For more information, see Documentation/usb/gadget_hid.txt which
979 includes sample code for accessing the device files.
981 Say "y" to link the driver statically, or "m" to build a
982 dynamically linked module called "g_hid".
985 tristate "EHCI Debug Device Gadget"
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
1008 Userland can interact using /dev/ttyGSxxx.
1012 # put drivers that need isochronous transfer support (for audio
1013 # or video class gadget drivers), or specific hardware, here.
1015 tristate "USB Webcam Gadget"
1016 depends on VIDEO_DEV
1018 The Webcam Gadget acts as a composite USB Audio and Video Class
1019 device. It provides a userspace API to process UVC control requests
1020 and stream video data to the host.
1022 Say "y" to link the driver statically, or "m" to build a
1023 dynamically linked module called "g_webcam".