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