drivers/usb/gadget/Kconfig

   1 #
   2 # USB Gadget support on a system involves
   3 #    (a) a peripheral controller, and
   4 #    (b) the gadget driver using it.
   5 #
   6 # NOTE:  Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
   7 #
   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.
  11 #
  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).
  14 #
  15
  16 menuconfig USB_GADGET
  17         tristate "USB Gadget Support"
  18         select NLS
  19         help
  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.
  24
  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
  31            motherboards.
  32
  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.)
  38
  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).
  41
  42            For more information, see <http://www.linux-usb.org/gadget> and
  43            the kernel DocBook documentation for this API.
  44
  45 if USB_GADGET
  46
  47 config USB_GADGET_DEBUG
  48         boolean "Debugging messages (DEVELOPMENT)"
  49         depends on DEBUG_KERNEL
  50         help
  51            Many controller and gadget drivers will print some debugging
  52            messages if you use this option to ask for those messages.
  53
  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
  59            production build.
  60
  61 config USB_GADGET_DEBUG_FILES
  62         boolean "Debugging information files (DEVELOPMENT)"
  63         depends on PROC_FS
  64         help
  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".
  71
  72 config USB_GADGET_DEBUG_FS
  73         boolean "Debugging information files in debugfs (DEVELOPMENT)"
  74         depends on DEBUG_FS
  75         help
  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".
  82
  83 config USB_GADGET_VBUS_DRAW
  84         int "Maximum VBUS Power usage (2-500 mA)"
  85         range 2 500
  86         default 2
  87         help
  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.
  92
  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.
  96
  97            This value will be used except for system-specific gadget
  98            drivers that have more specific information.
  99
 100 config USB_GADGET_STORAGE_NUM_BUFFERS
 101         int "Number of storage pipeline buffers"
 102         range 2 4
 103         default 2
 104         help
 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.
 114            If unsure, say 2.
 115
 116 #
 117 # USB Peripheral Controller Support
 118 #
 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.
 125 #
 126 menu "USB Peripheral Controller"
 127
 128 #
 129 # Integrated controllers
 130 #
 131
 132 config USB_AT91
 133         tristate "Atmel AT91 USB Device Port"
 134         depends on ARCH_AT91
 135         help
 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).
 139
 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.
 143
 144 config USB_LPC32XX
 145         tristate "LPC32XX USB Peripheral Controller"
 146         depends on ARCH_LPC32XX
 147         select USB_ISP1301
 148         help
 149            This option selects the USB device controller in the LPC32xx SoC.
 150
 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.
 154
 155 config USB_ATMEL_USBA
 156         tristate "Atmel USBA"
 157         depends on AVR32 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
 158         help
 159           USBA is the integrated high-speed USB Device controller on
 160           the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel.
 161
 162 config USB_BCM63XX_UDC
 163         tristate "Broadcom BCM63xx Peripheral Controller"
 164         depends on BCM63XX
 165         help
 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).
 169
 170            Say "y" to link the driver statically, or "m" to build a
 171            dynamically linked module called "bcm63xx_udc".
 172
 173 config USB_FSL_USB2
 174         tristate "Freescale Highspeed USB DR Peripheral Controller"
 175         depends on FSL_SOC || ARCH_MXC
 176         select USB_FSL_MPH_DR_OF if OF
 177         help
 178            Some of Freescale PowerPC and i.MX processors have a High Speed
 179            Dual-Role(DR) USB controller, which supports device mode.
 180
 181            The number of programmable endpoints is different through
 182            SOC revisions.
 183
 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.
 187
 188 config USB_FUSB300
 189         tristate "Faraday FUSB300 USB Peripheral Controller"
 190         depends on !PHYS_ADDR_T_64BIT
 191         help
 192            Faraday usb device controller FUSB300 driver
 193
 194 config USB_OMAP
 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
 198         select USB_OTG_UTILS if ARCH_OMAP
 199         help
 200            Many Texas Instruments OMAP processors have flexible full
 201            speed USB device controllers, with support for up to 30
 202            endpoints (plus endpoint zero).  This driver supports the
 203            controller in the OMAP 1611, and should work with controllers
 204            in other OMAP processors too, given minor tweaks.
 205
 206            Say "y" to link the driver statically, or "m" to build a
 207            dynamically linked module called "omap_udc" and force all
 208            gadget drivers to also be dynamically linked.
 209
 210 config USB_PXA25X
 211         tristate "PXA 25x or IXP 4xx"
 212         depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX
 213         select USB_OTG_UTILS
 214         help
 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.
 218
 219            It has fifteen fixed-function endpoints, as well as endpoint
 220            zero (for control transfers).
 221
 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.
 225
 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
 230         bool
 231         default n if USB_ETH_RNDIS
 232         default y if USB_ZERO
 233         default y if USB_ETH
 234         default y if USB_G_SERIAL
 235
 236 config USB_R8A66597
 237         tristate "Renesas R8A66597 USB Peripheral Controller"
 238         help
 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.
 242
 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.
 246
 247 config USB_RENESAS_USBHS_UDC
 248         tristate 'Renesas USBHS controller'
 249         depends on USB_RENESAS_USBHS
 250         help
 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.
 254
 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.
 258
 259 config USB_PXA27X
 260         tristate "PXA 27x"
 261         depends on ARCH_PXA && (PXA27x || PXA3xx)
 262         select USB_OTG_UTILS
 263         help
 264            Intel's PXA 27x series XScale ARM v5TE processors include
 265            an integrated full speed USB 1.1 device controller.
 266
 267            It has up to 23 endpoints, as well as endpoint zero (for
 268            control transfers).
 269
 270            Say "y" to link the driver statically, or "m" to build a
 271            dynamically linked module called "pxa27x_udc" and force all
 272            gadget drivers to also be dynamically linked.
 273
 274 config USB_S3C_HSOTG
 275         tristate "S3C HS/OtG USB Device controller"
 276         depends on S3C_DEV_USB_HSOTG
 277         help
 278           The Samsung S3C64XX USB2.0 high-speed gadget controller
 279           integrated into the S3C64XX series SoC.
 280
 281 config USB_IMX
 282         tristate "Freescale i.MX1 USB Peripheral Controller"
 283         depends on ARCH_MXC
 284         help
 285            Freescale's i.MX1 includes an integrated full speed
 286            USB 1.1 device controller.
 287
 288            It has Six fixed-function endpoints, as well as endpoint
 289            zero (for control transfers).
 290
 291            Say "y" to link the driver statically, or "m" to build a
 292            dynamically linked module called "imx_udc" and force all
 293            gadget drivers to also be dynamically linked.
 294
 295 config USB_S3C2410
 296         tristate "S3C2410 USB Device Controller"
 297         depends on ARCH_S3C24XX
 298         help
 299           Samsung's S3C2410 is an ARM-4 processor with an integrated
 300           full speed USB 1.1 device controller.  It has 4 configurable
 301           endpoints, as well as endpoint zero (for control transfers).
 302
 303           This driver has been tested on the S3C2410, S3C2412, and
 304           S3C2440 processors.
 305
 306 config USB_S3C2410_DEBUG
 307         boolean "S3C2410 udc debug messages"
 308         depends on USB_S3C2410
 309
 310 config USB_S3C_HSUDC
 311         tristate "S3C2416, S3C2443 and S3C2450 USB Device Controller"
 312         depends on ARCH_S3C24XX
 313         help
 314           Samsung's S3C2416, S3C2443 and S3C2450 is an ARM9 based SoC
 315           integrated with dual speed USB 2.0 device controller. It has
 316           8 endpoints, as well as endpoint zero.
 317
 318           This driver has been tested on S3C2416 and S3C2450 processors.
 319
 320 config USB_MV_UDC
 321         tristate "Marvell USB2.0 Device Controller"
 322         help
 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.
 326
 327 config USB_MV_U3D
 328         tristate "MARVELL PXA2128 USB 3.0 controller"
 329         depends on CPU_MMP3
 330         select USB_GADGET_DUALSPEED
 331         select USB_GADGET_SUPERSPEED
 332         help
 333           MARVELL PXA2128 Processor series include a super speed USB3.0 device
 334           controller, which support super speed USB peripheral.
 335
 336 #
 337 # Controllers available in both integrated and discrete versions
 338 #
 339
 340 # musb builds in ../musb along with host support
 341 config USB_GADGET_MUSB_HDRC
 342         tristate "Inventra HDRC USB Peripheral (TI, ADI, ...)"
 343         depends on USB_MUSB_HDRC
 344         help
 345           This OTG-capable silicon IP is used in dual designs including
 346           the TI DaVinci, OMAP 243x, OMAP 343x, TUSB 6010, and ADI Blackfin
 347
 348 config USB_M66592
 349         tristate "Renesas M66592 USB Peripheral Controller"
 350         help
 351            M66592 is a discrete USB peripheral controller chip that
 352            supports both full and high speed USB 2.0 data transfers.
 353            It has seven configurable endpoints, and endpoint zero.
 354
 355            Say "y" to link the driver statically, or "m" to build a
 356            dynamically linked module called "m66592_udc" and force all
 357            gadget drivers to also be dynamically linked.
 358
 359 #
 360 # Controllers available only in discrete form (and all PCI controllers)
 361 #
 362
 363 config USB_AMD5536UDC
 364         tristate "AMD5536 UDC"
 365         depends on PCI
 366         help
 367            The AMD5536 UDC is part of the AMD Geode CS5536, an x86 southbridge.
 368            It is a USB Highspeed DMA capable USB device controller. Beside ep0
 369            it provides 4 IN and 4 OUT endpoints (bulk or interrupt type).
 370            The UDC port supports OTG operation, and may be used as a host port
 371            if it's not being used to implement peripheral or OTG roles.
 372
 373            Say "y" to link the driver statically, or "m" to build a
 374            dynamically linked module called "amd5536udc" and force all
 375            gadget drivers to also be dynamically linked.
 376
 377 config USB_FSL_QE
 378         tristate "Freescale QE/CPM USB Device Controller"
 379         depends on FSL_SOC && (QUICC_ENGINE || CPM)
 380         help
 381            Some of Freescale PowerPC processors have a Full Speed
 382            QE/CPM2 USB controller, which support device mode with 4
 383            programmable endpoints. This driver supports the
 384            controller in the MPC8360 and MPC8272, and should work with
 385            controllers having QE or CPM2, given minor tweaks.
 386
 387            Set CONFIG_USB_GADGET to "m" to build this driver as a
 388            dynamically linked module called "fsl_qe_udc".
 389
 390 config USB_NET2272
 391         tristate "PLX NET2272"
 392         help
 393           PLX NET2272 is a USB peripheral controller which supports
 394           both full and high speed USB 2.0 data transfers.
 395
 396           It has three configurable endpoints, as well as endpoint zero
 397           (for control transfer).
 398           Say "y" to link the driver statically, or "m" to build a
 399           dynamically linked module called "net2272" and force all
 400           gadget drivers to also be dynamically linked.
 401
 402 config USB_NET2272_DMA
 403         boolean "Support external DMA controller"
 404         depends on USB_NET2272
 405         help
 406           The NET2272 part can optionally support an external DMA
 407           controller, but your board has to have support in the
 408           driver itself.
 409
 410           If unsure, say "N" here.  The driver works fine in PIO mode.
 411
 412 config USB_NET2280
 413         tristate "NetChip 228x"
 414         depends on PCI
 415         help
 416            NetChip 2280 / 2282 is a PCI based USB peripheral controller which
 417            supports both full and high speed USB 2.0 data transfers.
 418
 419            It has six configurable endpoints, as well as endpoint zero
 420            (for control transfers) and several endpoints with dedicated
 421            functions.
 422
 423            Say "y" to link the driver statically, or "m" to build a
 424            dynamically linked module called "net2280" and force all
 425            gadget drivers to also be dynamically linked.
 426
 427 config USB_GOKU
 428         tristate "Toshiba TC86C001 'Goku-S'"
 429         depends on PCI
 430         help
 431            The Toshiba TC86C001 is a PCI device which includes controllers
 432            for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI).
 433
 434            The device controller has three configurable (bulk or interrupt)
 435            endpoints, plus endpoint zero (for control transfers).
 436
 437            Say "y" to link the driver statically, or "m" to build a
 438            dynamically linked module called "goku_udc" and to force all
 439            gadget drivers to also be dynamically linked.
 440
 441 config USB_EG20T
 442         tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7213/ML7831) UDC"
 443         depends on PCI
 444         help
 445           This is a USB device driver for EG20T PCH.
 446           EG20T PCH is the platform controller hub that is used in Intel's
 447           general embedded platform. EG20T PCH has USB device interface.
 448           Using this interface, it is able to access system devices connected
 449           to USB device.
 450           This driver enables USB device function.
 451           USB device is a USB peripheral controller which
 452           supports both full and high speed USB 2.0 data transfers.
 453           This driver supports both control transfer and bulk transfer modes.
 454           This driver dose not support interrupt transfer or isochronous
 455           transfer modes.
 456
 457           This driver also can be used for LAPIS Semiconductor's ML7213 which is
 458           for IVI(In-Vehicle Infotainment) use.
 459           ML7831 is for general purpose use.
 460           ML7213/ML7831 is companion chip for Intel Atom E6xx series.
 461           ML7213/ML7831 is completely compatible for Intel EG20T PCH.
 462
 463 #
 464 # LAST -- dummy/emulated controller
 465 #
 466
 467 config USB_DUMMY_HCD
 468         tristate "Dummy HCD (DEVELOPMENT)"
 469         depends on USB=y || (USB=m && USB_GADGET=m)
 470         help
 471           This host controller driver emulates USB, looping all data transfer
 472           requests back to a USB "gadget driver" in the same host.  The host
 473           side is the master; the gadget side is the slave.  Gadget drivers
 474           can be high, full, or low speed; and they have access to endpoints
 475           like those from NET2280, PXA2xx, or SA1100 hardware.
 476
 477           This may help in some stages of creating a driver to embed in a
 478           Linux device, since it lets you debug several parts of the gadget
 479           driver without its hardware or drivers being involved.
 480
 481           Since such a gadget side driver needs to interoperate with a host
 482           side Linux-USB device driver, this may help to debug both sides
 483           of a USB protocol stack.
 484
 485           Say "y" to link the driver statically, or "m" to build a
 486           dynamically linked module called "dummy_hcd" and force all
 487           gadget drivers to also be dynamically linked.
 488
 489 # NOTE:  Please keep dummy_hcd LAST so that "real hardware" appears
 490 # first and will be selected by default.
 491
 492 endmenu
 493
 494 #
 495 # USB Gadget Drivers
 496 #
 497
 498 # composite based drivers
 499 config USB_LIBCOMPOSITE
 500         tristate
 501         depends on USB_GADGET
 502
 503 config USB_F_SS_LB
 504         tristate
 505
 506 choice
 507         tristate "USB Gadget Drivers"
 508         default USB_ETH
 509         help
 510           A Linux "Gadget Driver" talks to the USB Peripheral Controller
 511           driver through the abstract "gadget" API.  Some other operating
 512           systems call these "client" drivers, of which "class drivers"
 513           are a subset (implementing a USB device class specification).
 514           A gadget driver implements one or more USB functions using
 515           the peripheral hardware.
 516
 517           Gadget drivers are hardware-neutral, or "platform independent",
 518           except that they sometimes must understand quirks or limitations
 519           of the particular controllers they work with.  For example, when
 520           a controller doesn't support alternate configurations or provide
 521           enough of the right types of endpoints, the gadget driver might
 522           not be able work with that controller, or might need to implement
 523           a less common variant of a device class protocol.
 524
 525 # this first set of drivers all depend on bulk-capable hardware.
 526
 527 config USB_ZERO
 528         tristate "Gadget Zero (DEVELOPMENT)"
 529         select USB_LIBCOMPOSITE
 530         select USB_F_SS_LB
 531         help
 532           Gadget Zero is a two-configuration device.  It either sinks and
 533           sources bulk data; or it loops back a configurable number of
 534           transfers.  It also implements control requests, for "chapter 9"
 535           conformance.  The driver needs only two bulk-capable endpoints, so
 536           it can work on top of most device-side usb controllers.  It's
 537           useful for testing, and is also a working example showing how
 538           USB "gadget drivers" can be written.
 539
 540           Make this be the first driver you try using on top of any new
 541           USB peripheral controller driver.  Then you can use host-side
 542           test software, like the "usbtest" driver, to put your hardware
 543           and its driver through a basic set of functional tests.
 544
 545           Gadget Zero also works with the host-side "usb-skeleton" driver,
 546           and with many kinds of host-side test software.  You may need
 547           to tweak product and vendor IDs before host software knows about
 548           this device, and arrange to select an appropriate configuration.
 549
 550           Say "y" to link the driver statically, or "m" to build a
 551           dynamically linked module called "g_zero".
 552
 553 config USB_ZERO_HNPTEST
 554         boolean "HNP Test Device"
 555         depends on USB_ZERO && USB_OTG
 556         help
 557           You can configure this device to enumerate using the device
 558           identifiers of the USB-OTG test device.  That means that when
 559           this gadget connects to another OTG device, with this one using
 560           the "B-Peripheral" role, that device will use HNP to let this
 561           one serve as the USB host instead (in the "B-Host" role).
 562
 563 config USB_AUDIO
 564         tristate "Audio Gadget"
 565         depends on SND
 566         select USB_LIBCOMPOSITE
 567         select SND_PCM
 568         help
 569           This Gadget Audio driver is compatible with USB Audio Class
 570           specification 2.0. It implements 1 AudioControl interface,
 571           1 AudioStreaming Interface each for USB-OUT and USB-IN.
 572           Number of channels, sample rate and sample size can be
 573           specified as module parameters.
 574           This driver doesn't expect any real Audio codec to be present
 575           on the device - the audio streams are simply sinked to and
 576           sourced from a virtual ALSA sound card created. The user-space
 577           application may choose to do whatever it wants with the data
 578           received from the USB Host and choose to provide whatever it
 579           wants as audio data to the USB Host.
 580
 581           Say "y" to link the driver statically, or "m" to build a
 582           dynamically linked module called "g_audio".
 583
 584 config GADGET_UAC1
 585         bool "UAC 1.0 (Legacy)"
 586         depends on USB_AUDIO
 587         help
 588           If you instead want older UAC Spec-1.0 driver that also has audio
 589           paths hardwired to the Audio codec chip on-board and doesn't work
 590           without one.
 591
 592 config USB_ETH
 593         tristate "Ethernet Gadget (with CDC Ethernet support)"
 594         depends on NET
 595         select USB_LIBCOMPOSITE
 596         select CRC32
 597         help
 598           This driver implements Ethernet style communication, in one of
 599           several ways:
 600
 601            - The "Communication Device Class" (CDC) Ethernet Control Model.
 602              That protocol is often avoided with pure Ethernet adapters, in
 603              favor of simpler vendor-specific hardware, but is widely
 604              supported by firmware for smart network devices.
 605
 606            - On hardware can't implement that protocol, a simple CDC subset
 607              is used, placing fewer demands on USB.
 608
 609            - CDC Ethernet Emulation Model (EEM) is a newer standard that has
 610              a simpler interface that can be used by more USB hardware.
 611
 612           RNDIS support is an additional option, more demanding than than
 613           subset.
 614
 615           Within the USB device, this gadget driver exposes a network device
 616           "usbX", where X depends on what other networking devices you have.
 617           Treat it like a two-node Ethernet link:  host, and gadget.
 618
 619           The Linux-USB host-side "usbnet" driver interoperates with this
 620           driver, so that deep I/O queues can be supported.  On 2.4 kernels,
 621           use "CDCEther" instead, if you're using the CDC option. That CDC
 622           mode should also interoperate with standard CDC Ethernet class
 623           drivers on other host operating systems.
 624
 625           Say "y" to link the driver statically, or "m" to build a
 626           dynamically linked module called "g_ether".
 627
 628 config USB_ETH_RNDIS
 629         bool "RNDIS support"
 630         depends on USB_ETH
 631         select USB_LIBCOMPOSITE
 632         default y
 633         help
 634            Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol,
 635            and Microsoft provides redistributable binary RNDIS drivers for
 636            older versions of Windows.
 637
 638            If you say "y" here, the Ethernet gadget driver will try to provide
 639            a second device configuration, supporting RNDIS to talk to such
 640            Microsoft USB hosts.
 641
 642            To make MS-Windows work with this, use Documentation/usb/linux.inf
 643            as the "driver info file".  For versions of MS-Windows older than
 644            XP, you'll need to download drivers from Microsoft's website; a URL
 645            is given in comments found in that info file.
 646
 647 config USB_ETH_EEM
 648        bool "Ethernet Emulation Model (EEM) support"
 649        depends on USB_ETH
 650         select USB_LIBCOMPOSITE
 651        default n
 652        help
 653          CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM
 654          and therefore can be supported by more hardware.  Technically ECM and
 655          EEM are designed for different applications.  The ECM model extends
 656          the network interface to the target (e.g. a USB cable modem), and the
 657          EEM model is for mobile devices to communicate with hosts using
 658          ethernet over USB.  For Linux gadgets, however, the interface with
 659          the host is the same (a usbX device), so the differences are minimal.
 660
 661          If you say "y" here, the Ethernet gadget driver will use the EEM
 662          protocol rather than ECM.  If unsure, say "n".
 663
 664 config USB_G_NCM
 665         tristate "Network Control Model (NCM) support"
 666         depends on NET
 667         select USB_LIBCOMPOSITE
 668         select CRC32
 669         help
 670           This driver implements USB CDC NCM subclass standard. NCM is
 671           an advanced protocol for Ethernet encapsulation, allows grouping
 672           of several ethernet frames into one USB transfer and different
 673           alignment possibilities.
 674
 675           Say "y" to link the driver statically, or "m" to build a
 676           dynamically linked module called "g_ncm".
 677
 678 config USB_GADGETFS
 679         tristate "Gadget Filesystem"
 680         help
 681           This driver provides a filesystem based API that lets user mode
 682           programs implement a single-configuration USB device, including
 683           endpoint I/O and control requests that don't relate to enumeration.
 684           All endpoints, transfer speeds, and transfer types supported by
 685           the hardware are available, through read() and write() calls.
 686
 687           Say "y" to link the driver statically, or "m" to build a
 688           dynamically linked module called "gadgetfs".
 689
 690 config USB_FUNCTIONFS
 691         tristate "Function Filesystem"
 692         select USB_LIBCOMPOSITE
 693         select USB_FUNCTIONFS_GENERIC if !(USB_FUNCTIONFS_ETH || USB_FUNCTIONFS_RNDIS)
 694         help
 695           The Function Filesystem (FunctionFS) lets one create USB
 696           composite functions in user space in the same way GadgetFS
 697           lets one create USB gadgets in user space.  This allows creation
 698           of composite gadgets such that some of the functions are
 699           implemented in kernel space (for instance Ethernet, serial or
 700           mass storage) and other are implemented in user space.
 701
 702           If you say "y" or "m" here you will be able what kind of
 703           configurations the gadget will provide.
 704
 705           Say "y" to link the driver statically, or "m" to build
 706           a dynamically linked module called "g_ffs".
 707
 708 config USB_FUNCTIONFS_ETH
 709         bool "Include configuration with CDC ECM (Ethernet)"
 710         depends on USB_FUNCTIONFS && NET
 711         help
 712           Include a configuration with CDC ECM function (Ethernet) and the
 713           Function Filesystem.
 714
 715 config USB_FUNCTIONFS_RNDIS
 716         bool "Include configuration with RNDIS (Ethernet)"
 717         depends on USB_FUNCTIONFS && NET
 718         help
 719           Include a configuration with RNDIS function (Ethernet) and the Filesystem.
 720
 721 config USB_FUNCTIONFS_GENERIC
 722         bool "Include 'pure' configuration"
 723         depends on USB_FUNCTIONFS
 724         help
 725           Include a configuration with the Function Filesystem alone with
 726           no Ethernet interface.
 727
 728 config USB_MASS_STORAGE
 729         tristate "Mass Storage Gadget"
 730         depends on BLOCK
 731         select USB_LIBCOMPOSITE
 732         help
 733           The Mass Storage Gadget acts as a USB Mass Storage disk drive.
 734           As its storage repository it can use a regular file or a block
 735           device (in much the same way as the "loop" device driver),
 736           specified as a module parameter or sysfs option.
 737
 738           This driver is a replacement for now removed File-backed
 739           Storage Gadget (g_file_storage).
 740
 741           Say "y" to link the driver statically, or "m" to build
 742           a dynamically linked module called "g_mass_storage".
 743
 744 config USB_GADGET_TARGET
 745         tristate "USB Gadget Target Fabric Module"
 746         depends on TARGET_CORE
 747         select USB_LIBCOMPOSITE
 748         help
 749           This fabric is an USB gadget. Two USB protocols are supported that is
 750           BBB or BOT (Bulk Only Transport) and UAS (USB Attached SCSI). BOT is
 751           advertised on alternative interface 0 (primary) and UAS is on
 752           alternative interface 1. Both protocols can work on USB2.0 and USB3.0.
 753           UAS utilizes the USB 3.0 feature called streams support.
 754
 755 config USB_G_SERIAL
 756         tristate "Serial Gadget (with CDC ACM and CDC OBEX support)"
 757         select USB_LIBCOMPOSITE
 758         help
 759           The Serial Gadget talks to the Linux-USB generic serial driver.
 760           This driver supports a CDC-ACM module option, which can be used
 761           to interoperate with MS-Windows hosts or with the Linux-USB
 762           "cdc-acm" driver.
 763
 764           This driver also supports a CDC-OBEX option.  You will need a
 765           user space OBEX server talking to /dev/ttyGS*, since the kernel
 766           itself doesn't implement the OBEX protocol.
 767
 768           Say "y" to link the driver statically, or "m" to build a
 769           dynamically linked module called "g_serial".
 770
 771           For more information, see Documentation/usb/gadget_serial.txt
 772           which includes instructions and a "driver info file" needed to
 773           make MS-Windows work with CDC ACM.
 774
 775 config USB_MIDI_GADGET
 776         tristate "MIDI Gadget"
 777         depends on SND
 778         select USB_LIBCOMPOSITE
 779         select SND_RAWMIDI
 780         help
 781           The MIDI Gadget acts as a USB Audio device, with one MIDI
 782           input and one MIDI output. These MIDI jacks appear as
 783           a sound "card" in the ALSA sound system. Other MIDI
 784           connections can then be made on the gadget system, using
 785           ALSA's aconnect utility etc.
 786
 787           Say "y" to link the driver statically, or "m" to build a
 788           dynamically linked module called "g_midi".
 789
 790 config USB_G_PRINTER
 791         tristate "Printer Gadget"
 792         select USB_LIBCOMPOSITE
 793         help
 794           The Printer Gadget channels data between the USB host and a
 795           userspace program driving the print engine. The user space
 796           program reads and writes the device file /dev/g_printer to
 797           receive or send printer data. It can use ioctl calls to
 798           the device file to get or set printer status.
 799
 800           Say "y" to link the driver statically, or "m" to build a
 801           dynamically linked module called "g_printer".
 802
 803           For more information, see Documentation/usb/gadget_printer.txt
 804           which includes sample code for accessing the device file.
 805
 806 config USB_CDC_COMPOSITE
 807         tristate "CDC Composite Device (Ethernet and ACM)"
 808         depends on NET
 809         select USB_LIBCOMPOSITE
 810         help
 811           This driver provides two functions in one configuration:
 812           a CDC Ethernet (ECM) link, and a CDC ACM (serial port) link.
 813
 814           This driver requires four bulk and two interrupt endpoints,
 815           plus the ability to handle altsettings.  Not all peripheral
 816           controllers are that capable.
 817
 818           Say "y" to link the driver statically, or "m" to build a
 819           dynamically linked module.
 820
 821 config USB_G_NOKIA
 822         tristate "Nokia composite gadget"
 823         depends on PHONET
 824         select USB_LIBCOMPOSITE
 825         help
 826           The Nokia composite gadget provides support for acm, obex
 827           and phonet in only one composite gadget driver.
 828
 829           It's only really useful for N900 hardware. If you're building
 830           a kernel for N900, say Y or M here. If unsure, say N.
 831
 832 config USB_G_ACM_MS
 833         tristate "CDC Composite Device (ACM and mass storage)"
 834         depends on BLOCK
 835         select USB_LIBCOMPOSITE
 836         help
 837           This driver provides two functions in one configuration:
 838           a mass storage, and a CDC ACM (serial port) link.
 839
 840           Say "y" to link the driver statically, or "m" to build a
 841           dynamically linked module called "g_acm_ms".
 842
 843 config USB_G_MULTI
 844         tristate "Multifunction Composite Gadget"
 845         depends on BLOCK && NET
 846         select USB_G_MULTI_CDC if !USB_G_MULTI_RNDIS
 847         select USB_LIBCOMPOSITE
 848         help
 849           The Multifunction Composite Gadget provides Ethernet (RNDIS
 850           and/or CDC Ethernet), mass storage and ACM serial link
 851           interfaces.
 852
 853           You will be asked to choose which of the two configurations is
 854           to be available in the gadget.  At least one configuration must
 855           be chosen to make the gadget usable.  Selecting more than one
 856           configuration will prevent Windows from automatically detecting
 857           the gadget as a composite gadget, so an INF file will be needed to
 858           use the gadget.
 859
 860           Say "y" to link the driver statically, or "m" to build a
 861           dynamically linked module called "g_multi".
 862
 863 config USB_G_MULTI_RNDIS
 864         bool "RNDIS + CDC Serial + Storage configuration"
 865         depends on USB_G_MULTI
 866         default y
 867         help
 868           This option enables a configuration with RNDIS, CDC Serial and
 869           Mass Storage functions available in the Multifunction Composite
 870           Gadget.  This is the configuration dedicated for Windows since RNDIS
 871           is Microsoft's protocol.
 872
 873           If unsure, say "y".
 874
 875 config USB_G_MULTI_CDC
 876         bool "CDC Ethernet + CDC Serial + Storage configuration"
 877         depends on USB_G_MULTI
 878         default n
 879         help
 880           This option enables a configuration with CDC Ethernet (ECM), CDC
 881           Serial and Mass Storage functions available in the Multifunction
 882           Composite Gadget.
 883
 884           If unsure, say "y".
 885
 886 config USB_G_HID
 887         tristate "HID Gadget"
 888         select USB_LIBCOMPOSITE
 889         help
 890           The HID gadget driver provides generic emulation of USB
 891           Human Interface Devices (HID).
 892
 893           For more information, see Documentation/usb/gadget_hid.txt which
 894           includes sample code for accessing the device files.
 895
 896           Say "y" to link the driver statically, or "m" to build a
 897           dynamically linked module called "g_hid".
 898
 899 # Standalone / single function gadgets
 900 config USB_G_DBGP
 901         tristate "EHCI Debug Device Gadget"
 902         select USB_LIBCOMPOSITE
 903         help
 904           This gadget emulates an EHCI Debug device. This is useful when you want
 905           to interact with an EHCI Debug Port.
 906
 907           Say "y" to link the driver statically, or "m" to build a
 908           dynamically linked module called "g_dbgp".
 909
 910 if USB_G_DBGP
 911 choice
 912         prompt "EHCI Debug Device mode"
 913         default USB_G_DBGP_SERIAL
 914
 915 config USB_G_DBGP_PRINTK
 916         depends on USB_G_DBGP
 917         bool "printk"
 918         help
 919           Directly printk() received data. No interaction.
 920
 921 config USB_G_DBGP_SERIAL
 922         depends on USB_G_DBGP
 923         bool "serial"
 924         help
 925           Userland can interact using /dev/ttyGSxxx.
 926 endchoice
 927 endif
 928
 929 # put drivers that need isochronous transfer support (for audio
 930 # or video class gadget drivers), or specific hardware, here.
 931 config USB_G_WEBCAM
 932         tristate "USB Webcam Gadget"
 933         depends on VIDEO_DEV
 934         select USB_LIBCOMPOSITE
 935         help
 936           The Webcam Gadget acts as a composite USB Audio and Video Class
 937           device. It provides a userspace API to process UVC control requests
 938           and stream video data to the host.
 939
 940           Say "y" to link the driver statically, or "m" to build a
 941           dynamically linked module called "g_webcam".
 942
 943 endchoice
 944
 945 endif # USB_GADGET