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         depends on USB_PHY
 148         select USB_ISP1301
 149         help
 150            This option selects the USB device controller in the LPC32xx SoC.
 151
 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.
 155
 156 config USB_ATMEL_USBA
 157         tristate "Atmel USBA"
 158         depends on AVR32 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
 159         help
 160           USBA is the integrated high-speed USB Device controller on
 161           the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel.
 162
 163 config USB_BCM63XX_UDC
 164         tristate "Broadcom BCM63xx Peripheral Controller"
 165         depends on BCM63XX
 166         help
 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).
 170
 171            Say "y" to link the driver statically, or "m" to build a
 172            dynamically linked module called "bcm63xx_udc".
 173
 174 config USB_FSL_USB2
 175         tristate "Freescale Highspeed USB DR Peripheral Controller"
 176         depends on FSL_SOC || ARCH_MXC
 177         select USB_FSL_MPH_DR_OF if OF
 178         help
 179            Some of Freescale PowerPC and i.MX processors have a High Speed
 180            Dual-Role(DR) USB controller, which supports device mode.
 181
 182            The number of programmable endpoints is different through
 183            SOC revisions.
 184
 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.
 188
 189 config USB_FUSB300
 190         tristate "Faraday FUSB300 USB Peripheral Controller"
 191         depends on !PHYS_ADDR_T_64BIT
 192         help
 193            Faraday usb device controller FUSB300 driver
 194
 195 config USB_OMAP
 196         tristate "OMAP USB Device Controller"
 197         depends on ARCH_OMAP1
 198         depends on USB_PHY
 199         select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_H4_OTG
 200         help
 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.
 206
 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.
 210
 211 config USB_PXA25X
 212         tristate "PXA 25x or IXP 4xx"
 213         depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX
 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         help
 262            Intel's PXA 27x series XScale ARM v5TE processors include
 263            an integrated full speed USB 1.1 device controller.
 264
 265            It has up to 23 endpoints, as well as endpoint zero (for
 266            control transfers).
 267
 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.
 271
 272 config USB_S3C_HSOTG
 273         tristate "S3C HS/OtG USB Device controller"
 274         depends on S3C_DEV_USB_HSOTG
 275         help
 276           The Samsung S3C64XX USB2.0 high-speed gadget controller
 277           integrated into the S3C64XX series SoC.
 278
 279 config USB_IMX
 280         tristate "Freescale i.MX1 USB Peripheral Controller"
 281         depends on ARCH_MXC
 282         depends on BROKEN
 283         help
 284            Freescale's i.MX1 includes an integrated full speed
 285            USB 1.1 device controller.
 286
 287            It has Six fixed-function endpoints, as well as endpoint
 288            zero (for control transfers).
 289
 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.
 293
 294 config USB_S3C2410
 295         tristate "S3C2410 USB Device Controller"
 296         depends on ARCH_S3C24XX
 297         help
 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).
 301
 302           This driver has been tested on the S3C2410, S3C2412, and
 303           S3C2440 processors.
 304
 305 config USB_S3C2410_DEBUG
 306         boolean "S3C2410 udc debug messages"
 307         depends on USB_S3C2410
 308
 309 config USB_S3C_HSUDC
 310         tristate "S3C2416, S3C2443 and S3C2450 USB Device Controller"
 311         depends on ARCH_S3C24XX
 312         help
 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.
 316
 317           This driver has been tested on S3C2416 and S3C2450 processors.
 318
 319 config USB_MV_UDC
 320         tristate "Marvell USB2.0 Device Controller"
 321         depends on GENERIC_HARDIRQS
 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         help
 330           MARVELL PXA2128 Processor series include a super speed USB3.0 device
 331           controller, which support super speed USB peripheral.
 332
 333 #
 334 # Controllers available in both integrated and discrete versions
 335 #
 336
 337 config USB_M66592
 338         tristate "Renesas M66592 USB Peripheral Controller"
 339         help
 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.
 343
 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.
 347
 348 #
 349 # Controllers available only in discrete form (and all PCI controllers)
 350 #
 351
 352 config USB_AMD5536UDC
 353         tristate "AMD5536 UDC"
 354         depends on PCI
 355         help
 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.
 361
 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.
 365
 366 config USB_FSL_QE
 367         tristate "Freescale QE/CPM USB Device Controller"
 368         depends on FSL_SOC && (QUICC_ENGINE || CPM)
 369         help
 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.
 375
 376            Set CONFIG_USB_GADGET to "m" to build this driver as a
 377            dynamically linked module called "fsl_qe_udc".
 378
 379 config USB_NET2272
 380         tristate "PLX NET2272"
 381         help
 382           PLX NET2272 is a USB peripheral controller which supports
 383           both full and high speed USB 2.0 data transfers.
 384
 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.
 390
 391 config USB_NET2272_DMA
 392         boolean "Support external DMA controller"
 393         depends on USB_NET2272
 394         help
 395           The NET2272 part can optionally support an external DMA
 396           controller, but your board has to have support in the
 397           driver itself.
 398
 399           If unsure, say "N" here.  The driver works fine in PIO mode.
 400
 401 config USB_NET2280
 402         tristate "NetChip 228x"
 403         depends on PCI
 404         help
 405            NetChip 2280 / 2282 is a PCI based USB peripheral controller which
 406            supports both full and high speed USB 2.0 data transfers.
 407
 408            It has six configurable endpoints, as well as endpoint zero
 409            (for control transfers) and several endpoints with dedicated
 410            functions.
 411
 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.
 415
 416 config USB_GOKU
 417         tristate "Toshiba TC86C001 'Goku-S'"
 418         depends on PCI
 419         help
 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).
 422
 423            The device controller has three configurable (bulk or interrupt)
 424            endpoints, plus endpoint zero (for control transfers).
 425
 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.
 429
 430 config USB_EG20T
 431         tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7213/ML7831) UDC"
 432         depends on PCI && GENERIC_HARDIRQS
 433         help
 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
 438           to USB device.
 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
 444           transfer modes.
 445
 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.
 451
 452 #
 453 # LAST -- dummy/emulated controller
 454 #
 455
 456 config USB_DUMMY_HCD
 457         tristate "Dummy HCD (DEVELOPMENT)"
 458         depends on USB=y || (USB=m && USB_GADGET=m)
 459         help
 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.
 465
 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.
 469
 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.
 473
 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.
 477
 478 # NOTE:  Please keep dummy_hcd LAST so that "real hardware" appears
 479 # first and will be selected by default.
 480
 481 endmenu
 482
 483 #
 484 # USB Gadget Drivers
 485 #
 486
 487 # composite based drivers
 488 config USB_LIBCOMPOSITE
 489         tristate
 490         select CONFIGFS_FS
 491         depends on USB_GADGET
 492
 493 config USB_F_ACM
 494         tristate
 495
 496 config USB_F_SS_LB
 497         tristate
 498
 499 config USB_U_SERIAL
 500         tristate
 501
 502 config USB_U_ETHER
 503         tristate
 504
 505 config USB_F_SERIAL
 506         tristate
 507
 508 config USB_F_OBEX
 509         tristate
 510
 511 choice
 512         tristate "USB Gadget Drivers"
 513         default USB_ETH
 514         help
 515           A Linux "Gadget Driver" talks to the USB Peripheral Controller
 516           driver through the abstract "gadget" API.  Some other operating
 517           systems call these "client" drivers, of which "class drivers"
 518           are a subset (implementing a USB device class specification).
 519           A gadget driver implements one or more USB functions using
 520           the peripheral hardware.
 521
 522           Gadget drivers are hardware-neutral, or "platform independent",
 523           except that they sometimes must understand quirks or limitations
 524           of the particular controllers they work with.  For example, when
 525           a controller doesn't support alternate configurations or provide
 526           enough of the right types of endpoints, the gadget driver might
 527           not be able work with that controller, or might need to implement
 528           a less common variant of a device class protocol.
 529
 530 # this first set of drivers all depend on bulk-capable hardware.
 531
 532 config USB_ZERO
 533         tristate "Gadget Zero (DEVELOPMENT)"
 534         select USB_LIBCOMPOSITE
 535         select USB_F_SS_LB
 536         help
 537           Gadget Zero is a two-configuration device.  It either sinks and
 538           sources bulk data; or it loops back a configurable number of
 539           transfers.  It also implements control requests, for "chapter 9"
 540           conformance.  The driver needs only two bulk-capable endpoints, so
 541           it can work on top of most device-side usb controllers.  It's
 542           useful for testing, and is also a working example showing how
 543           USB "gadget drivers" can be written.
 544
 545           Make this be the first driver you try using on top of any new
 546           USB peripheral controller driver.  Then you can use host-side
 547           test software, like the "usbtest" driver, to put your hardware
 548           and its driver through a basic set of functional tests.
 549
 550           Gadget Zero also works with the host-side "usb-skeleton" driver,
 551           and with many kinds of host-side test software.  You may need
 552           to tweak product and vendor IDs before host software knows about
 553           this device, and arrange to select an appropriate configuration.
 554
 555           Say "y" to link the driver statically, or "m" to build a
 556           dynamically linked module called "g_zero".
 557
 558 config USB_ZERO_HNPTEST
 559         boolean "HNP Test Device"
 560         depends on USB_ZERO && USB_OTG
 561         help
 562           You can configure this device to enumerate using the device
 563           identifiers of the USB-OTG test device.  That means that when
 564           this gadget connects to another OTG device, with this one using
 565           the "B-Peripheral" role, that device will use HNP to let this
 566           one serve as the USB host instead (in the "B-Host" role).
 567
 568 config USB_AUDIO
 569         tristate "Audio Gadget"
 570         depends on SND
 571         select USB_LIBCOMPOSITE
 572         select SND_PCM
 573         help
 574           This Gadget Audio driver is compatible with USB Audio Class
 575           specification 2.0. It implements 1 AudioControl interface,
 576           1 AudioStreaming Interface each for USB-OUT and USB-IN.
 577           Number of channels, sample rate and sample size can be
 578           specified as module parameters.
 579           This driver doesn't expect any real Audio codec to be present
 580           on the device - the audio streams are simply sinked to and
 581           sourced from a virtual ALSA sound card created. The user-space
 582           application may choose to do whatever it wants with the data
 583           received from the USB Host and choose to provide whatever it
 584           wants as audio data to the USB Host.
 585
 586           Say "y" to link the driver statically, or "m" to build a
 587           dynamically linked module called "g_audio".
 588
 589 config GADGET_UAC1
 590         bool "UAC 1.0 (Legacy)"
 591         depends on USB_AUDIO
 592         help
 593           If you instead want older UAC Spec-1.0 driver that also has audio
 594           paths hardwired to the Audio codec chip on-board and doesn't work
 595           without one.
 596
 597 config USB_ETH
 598         tristate "Ethernet Gadget (with CDC Ethernet support)"
 599         depends on NET
 600         select USB_LIBCOMPOSITE
 601         select USB_U_ETHER
 602         select CRC32
 603         help
 604           This driver implements Ethernet style communication, in one of
 605           several ways:
 606
 607            - The "Communication Device Class" (CDC) Ethernet Control Model.
 608              That protocol is often avoided with pure Ethernet adapters, in
 609              favor of simpler vendor-specific hardware, but is widely
 610              supported by firmware for smart network devices.
 611
 612            - On hardware can't implement that protocol, a simple CDC subset
 613              is used, placing fewer demands on USB.
 614
 615            - CDC Ethernet Emulation Model (EEM) is a newer standard that has
 616              a simpler interface that can be used by more USB hardware.
 617
 618           RNDIS support is an additional option, more demanding than than
 619           subset.
 620
 621           Within the USB device, this gadget driver exposes a network device
 622           "usbX", where X depends on what other networking devices you have.
 623           Treat it like a two-node Ethernet link:  host, and gadget.
 624
 625           The Linux-USB host-side "usbnet" driver interoperates with this
 626           driver, so that deep I/O queues can be supported.  On 2.4 kernels,
 627           use "CDCEther" instead, if you're using the CDC option. That CDC
 628           mode should also interoperate with standard CDC Ethernet class
 629           drivers on other host operating systems.
 630
 631           Say "y" to link the driver statically, or "m" to build a
 632           dynamically linked module called "g_ether".
 633
 634 config USB_ETH_RNDIS
 635         bool "RNDIS support"
 636         depends on USB_ETH
 637         select USB_LIBCOMPOSITE
 638         default y
 639         help
 640            Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol,
 641            and Microsoft provides redistributable binary RNDIS drivers for
 642            older versions of Windows.
 643
 644            If you say "y" here, the Ethernet gadget driver will try to provide
 645            a second device configuration, supporting RNDIS to talk to such
 646            Microsoft USB hosts.
 647
 648            To make MS-Windows work with this, use Documentation/usb/linux.inf
 649            as the "driver info file".  For versions of MS-Windows older than
 650            XP, you'll need to download drivers from Microsoft's website; a URL
 651            is given in comments found in that info file.
 652
 653 config USB_ETH_EEM
 654        bool "Ethernet Emulation Model (EEM) support"
 655        depends on USB_ETH
 656         select USB_LIBCOMPOSITE
 657        default n
 658        help
 659          CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM
 660          and therefore can be supported by more hardware.  Technically ECM and
 661          EEM are designed for different applications.  The ECM model extends
 662          the network interface to the target (e.g. a USB cable modem), and the
 663          EEM model is for mobile devices to communicate with hosts using
 664          ethernet over USB.  For Linux gadgets, however, the interface with
 665          the host is the same (a usbX device), so the differences are minimal.
 666
 667          If you say "y" here, the Ethernet gadget driver will use the EEM
 668          protocol rather than ECM.  If unsure, say "n".
 669
 670 config USB_G_NCM
 671         tristate "Network Control Model (NCM) support"
 672         depends on NET
 673         select USB_LIBCOMPOSITE
 674         select USB_U_ETHER
 675         select CRC32
 676         help
 677           This driver implements USB CDC NCM subclass standard. NCM is
 678           an advanced protocol for Ethernet encapsulation, allows grouping
 679           of several ethernet frames into one USB transfer and different
 680           alignment possibilities.
 681
 682           Say "y" to link the driver statically, or "m" to build a
 683           dynamically linked module called "g_ncm".
 684
 685 config USB_GADGETFS
 686         tristate "Gadget Filesystem"
 687         help
 688           This driver provides a filesystem based API that lets user mode
 689           programs implement a single-configuration USB device, including
 690           endpoint I/O and control requests that don't relate to enumeration.
 691           All endpoints, transfer speeds, and transfer types supported by
 692           the hardware are available, through read() and write() calls.
 693
 694           Say "y" to link the driver statically, or "m" to build a
 695           dynamically linked module called "gadgetfs".
 696
 697 config USB_FUNCTIONFS
 698         tristate "Function Filesystem"
 699         select USB_LIBCOMPOSITE
 700         select USB_FUNCTIONFS_GENERIC if !(USB_FUNCTIONFS_ETH || USB_FUNCTIONFS_RNDIS)
 701         help
 702           The Function Filesystem (FunctionFS) lets one create USB
 703           composite functions in user space in the same way GadgetFS
 704           lets one create USB gadgets in user space.  This allows creation
 705           of composite gadgets such that some of the functions are
 706           implemented in kernel space (for instance Ethernet, serial or
 707           mass storage) and other are implemented in user space.
 708
 709           If you say "y" or "m" here you will be able what kind of
 710           configurations the gadget will provide.
 711
 712           Say "y" to link the driver statically, or "m" to build
 713           a dynamically linked module called "g_ffs".
 714
 715 config USB_FUNCTIONFS_ETH
 716         bool "Include configuration with CDC ECM (Ethernet)"
 717         depends on USB_FUNCTIONFS && NET
 718         select USB_U_ETHER
 719         help
 720           Include a configuration with CDC ECM function (Ethernet) and the
 721           Function Filesystem.
 722
 723 config USB_FUNCTIONFS_RNDIS
 724         bool "Include configuration with RNDIS (Ethernet)"
 725         depends on USB_FUNCTIONFS && NET
 726         select USB_U_ETHER
 727         help
 728           Include a configuration with RNDIS function (Ethernet) and the Filesystem.
 729
 730 config USB_FUNCTIONFS_GENERIC
 731         bool "Include 'pure' configuration"
 732         depends on USB_FUNCTIONFS
 733         help
 734           Include a configuration with the Function Filesystem alone with
 735           no Ethernet interface.
 736
 737 config USB_MASS_STORAGE
 738         tristate "Mass Storage Gadget"
 739         depends on BLOCK
 740         select USB_LIBCOMPOSITE
 741         help
 742           The Mass Storage Gadget acts as a USB Mass Storage disk drive.
 743           As its storage repository it can use a regular file or a block
 744           device (in much the same way as the "loop" device driver),
 745           specified as a module parameter or sysfs option.
 746
 747           This driver is a replacement for now removed File-backed
 748           Storage Gadget (g_file_storage).
 749
 750           Say "y" to link the driver statically, or "m" to build
 751           a dynamically linked module called "g_mass_storage".
 752
 753 config USB_GADGET_TARGET
 754         tristate "USB Gadget Target Fabric Module"
 755         depends on TARGET_CORE
 756         select USB_LIBCOMPOSITE
 757         help
 758           This fabric is an USB gadget. Two USB protocols are supported that is
 759           BBB or BOT (Bulk Only Transport) and UAS (USB Attached SCSI). BOT is
 760           advertised on alternative interface 0 (primary) and UAS is on
 761           alternative interface 1. Both protocols can work on USB2.0 and USB3.0.
 762           UAS utilizes the USB 3.0 feature called streams support.
 763
 764 config USB_G_SERIAL
 765         tristate "Serial Gadget (with CDC ACM and CDC OBEX support)"
 766         depends on TTY
 767         select USB_U_SERIAL
 768         select USB_F_ACM
 769         select USB_F_SERIAL
 770         select USB_F_OBEX
 771         select USB_LIBCOMPOSITE
 772         help
 773           The Serial Gadget talks to the Linux-USB generic serial driver.
 774           This driver supports a CDC-ACM module option, which can be used
 775           to interoperate with MS-Windows hosts or with the Linux-USB
 776           "cdc-acm" driver.
 777
 778           This driver also supports a CDC-OBEX option.  You will need a
 779           user space OBEX server talking to /dev/ttyGS*, since the kernel
 780           itself doesn't implement the OBEX protocol.
 781
 782           Say "y" to link the driver statically, or "m" to build a
 783           dynamically linked module called "g_serial".
 784
 785           For more information, see Documentation/usb/gadget_serial.txt
 786           which includes instructions and a "driver info file" needed to
 787           make MS-Windows work with CDC ACM.
 788
 789 config USB_MIDI_GADGET
 790         tristate "MIDI Gadget"
 791         depends on SND
 792         select USB_LIBCOMPOSITE
 793         select SND_RAWMIDI
 794         help
 795           The MIDI Gadget acts as a USB Audio device, with one MIDI
 796           input and one MIDI output. These MIDI jacks appear as
 797           a sound "card" in the ALSA sound system. Other MIDI
 798           connections can then be made on the gadget system, using
 799           ALSA's aconnect utility etc.
 800
 801           Say "y" to link the driver statically, or "m" to build a
 802           dynamically linked module called "g_midi".
 803
 804 config USB_G_PRINTER
 805         tristate "Printer Gadget"
 806         select USB_LIBCOMPOSITE
 807         help
 808           The Printer Gadget channels data between the USB host and a
 809           userspace program driving the print engine. The user space
 810           program reads and writes the device file /dev/g_printer to
 811           receive or send printer data. It can use ioctl calls to
 812           the device file to get or set printer status.
 813
 814           Say "y" to link the driver statically, or "m" to build a
 815           dynamically linked module called "g_printer".
 816
 817           For more information, see Documentation/usb/gadget_printer.txt
 818           which includes sample code for accessing the device file.
 819
 820 if TTY
 821
 822 config USB_CDC_COMPOSITE
 823         tristate "CDC Composite Device (Ethernet and ACM)"
 824         depends on NET
 825         select USB_LIBCOMPOSITE
 826         select USB_U_SERIAL
 827         select USB_U_ETHER
 828         select USB_F_ACM
 829         help
 830           This driver provides two functions in one configuration:
 831           a CDC Ethernet (ECM) link, and a CDC ACM (serial port) link.
 832
 833           This driver requires four bulk and two interrupt endpoints,
 834           plus the ability to handle altsettings.  Not all peripheral
 835           controllers are that capable.
 836
 837           Say "y" to link the driver statically, or "m" to build a
 838           dynamically linked module.
 839
 840 config USB_G_NOKIA
 841         tristate "Nokia composite gadget"
 842         depends on PHONET
 843         select USB_LIBCOMPOSITE
 844         select USB_U_SERIAL
 845         select USB_U_ETHER
 846         select USB_F_ACM
 847         help
 848           The Nokia composite gadget provides support for acm, obex
 849           and phonet in only one composite gadget driver.
 850
 851           It's only really useful for N900 hardware. If you're building
 852           a kernel for N900, say Y or M here. If unsure, say N.
 853
 854 config USB_G_ACM_MS
 855         tristate "CDC Composite Device (ACM and mass storage)"
 856         depends on BLOCK
 857         select USB_LIBCOMPOSITE
 858         select USB_U_SERIAL
 859         select USB_F_ACM
 860         help
 861           This driver provides two functions in one configuration:
 862           a mass storage, and a CDC ACM (serial port) link.
 863
 864           Say "y" to link the driver statically, or "m" to build a
 865           dynamically linked module called "g_acm_ms".
 866
 867 config USB_G_MULTI
 868         tristate "Multifunction Composite Gadget"
 869         depends on BLOCK && NET
 870         select USB_G_MULTI_CDC if !USB_G_MULTI_RNDIS
 871         select USB_LIBCOMPOSITE
 872         select USB_U_SERIAL
 873         select USB_U_ETHER
 874         select USB_F_ACM
 875         help
 876           The Multifunction Composite Gadget provides Ethernet (RNDIS
 877           and/or CDC Ethernet), mass storage and ACM serial link
 878           interfaces.
 879
 880           You will be asked to choose which of the two configurations is
 881           to be available in the gadget.  At least one configuration must
 882           be chosen to make the gadget usable.  Selecting more than one
 883           configuration will prevent Windows from automatically detecting
 884           the gadget as a composite gadget, so an INF file will be needed to
 885           use the gadget.
 886
 887           Say "y" to link the driver statically, or "m" to build a
 888           dynamically linked module called "g_multi".
 889
 890 config USB_G_MULTI_RNDIS
 891         bool "RNDIS + CDC Serial + Storage configuration"
 892         depends on USB_G_MULTI
 893         default y
 894         help
 895           This option enables a configuration with RNDIS, CDC Serial and
 896           Mass Storage functions available in the Multifunction Composite
 897           Gadget.  This is the configuration dedicated for Windows since RNDIS
 898           is Microsoft's protocol.
 899
 900           If unsure, say "y".
 901
 902 config USB_G_MULTI_CDC
 903         bool "CDC Ethernet + CDC Serial + Storage configuration"
 904         depends on USB_G_MULTI
 905         default n
 906         help
 907           This option enables a configuration with CDC Ethernet (ECM), CDC
 908           Serial and Mass Storage functions available in the Multifunction
 909           Composite Gadget.
 910
 911           If unsure, say "y".
 912
 913 endif # TTY
 914
 915 config USB_G_HID
 916         tristate "HID Gadget"
 917         select USB_LIBCOMPOSITE
 918         help
 919           The HID gadget driver provides generic emulation of USB
 920           Human Interface Devices (HID).
 921
 922           For more information, see Documentation/usb/gadget_hid.txt which
 923           includes sample code for accessing the device files.
 924
 925           Say "y" to link the driver statically, or "m" to build a
 926           dynamically linked module called "g_hid".
 927
 928 # Standalone / single function gadgets
 929 config USB_G_DBGP
 930         tristate "EHCI Debug Device Gadget"
 931         depends on TTY
 932         select USB_LIBCOMPOSITE
 933         help
 934           This gadget emulates an EHCI Debug device. This is useful when you want
 935           to interact with an EHCI Debug Port.
 936
 937           Say "y" to link the driver statically, or "m" to build a
 938           dynamically linked module called "g_dbgp".
 939
 940 if USB_G_DBGP
 941 choice
 942         prompt "EHCI Debug Device mode"
 943         default USB_G_DBGP_SERIAL
 944
 945 config USB_G_DBGP_PRINTK
 946         depends on USB_G_DBGP
 947         bool "printk"
 948         help
 949           Directly printk() received data. No interaction.
 950
 951 config USB_G_DBGP_SERIAL
 952         depends on USB_G_DBGP
 953         select USB_U_SERIAL
 954         bool "serial"
 955         help
 956           Userland can interact using /dev/ttyGSxxx.
 957 endchoice
 958 endif
 959
 960 # put drivers that need isochronous transfer support (for audio
 961 # or video class gadget drivers), or specific hardware, here.
 962 config USB_G_WEBCAM
 963         tristate "USB Webcam Gadget"
 964         depends on VIDEO_DEV
 965         select USB_LIBCOMPOSITE
 966         select VIDEOBUF2_VMALLOC
 967         help
 968           The Webcam Gadget acts as a composite USB Audio and Video Class
 969           device. It provides a userspace API to process UVC control requests
 970           and stream video data to the host.
 971
 972           Say "y" to link the driver statically, or "m" to build a
 973           dynamically linked module called "g_webcam".
 974
 975 endchoice
 976
 977 endif # USB_GADGET