drivers/usb/gadget/Kconfig

   1 #
   2 # USB Gadget support on a system involves
   3 #    (a) a peripheral controller, and
   4 #    (b) the gadget driver using it.
   5 #
   6 # NOTE:  Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
   7 #
   8 #  - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
   9 #  - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
  10 #  - Some systems have both kinds of controllers.
  11 #
  12 # With help from a special transceiver and a "Mini-AB" jack, systems with
  13 # both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
  14 #
  15
  16 menuconfig USB_GADGET
  17         tristate "USB Gadget Support"
  18         select NLS
  19         help
  20            USB is a master/slave protocol, organized with one master
  21            host (such as a PC) controlling up to 127 peripheral devices.
  22            The USB hardware is asymmetric, which makes it easier to set up:
  23            you can't connect a "to-the-host" connector to a peripheral.
  24
  25            Linux can run in the host, or in the peripheral.  In both cases
  26            you need a low level bus controller driver, and some software
  27            talking to it.  Peripheral controllers are often discrete silicon,
  28            or are integrated with the CPU in a microcontroller.  The more
  29            familiar host side controllers have names like "EHCI", "OHCI",
  30            or "UHCI", and are usually integrated into southbridges on PC
  31            motherboards.
  32
  33            Enable this configuration option if you want to run Linux inside
  34            a USB peripheral device.  Configure one hardware driver for your
  35            peripheral/device side bus controller, and a "gadget driver" for
  36            your peripheral protocol.  (If you use modular gadget drivers,
  37            you may configure more than one.)
  38
  39            If in doubt, say "N" and don't enable these drivers; most people
  40            don't have this kind of hardware (except maybe inside Linux PDAs).
  41
  42            For more information, see <http://www.linux-usb.org/gadget> and
  43            the kernel DocBook documentation for this API.
  44
  45 if USB_GADGET
  46
  47 config USB_GADGET_DEBUG
  48         boolean "Debugging messages (DEVELOPMENT)"
  49         depends on DEBUG_KERNEL
  50         help
  51            Many controller and gadget drivers will print some debugging
  52            messages if you use this option to ask for those messages.
  53
  54            Avoid enabling these messages, even if you're actively
  55            debugging such a driver.  Many drivers will emit so many
  56            messages that the driver timings are affected, which will
  57            either create new failure modes or remove the one you're
  58            trying to track down.  Never enable these messages for a
  59            production build.
  60
  61 config USB_GADGET_DEBUG_FILES
  62         boolean "Debugging information files (DEVELOPMENT)"
  63         depends on PROC_FS
  64         help
  65            Some of the drivers in the "gadget" framework can expose
  66            debugging information in files such as /proc/driver/udc
  67            (for a peripheral controller).  The information in these
  68            files may help when you're troubleshooting or bringing up a
  69            driver on a new board.   Enable these files by choosing "Y"
  70            here.  If in doubt, or to conserve kernel memory, say "N".
  71
  72 config USB_GADGET_DEBUG_FS
  73         boolean "Debugging information files in debugfs (DEVELOPMENT)"
  74         depends on DEBUG_FS
  75         help
  76            Some of the drivers in the "gadget" framework can expose
  77            debugging information in files under /sys/kernel/debug/.
  78            The information in these files may help when you're
  79            troubleshooting or bringing up a driver on a new board.
  80            Enable these files by choosing "Y" here.  If in doubt, or
  81            to conserve kernel memory, say "N".
  82
  83 config USB_GADGET_VBUS_DRAW
  84         int "Maximum VBUS Power usage (2-500 mA)"
  85         range 2 500
  86         default 2
  87         help
  88            Some devices need to draw power from USB when they are
  89            configured, perhaps to operate circuitry or to recharge
  90            batteries.  This is in addition to any local power supply,
  91            such as an AC adapter or batteries.
  92
  93            Enter the maximum power your device draws through USB, in
  94            milliAmperes.  The permitted range of values is 2 - 500 mA;
  95            0 mA would be legal, but can make some hosts misbehave.
  96
  97            This value will be used except for system-specific gadget
  98            drivers that have more specific information.
  99
 100 config USB_GADGET_STORAGE_NUM_BUFFERS
 101         int "Number of storage pipeline buffers"
 102         range 2 4
 103         default 2
 104         help
 105            Usually 2 buffers are enough to establish a good buffering
 106            pipeline. The number may be increased in order to compensate
 107            for a bursty VFS behaviour. For instance there may be CPU wake up
 108            latencies that makes the VFS to appear bursty in a system with
 109            an CPU on-demand governor. Especially if DMA is doing IO to
 110            offload the CPU. In this case the CPU will go into power
 111            save often and spin up occasionally to move data within VFS.
 112            If selecting USB_GADGET_DEBUG_FILES this value may be set by
 113            a module parameter as well.
 114            If unsure, say 2.
 115
 116 #
 117 # USB Peripheral Controller Support
 118 #
 119 # The order here is alphabetical, except that integrated controllers go
 120 # before discrete ones so they will be the initial/default value:
 121 #   - integrated/SOC controllers first
 122 #   - licensed IP used in both SOC and discrete versions
 123 #   - discrete ones (including all PCI-only controllers)
 124 #   - debug/dummy gadget+hcd is last.
 125 #
 126 menu "USB Peripheral Controller"
 127
 128 #
 129 # Integrated controllers
 130 #
 131
 132 config USB_AT91
 133         tristate "Atmel AT91 USB Device Port"
 134         depends on ARCH_AT91
 135         help
 136            Many Atmel AT91 processors (such as the AT91RM2000) have a
 137            full speed USB Device Port with support for five configurable
 138            endpoints (plus endpoint zero).
 139
 140            Say "y" to link the driver statically, or "m" to build a
 141            dynamically linked module called "at91_udc" and force all
 142            gadget drivers to also be dynamically linked.
 143
 144 config USB_LPC32XX
 145         tristate "LPC32XX USB Peripheral Controller"
 146         depends on ARCH_LPC32XX
 147         select USB_ISP1301
 148         select USB_OTG_UTILS
 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         select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_H4_OTG
 199         select USB_OTG_UTILS if ARCH_OMAP
 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         select USB_OTG_UTILS
 215         help
 216            Intel's PXA 25x series XScale ARM-5TE processors include
 217            an integrated full speed USB 1.1 device controller.  The
 218            controller in the IXP 4xx series is register-compatible.
 219
 220            It has fifteen fixed-function endpoints, as well as endpoint
 221            zero (for control transfers).
 222
 223            Say "y" to link the driver statically, or "m" to build a
 224            dynamically linked module called "pxa25x_udc" and force all
 225            gadget drivers to also be dynamically linked.
 226
 227 # if there's only one gadget driver, using only two bulk endpoints,
 228 # don't waste memory for the other endpoints
 229 config USB_PXA25X_SMALL
 230         depends on USB_PXA25X
 231         bool
 232         default n if USB_ETH_RNDIS
 233         default y if USB_ZERO
 234         default y if USB_ETH
 235         default y if USB_G_SERIAL
 236
 237 config USB_R8A66597
 238         tristate "Renesas R8A66597 USB Peripheral Controller"
 239         help
 240            R8A66597 is a discrete USB host and peripheral controller chip that
 241            supports both full and high speed USB 2.0 data transfers.
 242            It has nine configurable endpoints, and endpoint zero.
 243
 244            Say "y" to link the driver statically, or "m" to build a
 245            dynamically linked module called "r8a66597_udc" and force all
 246            gadget drivers to also be dynamically linked.
 247
 248 config USB_RENESAS_USBHS_UDC
 249         tristate 'Renesas USBHS controller'
 250         depends on USB_RENESAS_USBHS
 251         help
 252            Renesas USBHS is a discrete USB host and peripheral controller chip
 253            that supports both full and high speed USB 2.0 data transfers.
 254            It has nine or more configurable endpoints, and endpoint zero.
 255
 256            Say "y" to link the driver statically, or "m" to build a
 257            dynamically linked module called "renesas_usbhs" and force all
 258            gadget drivers to also be dynamically linked.
 259
 260 config USB_PXA27X
 261         tristate "PXA 27x"
 262         depends on ARCH_PXA && (PXA27x || PXA3xx)
 263         select USB_OTG_UTILS
 264         help
 265            Intel's PXA 27x series XScale ARM v5TE processors include
 266            an integrated full speed USB 1.1 device controller.
 267
 268            It has up to 23 endpoints, as well as endpoint zero (for
 269            control transfers).
 270
 271            Say "y" to link the driver statically, or "m" to build a
 272            dynamically linked module called "pxa27x_udc" and force all
 273            gadget drivers to also be dynamically linked.
 274
 275 config USB_S3C_HSOTG
 276         tristate "S3C HS/OtG USB Device controller"
 277         depends on S3C_DEV_USB_HSOTG
 278         help
 279           The Samsung S3C64XX USB2.0 high-speed gadget controller
 280           integrated into the S3C64XX series SoC.
 281
 282 config USB_IMX
 283         tristate "Freescale i.MX1 USB Peripheral Controller"
 284         depends on ARCH_MXC
 285         depends on BROKEN
 286         help
 287            Freescale's i.MX1 includes an integrated full speed
 288            USB 1.1 device controller.
 289
 290            It has Six fixed-function endpoints, as well as endpoint
 291            zero (for control transfers).
 292
 293            Say "y" to link the driver statically, or "m" to build a
 294            dynamically linked module called "imx_udc" and force all
 295            gadget drivers to also be dynamically linked.
 296
 297 config USB_S3C2410
 298         tristate "S3C2410 USB Device Controller"
 299         depends on ARCH_S3C24XX
 300         help
 301           Samsung's S3C2410 is an ARM-4 processor with an integrated
 302           full speed USB 1.1 device controller.  It has 4 configurable
 303           endpoints, as well as endpoint zero (for control transfers).
 304
 305           This driver has been tested on the S3C2410, S3C2412, and
 306           S3C2440 processors.
 307
 308 config USB_S3C2410_DEBUG
 309         boolean "S3C2410 udc debug messages"
 310         depends on USB_S3C2410
 311
 312 config USB_S3C_HSUDC
 313         tristate "S3C2416, S3C2443 and S3C2450 USB Device Controller"
 314         depends on ARCH_S3C24XX
 315         help
 316           Samsung's S3C2416, S3C2443 and S3C2450 is an ARM9 based SoC
 317           integrated with dual speed USB 2.0 device controller. It has
 318           8 endpoints, as well as endpoint zero.
 319
 320           This driver has been tested on S3C2416 and S3C2450 processors.
 321
 322 config USB_MV_UDC
 323         tristate "Marvell USB2.0 Device Controller"
 324         depends on GENERIC_HARDIRQS
 325         help
 326           Marvell Socs (including PXA and MMP series) include a high speed
 327           USB2.0 OTG controller, which can be configured as high speed or
 328           full speed USB peripheral.
 329
 330 config USB_MV_U3D
 331         tristate "MARVELL PXA2128 USB 3.0 controller"
 332         depends on CPU_MMP3
 333         select USB_GADGET_DUALSPEED
 334         select USB_GADGET_SUPERSPEED
 335         help
 336           MARVELL PXA2128 Processor series include a super speed USB3.0 device
 337           controller, which support super speed USB peripheral.
 338
 339 #
 340 # Controllers available in both integrated and discrete versions
 341 #
 342
 343 # musb builds in ../musb along with host support
 344 config USB_GADGET_MUSB_HDRC
 345         tristate "Inventra HDRC USB Peripheral (TI, ADI, ...)"
 346         depends on USB_MUSB_HDRC
 347         help
 348           This OTG-capable silicon IP is used in dual designs including
 349           the TI DaVinci, OMAP 243x, OMAP 343x, TUSB 6010, and ADI Blackfin
 350
 351 config USB_M66592
 352         tristate "Renesas M66592 USB Peripheral Controller"
 353         help
 354            M66592 is a discrete USB peripheral controller chip that
 355            supports both full and high speed USB 2.0 data transfers.
 356            It has seven configurable endpoints, and endpoint zero.
 357
 358            Say "y" to link the driver statically, or "m" to build a
 359            dynamically linked module called "m66592_udc" and force all
 360            gadget drivers to also be dynamically linked.
 361
 362 #
 363 # Controllers available only in discrete form (and all PCI controllers)
 364 #
 365
 366 config USB_AMD5536UDC
 367         tristate "AMD5536 UDC"
 368         depends on PCI
 369         help
 370            The AMD5536 UDC is part of the AMD Geode CS5536, an x86 southbridge.
 371            It is a USB Highspeed DMA capable USB device controller. Beside ep0
 372            it provides 4 IN and 4 OUT endpoints (bulk or interrupt type).
 373            The UDC port supports OTG operation, and may be used as a host port
 374            if it's not being used to implement peripheral or OTG roles.
 375
 376            Say "y" to link the driver statically, or "m" to build a
 377            dynamically linked module called "amd5536udc" and force all
 378            gadget drivers to also be dynamically linked.
 379
 380 config USB_FSL_QE
 381         tristate "Freescale QE/CPM USB Device Controller"
 382         depends on FSL_SOC && (QUICC_ENGINE || CPM)
 383         help
 384            Some of Freescale PowerPC processors have a Full Speed
 385            QE/CPM2 USB controller, which support device mode with 4
 386            programmable endpoints. This driver supports the
 387            controller in the MPC8360 and MPC8272, and should work with
 388            controllers having QE or CPM2, given minor tweaks.
 389
 390            Set CONFIG_USB_GADGET to "m" to build this driver as a
 391            dynamically linked module called "fsl_qe_udc".
 392
 393 config USB_NET2272
 394         tristate "PLX NET2272"
 395         help
 396           PLX NET2272 is a USB peripheral controller which supports
 397           both full and high speed USB 2.0 data transfers.
 398
 399           It has three configurable endpoints, as well as endpoint zero
 400           (for control transfer).
 401           Say "y" to link the driver statically, or "m" to build a
 402           dynamically linked module called "net2272" and force all
 403           gadget drivers to also be dynamically linked.
 404
 405 config USB_NET2272_DMA
 406         boolean "Support external DMA controller"
 407         depends on USB_NET2272
 408         help
 409           The NET2272 part can optionally support an external DMA
 410           controller, but your board has to have support in the
 411           driver itself.
 412
 413           If unsure, say "N" here.  The driver works fine in PIO mode.
 414
 415 config USB_NET2280
 416         tristate "NetChip 228x"
 417         depends on PCI
 418         help
 419            NetChip 2280 / 2282 is a PCI based USB peripheral controller which
 420            supports both full and high speed USB 2.0 data transfers.
 421
 422            It has six configurable endpoints, as well as endpoint zero
 423            (for control transfers) and several endpoints with dedicated
 424            functions.
 425
 426            Say "y" to link the driver statically, or "m" to build a
 427            dynamically linked module called "net2280" and force all
 428            gadget drivers to also be dynamically linked.
 429
 430 config USB_GOKU
 431         tristate "Toshiba TC86C001 'Goku-S'"
 432         depends on PCI
 433         help
 434            The Toshiba TC86C001 is a PCI device which includes controllers
 435            for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI).
 436
 437            The device controller has three configurable (bulk or interrupt)
 438            endpoints, plus endpoint zero (for control transfers).
 439
 440            Say "y" to link the driver statically, or "m" to build a
 441            dynamically linked module called "goku_udc" and to force all
 442            gadget drivers to also be dynamically linked.
 443
 444 config USB_EG20T
 445         tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7213/ML7831) UDC"
 446         depends on PCI && GENERIC_HARDIRQS
 447         help
 448           This is a USB device driver for EG20T PCH.
 449           EG20T PCH is the platform controller hub that is used in Intel's
 450           general embedded platform. EG20T PCH has USB device interface.
 451           Using this interface, it is able to access system devices connected
 452           to USB device.
 453           This driver enables USB device function.
 454           USB device is a USB peripheral controller which
 455           supports both full and high speed USB 2.0 data transfers.
 456           This driver supports both control transfer and bulk transfer modes.
 457           This driver dose not support interrupt transfer or isochronous
 458           transfer modes.
 459
 460           This driver also can be used for LAPIS Semiconductor's ML7213 which is
 461           for IVI(In-Vehicle Infotainment) use.
 462           ML7831 is for general purpose use.
 463           ML7213/ML7831 is companion chip for Intel Atom E6xx series.
 464           ML7213/ML7831 is completely compatible for Intel EG20T PCH.
 465
 466 #
 467 # LAST -- dummy/emulated controller
 468 #
 469
 470 config USB_DUMMY_HCD
 471         tristate "Dummy HCD (DEVELOPMENT)"
 472         depends on USB=y || (USB=m && USB_GADGET=m)
 473         help
 474           This host controller driver emulates USB, looping all data transfer
 475           requests back to a USB "gadget driver" in the same host.  The host
 476           side is the master; the gadget side is the slave.  Gadget drivers
 477           can be high, full, or low speed; and they have access to endpoints
 478           like those from NET2280, PXA2xx, or SA1100 hardware.
 479
 480           This may help in some stages of creating a driver to embed in a
 481           Linux device, since it lets you debug several parts of the gadget
 482           driver without its hardware or drivers being involved.
 483
 484           Since such a gadget side driver needs to interoperate with a host
 485           side Linux-USB device driver, this may help to debug both sides
 486           of a USB protocol stack.
 487
 488           Say "y" to link the driver statically, or "m" to build a
 489           dynamically linked module called "dummy_hcd" and force all
 490           gadget drivers to also be dynamically linked.
 491
 492 # NOTE:  Please keep dummy_hcd LAST so that "real hardware" appears
 493 # first and will be selected by default.
 494
 495 endmenu
 496
 497 #
 498 # USB Gadget Drivers
 499 #
 500
 501 # composite based drivers
 502 config USB_LIBCOMPOSITE
 503         tristate
 504         depends on USB_GADGET
 505
 506 config USB_F_ACM
 507         tristate
 508
 509 config USB_F_SS_LB
 510         tristate
 511
 512 config USB_U_SERIAL
 513         tristate
 514
 515 choice
 516         tristate "USB Gadget Drivers"
 517         default USB_ETH
 518         help
 519           A Linux "Gadget Driver" talks to the USB Peripheral Controller
 520           driver through the abstract "gadget" API.  Some other operating
 521           systems call these "client" drivers, of which "class drivers"
 522           are a subset (implementing a USB device class specification).
 523           A gadget driver implements one or more USB functions using
 524           the peripheral hardware.
 525
 526           Gadget drivers are hardware-neutral, or "platform independent",
 527           except that they sometimes must understand quirks or limitations
 528           of the particular controllers they work with.  For example, when
 529           a controller doesn't support alternate configurations or provide
 530           enough of the right types of endpoints, the gadget driver might
 531           not be able work with that controller, or might need to implement
 532           a less common variant of a device class protocol.
 533
 534 # this first set of drivers all depend on bulk-capable hardware.
 535
 536 config USB_ZERO
 537         tristate "Gadget Zero (DEVELOPMENT)"
 538         select USB_LIBCOMPOSITE
 539         select USB_F_SS_LB
 540         help
 541           Gadget Zero is a two-configuration device.  It either sinks and
 542           sources bulk data; or it loops back a configurable number of
 543           transfers.  It also implements control requests, for "chapter 9"
 544           conformance.  The driver needs only two bulk-capable endpoints, so
 545           it can work on top of most device-side usb controllers.  It's
 546           useful for testing, and is also a working example showing how
 547           USB "gadget drivers" can be written.
 548
 549           Make this be the first driver you try using on top of any new
 550           USB peripheral controller driver.  Then you can use host-side
 551           test software, like the "usbtest" driver, to put your hardware
 552           and its driver through a basic set of functional tests.
 553
 554           Gadget Zero also works with the host-side "usb-skeleton" driver,
 555           and with many kinds of host-side test software.  You may need
 556           to tweak product and vendor IDs before host software knows about
 557           this device, and arrange to select an appropriate configuration.
 558
 559           Say "y" to link the driver statically, or "m" to build a
 560           dynamically linked module called "g_zero".
 561
 562 config USB_ZERO_HNPTEST
 563         boolean "HNP Test Device"
 564         depends on USB_ZERO && USB_OTG
 565         help
 566           You can configure this device to enumerate using the device
 567           identifiers of the USB-OTG test device.  That means that when
 568           this gadget connects to another OTG device, with this one using
 569           the "B-Peripheral" role, that device will use HNP to let this
 570           one serve as the USB host instead (in the "B-Host" role).
 571
 572 config USB_AUDIO
 573         tristate "Audio Gadget"
 574         depends on SND
 575         select USB_LIBCOMPOSITE
 576         select SND_PCM
 577         help
 578           This Gadget Audio driver is compatible with USB Audio Class
 579           specification 2.0. It implements 1 AudioControl interface,
 580           1 AudioStreaming Interface each for USB-OUT and USB-IN.
 581           Number of channels, sample rate and sample size can be
 582           specified as module parameters.
 583           This driver doesn't expect any real Audio codec to be present
 584           on the device - the audio streams are simply sinked to and
 585           sourced from a virtual ALSA sound card created. The user-space
 586           application may choose to do whatever it wants with the data
 587           received from the USB Host and choose to provide whatever it
 588           wants as audio data to the USB Host.
 589
 590           Say "y" to link the driver statically, or "m" to build a
 591           dynamically linked module called "g_audio".
 592
 593 config GADGET_UAC1
 594         bool "UAC 1.0 (Legacy)"
 595         depends on USB_AUDIO
 596         help
 597           If you instead want older UAC Spec-1.0 driver that also has audio
 598           paths hardwired to the Audio codec chip on-board and doesn't work
 599           without one.
 600
 601 config USB_ETH
 602         tristate "Ethernet Gadget (with CDC Ethernet support)"
 603         depends on NET
 604         select USB_LIBCOMPOSITE
 605         select CRC32
 606         help
 607           This driver implements Ethernet style communication, in one of
 608           several ways:
 609
 610            - The "Communication Device Class" (CDC) Ethernet Control Model.
 611              That protocol is often avoided with pure Ethernet adapters, in
 612              favor of simpler vendor-specific hardware, but is widely
 613              supported by firmware for smart network devices.
 614
 615            - On hardware can't implement that protocol, a simple CDC subset
 616              is used, placing fewer demands on USB.
 617
 618            - CDC Ethernet Emulation Model (EEM) is a newer standard that has
 619              a simpler interface that can be used by more USB hardware.
 620
 621           RNDIS support is an additional option, more demanding than than
 622           subset.
 623
 624           Within the USB device, this gadget driver exposes a network device
 625           "usbX", where X depends on what other networking devices you have.
 626           Treat it like a two-node Ethernet link:  host, and gadget.
 627
 628           The Linux-USB host-side "usbnet" driver interoperates with this
 629           driver, so that deep I/O queues can be supported.  On 2.4 kernels,
 630           use "CDCEther" instead, if you're using the CDC option. That CDC
 631           mode should also interoperate with standard CDC Ethernet class
 632           drivers on other host operating systems.
 633
 634           Say "y" to link the driver statically, or "m" to build a
 635           dynamically linked module called "g_ether".
 636
 637 config USB_ETH_RNDIS
 638         bool "RNDIS support"
 639         depends on USB_ETH
 640         select USB_LIBCOMPOSITE
 641         default y
 642         help
 643            Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol,
 644            and Microsoft provides redistributable binary RNDIS drivers for
 645            older versions of Windows.
 646
 647            If you say "y" here, the Ethernet gadget driver will try to provide
 648            a second device configuration, supporting RNDIS to talk to such
 649            Microsoft USB hosts.
 650
 651            To make MS-Windows work with this, use Documentation/usb/linux.inf
 652            as the "driver info file".  For versions of MS-Windows older than
 653            XP, you'll need to download drivers from Microsoft's website; a URL
 654            is given in comments found in that info file.
 655
 656 config USB_ETH_EEM
 657        bool "Ethernet Emulation Model (EEM) support"
 658        depends on USB_ETH
 659         select USB_LIBCOMPOSITE
 660        default n
 661        help
 662          CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM
 663          and therefore can be supported by more hardware.  Technically ECM and
 664          EEM are designed for different applications.  The ECM model extends
 665          the network interface to the target (e.g. a USB cable modem), and the
 666          EEM model is for mobile devices to communicate with hosts using
 667          ethernet over USB.  For Linux gadgets, however, the interface with
 668          the host is the same (a usbX device), so the differences are minimal.
 669
 670          If you say "y" here, the Ethernet gadget driver will use the EEM
 671          protocol rather than ECM.  If unsure, say "n".
 672
 673 config USB_G_NCM
 674         tristate "Network Control Model (NCM) support"
 675         depends on NET
 676         select USB_LIBCOMPOSITE
 677         select CRC32
 678         help
 679           This driver implements USB CDC NCM subclass standard. NCM is
 680           an advanced protocol for Ethernet encapsulation, allows grouping
 681           of several ethernet frames into one USB transfer and different
 682           alignment possibilities.
 683
 684           Say "y" to link the driver statically, or "m" to build a
 685           dynamically linked module called "g_ncm".
 686
 687 config USB_GADGETFS
 688         tristate "Gadget Filesystem"
 689         help
 690           This driver provides a filesystem based API that lets user mode
 691           programs implement a single-configuration USB device, including
 692           endpoint I/O and control requests that don't relate to enumeration.
 693           All endpoints, transfer speeds, and transfer types supported by
 694           the hardware are available, through read() and write() calls.
 695
 696           Say "y" to link the driver statically, or "m" to build a
 697           dynamically linked module called "gadgetfs".
 698
 699 config USB_FUNCTIONFS
 700         tristate "Function Filesystem"
 701         select USB_LIBCOMPOSITE
 702         select USB_FUNCTIONFS_GENERIC if !(USB_FUNCTIONFS_ETH || USB_FUNCTIONFS_RNDIS)
 703         help
 704           The Function Filesystem (FunctionFS) lets one create USB
 705           composite functions in user space in the same way GadgetFS
 706           lets one create USB gadgets in user space.  This allows creation
 707           of composite gadgets such that some of the functions are
 708           implemented in kernel space (for instance Ethernet, serial or
 709           mass storage) and other are implemented in user space.
 710
 711           If you say "y" or "m" here you will be able what kind of
 712           configurations the gadget will provide.
 713
 714           Say "y" to link the driver statically, or "m" to build
 715           a dynamically linked module called "g_ffs".
 716
 717 config USB_FUNCTIONFS_ETH
 718         bool "Include configuration with CDC ECM (Ethernet)"
 719         depends on USB_FUNCTIONFS && NET
 720         help
 721           Include a configuration with CDC ECM function (Ethernet) and the
 722           Function Filesystem.
 723
 724 config USB_FUNCTIONFS_RNDIS
 725         bool "Include configuration with RNDIS (Ethernet)"
 726         depends on USB_FUNCTIONFS && NET
 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_LIBCOMPOSITE
 770         help
 771           The Serial Gadget talks to the Linux-USB generic serial driver.
 772           This driver supports a CDC-ACM module option, which can be used
 773           to interoperate with MS-Windows hosts or with the Linux-USB
 774           "cdc-acm" driver.
 775
 776           This driver also supports a CDC-OBEX option.  You will need a
 777           user space OBEX server talking to /dev/ttyGS*, since the kernel
 778           itself doesn't implement the OBEX protocol.
 779
 780           Say "y" to link the driver statically, or "m" to build a
 781           dynamically linked module called "g_serial".
 782
 783           For more information, see Documentation/usb/gadget_serial.txt
 784           which includes instructions and a "driver info file" needed to
 785           make MS-Windows work with CDC ACM.
 786
 787 config USB_MIDI_GADGET
 788         tristate "MIDI Gadget"
 789         depends on SND
 790         select USB_LIBCOMPOSITE
 791         select SND_RAWMIDI
 792         help
 793           The MIDI Gadget acts as a USB Audio device, with one MIDI
 794           input and one MIDI output. These MIDI jacks appear as
 795           a sound "card" in the ALSA sound system. Other MIDI
 796           connections can then be made on the gadget system, using
 797           ALSA's aconnect utility etc.
 798
 799           Say "y" to link the driver statically, or "m" to build a
 800           dynamically linked module called "g_midi".
 801
 802 config USB_G_PRINTER
 803         tristate "Printer Gadget"
 804         select USB_LIBCOMPOSITE
 805         help
 806           The Printer Gadget channels data between the USB host and a
 807           userspace program driving the print engine. The user space
 808           program reads and writes the device file /dev/g_printer to
 809           receive or send printer data. It can use ioctl calls to
 810           the device file to get or set printer status.
 811
 812           Say "y" to link the driver statically, or "m" to build a
 813           dynamically linked module called "g_printer".
 814
 815           For more information, see Documentation/usb/gadget_printer.txt
 816           which includes sample code for accessing the device file.
 817
 818 if TTY
 819
 820 config USB_CDC_COMPOSITE
 821         tristate "CDC Composite Device (Ethernet and ACM)"
 822         depends on NET
 823         select USB_LIBCOMPOSITE
 824         select USB_U_SERIAL
 825         select USB_F_ACM
 826         help
 827           This driver provides two functions in one configuration:
 828           a CDC Ethernet (ECM) link, and a CDC ACM (serial port) link.
 829
 830           This driver requires four bulk and two interrupt endpoints,
 831           plus the ability to handle altsettings.  Not all peripheral
 832           controllers are that capable.
 833
 834           Say "y" to link the driver statically, or "m" to build a
 835           dynamically linked module.
 836
 837 config USB_G_NOKIA
 838         tristate "Nokia composite gadget"
 839         depends on PHONET
 840         select USB_LIBCOMPOSITE
 841         select USB_U_SERIAL
 842         help
 843           The Nokia composite gadget provides support for acm, obex
 844           and phonet in only one composite gadget driver.
 845
 846           It's only really useful for N900 hardware. If you're building
 847           a kernel for N900, say Y or M here. If unsure, say N.
 848
 849 config USB_G_ACM_MS
 850         tristate "CDC Composite Device (ACM and mass storage)"
 851         depends on BLOCK
 852         select USB_LIBCOMPOSITE
 853         select USB_U_SERIAL
 854         select USB_F_ACM
 855         help
 856           This driver provides two functions in one configuration:
 857           a mass storage, and a CDC ACM (serial port) link.
 858
 859           Say "y" to link the driver statically, or "m" to build a
 860           dynamically linked module called "g_acm_ms".
 861
 862 config USB_G_MULTI
 863         tristate "Multifunction Composite Gadget"
 864         depends on BLOCK && NET
 865         select USB_G_MULTI_CDC if !USB_G_MULTI_RNDIS
 866         select USB_LIBCOMPOSITE
 867         select USB_U_SERIAL
 868         select USB_F_ACM
 869         help
 870           The Multifunction Composite Gadget provides Ethernet (RNDIS
 871           and/or CDC Ethernet), mass storage and ACM serial link
 872           interfaces.
 873
 874           You will be asked to choose which of the two configurations is
 875           to be available in the gadget.  At least one configuration must
 876           be chosen to make the gadget usable.  Selecting more than one
 877           configuration will prevent Windows from automatically detecting
 878           the gadget as a composite gadget, so an INF file will be needed to
 879           use the gadget.
 880
 881           Say "y" to link the driver statically, or "m" to build a
 882           dynamically linked module called "g_multi".
 883
 884 config USB_G_MULTI_RNDIS
 885         bool "RNDIS + CDC Serial + Storage configuration"
 886         depends on USB_G_MULTI
 887         default y
 888         help
 889           This option enables a configuration with RNDIS, CDC Serial and
 890           Mass Storage functions available in the Multifunction Composite
 891           Gadget.  This is the configuration dedicated for Windows since RNDIS
 892           is Microsoft's protocol.
 893
 894           If unsure, say "y".
 895
 896 config USB_G_MULTI_CDC
 897         bool "CDC Ethernet + CDC Serial + Storage configuration"
 898         depends on USB_G_MULTI
 899         default n
 900         help
 901           This option enables a configuration with CDC Ethernet (ECM), CDC
 902           Serial and Mass Storage functions available in the Multifunction
 903           Composite Gadget.
 904
 905           If unsure, say "y".
 906
 907 endif # TTY
 908
 909 config USB_G_HID
 910         tristate "HID Gadget"
 911         select USB_LIBCOMPOSITE
 912         help
 913           The HID gadget driver provides generic emulation of USB
 914           Human Interface Devices (HID).
 915
 916           For more information, see Documentation/usb/gadget_hid.txt which
 917           includes sample code for accessing the device files.
 918
 919           Say "y" to link the driver statically, or "m" to build a
 920           dynamically linked module called "g_hid".
 921
 922 # Standalone / single function gadgets
 923 config USB_G_DBGP
 924         tristate "EHCI Debug Device Gadget"
 925         depends on TTY
 926         select USB_LIBCOMPOSITE
 927         help
 928           This gadget emulates an EHCI Debug device. This is useful when you want
 929           to interact with an EHCI Debug Port.
 930
 931           Say "y" to link the driver statically, or "m" to build a
 932           dynamically linked module called "g_dbgp".
 933
 934 if USB_G_DBGP
 935 choice
 936         prompt "EHCI Debug Device mode"
 937         default USB_G_DBGP_SERIAL
 938
 939 config USB_G_DBGP_PRINTK
 940         depends on USB_G_DBGP
 941         bool "printk"
 942         help
 943           Directly printk() received data. No interaction.
 944
 945 config USB_G_DBGP_SERIAL
 946         depends on USB_G_DBGP
 947         select USB_U_SERIAL
 948         bool "serial"
 949         help
 950           Userland can interact using /dev/ttyGSxxx.
 951 endchoice
 952 endif
 953
 954 # put drivers that need isochronous transfer support (for audio
 955 # or video class gadget drivers), or specific hardware, here.
 956 config USB_G_WEBCAM
 957         tristate "USB Webcam Gadget"
 958         depends on VIDEO_DEV
 959         select USB_LIBCOMPOSITE
 960         help
 961           The Webcam Gadget acts as a composite USB Audio and Video Class
 962           device. It provides a userspace API to process UVC control requests
 963           and stream video data to the host.
 964
 965           Say "y" to link the driver statically, or "m" to build a
 966           dynamically linked module called "g_webcam".
 967
 968 endchoice
 969
 970 endif # USB_GADGET