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