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_VERBOSE
  62         bool "Verbose debugging Messages (DEVELOPMENT)"
  63         depends on USB_GADGET_DEBUG
  64         help
  65            Many controller and gadget drivers will print verbose debugging
  66            messages if you use this option to ask for those messages.
  67
  68            Avoid enabling these messages, even if you're actively
  69            debugging such a driver.  Many drivers will emit so many
  70            messages that the driver timings are affected, which will
  71            either create new failure modes or remove the one you're
  72            trying to track down.  Never enable these messages for a
  73            production build.
  74
  75 config USB_GADGET_DEBUG_FILES
  76         boolean "Debugging information files (DEVELOPMENT)"
  77         depends on PROC_FS
  78         help
  79            Some of the drivers in the "gadget" framework can expose
  80            debugging information in files such as /proc/driver/udc
  81            (for a peripheral controller).  The information in these
  82            files may help when you're troubleshooting or bringing up a
  83            driver on a new board.   Enable these files by choosing "Y"
  84            here.  If in doubt, or to conserve kernel memory, say "N".
  85
  86 config USB_GADGET_DEBUG_FS
  87         boolean "Debugging information files in debugfs (DEVELOPMENT)"
  88         depends on DEBUG_FS
  89         help
  90            Some of the drivers in the "gadget" framework can expose
  91            debugging information in files under /sys/kernel/debug/.
  92            The information in these files may help when you're
  93            troubleshooting or bringing up a driver on a new board.
  94            Enable these files by choosing "Y" here.  If in doubt, or
  95            to conserve kernel memory, say "N".
  96
  97 config USB_GADGET_VBUS_DRAW
  98         int "Maximum VBUS Power usage (2-500 mA)"
  99         range 2 500
 100         default 2
 101         help
 102            Some devices need to draw power from USB when they are
 103            configured, perhaps to operate circuitry or to recharge
 104            batteries.  This is in addition to any local power supply,
 105            such as an AC adapter or batteries.
 106
 107            Enter the maximum power your device draws through USB, in
 108            milliAmperes.  The permitted range of values is 2 - 500 mA;
 109            0 mA would be legal, but can make some hosts misbehave.
 110
 111            This value will be used except for system-specific gadget
 112            drivers that have more specific information.
 113
 114 config USB_GADGET_STORAGE_NUM_BUFFERS
 115         int "Number of storage pipeline buffers"
 116         range 2 4
 117         default 2
 118         help
 119            Usually 2 buffers are enough to establish a good buffering
 120            pipeline. The number may be increased in order to compensate
 121            for a bursty VFS behaviour. For instance there may be CPU wake up
 122            latencies that makes the VFS to appear bursty in a system with
 123            an CPU on-demand governor. Especially if DMA is doing IO to
 124            offload the CPU. In this case the CPU will go into power
 125            save often and spin up occasionally to move data within VFS.
 126            If selecting USB_GADGET_DEBUG_FILES this value may be set by
 127            a module parameter as well.
 128            If unsure, say 2.
 129
 130 #
 131 # USB Peripheral Controller Support
 132 #
 133 # The order here is alphabetical, except that integrated controllers go
 134 # before discrete ones so they will be the initial/default value:
 135 #   - integrated/SOC controllers first
 136 #   - licensed IP used in both SOC and discrete versions
 137 #   - discrete ones (including all PCI-only controllers)
 138 #   - debug/dummy gadget+hcd is last.
 139 #
 140 menu "USB Peripheral Controller"
 141
 142 #
 143 # Integrated controllers
 144 #
 145
 146 config USB_AT91
 147         tristate "Atmel AT91 USB Device Port"
 148         depends on ARCH_AT91
 149         help
 150            Many Atmel AT91 processors (such as the AT91RM2000) have a
 151            full speed USB Device Port with support for five configurable
 152            endpoints (plus endpoint zero).
 153
 154            Say "y" to link the driver statically, or "m" to build a
 155            dynamically linked module called "at91_udc" and force all
 156            gadget drivers to also be dynamically linked.
 157
 158 config USB_LPC32XX
 159         tristate "LPC32XX USB Peripheral Controller"
 160         depends on ARCH_LPC32XX
 161         select USB_ISP1301
 162         help
 163            This option selects the USB device controller in the LPC32xx SoC.
 164
 165            Say "y" to link the driver statically, or "m" to build a
 166            dynamically linked module called "lpc32xx_udc" and force all
 167            gadget drivers to also be dynamically linked.
 168
 169 config USB_ATMEL_USBA
 170         tristate "Atmel USBA"
 171         depends on AVR32 || ARCH_AT91
 172         help
 173           USBA is the integrated high-speed USB Device controller on
 174           the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel.
 175
 176 config USB_BCM63XX_UDC
 177         tristate "Broadcom BCM63xx Peripheral Controller"
 178         depends on BCM63XX
 179         help
 180            Many Broadcom BCM63xx chipsets (such as the BCM6328) have a
 181            high speed USB Device Port with support for four fixed endpoints
 182            (plus endpoint zero).
 183
 184            Say "y" to link the driver statically, or "m" to build a
 185            dynamically linked module called "bcm63xx_udc".
 186
 187 config USB_FSL_USB2
 188         tristate "Freescale Highspeed USB DR Peripheral Controller"
 189         depends on FSL_SOC || ARCH_MXC
 190         select USB_FSL_MPH_DR_OF if OF
 191         help
 192            Some of Freescale PowerPC and i.MX processors have a High Speed
 193            Dual-Role(DR) USB controller, which supports device mode.
 194
 195            The number of programmable endpoints is different through
 196            SOC revisions.
 197
 198            Say "y" to link the driver statically, or "m" to build a
 199            dynamically linked module called "fsl_usb2_udc" and force
 200            all gadget drivers to also be dynamically linked.
 201
 202 config USB_FUSB300
 203         tristate "Faraday FUSB300 USB Peripheral Controller"
 204         depends on !PHYS_ADDR_T_64BIT && HAS_DMA
 205         help
 206            Faraday usb device controller FUSB300 driver
 207
 208 config USB_FOTG210_UDC
 209         depends on HAS_DMA
 210         tristate "Faraday FOTG210 USB Peripheral Controller"
 211         help
 212            Faraday USB2.0 OTG controller which can be configured as
 213            high speed or full speed USB device. This driver supppors
 214            Bulk Transfer so far.
 215
 216            Say "y" to link the driver statically, or "m" to build a
 217            dynamically linked module called "fotg210_udc".
 218
 219 config USB_GR_UDC
 220        tristate "Aeroflex Gaisler GRUSBDC USB Peripheral Controller Driver"
 221        depends on HAS_DMA
 222        help
 223           Select this to support Aeroflex Gaisler GRUSBDC cores from the GRLIB
 224           VHDL IP core library.
 225
 226 config USB_OMAP
 227         tristate "OMAP USB Device Controller"
 228         depends on ARCH_OMAP1
 229         select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_H4_OTG
 230         help
 231            Many Texas Instruments OMAP processors have flexible full
 232            speed USB device controllers, with support for up to 30
 233            endpoints (plus endpoint zero).  This driver supports the
 234            controller in the OMAP 1611, and should work with controllers
 235            in other OMAP processors too, given minor tweaks.
 236
 237            Say "y" to link the driver statically, or "m" to build a
 238            dynamically linked module called "omap_udc" and force all
 239            gadget drivers to also be dynamically linked.
 240
 241 config USB_PXA25X
 242         tristate "PXA 25x or IXP 4xx"
 243         depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX
 244         help
 245            Intel's PXA 25x series XScale ARM-5TE processors include
 246            an integrated full speed USB 1.1 device controller.  The
 247            controller in the IXP 4xx series is register-compatible.
 248
 249            It has fifteen fixed-function endpoints, as well as endpoint
 250            zero (for control transfers).
 251
 252            Say "y" to link the driver statically, or "m" to build a
 253            dynamically linked module called "pxa25x_udc" and force all
 254            gadget drivers to also be dynamically linked.
 255
 256 # if there's only one gadget driver, using only two bulk endpoints,
 257 # don't waste memory for the other endpoints
 258 config USB_PXA25X_SMALL
 259         depends on USB_PXA25X
 260         bool
 261         default n if USB_ETH_RNDIS
 262         default y if USB_ZERO
 263         default y if USB_ETH
 264         default y if USB_G_SERIAL
 265
 266 config USB_R8A66597
 267         tristate "Renesas R8A66597 USB Peripheral Controller"
 268         depends on HAS_DMA
 269         help
 270            R8A66597 is a discrete USB host and peripheral controller chip that
 271            supports both full and high speed USB 2.0 data transfers.
 272            It has nine configurable endpoints, and endpoint zero.
 273
 274            Say "y" to link the driver statically, or "m" to build a
 275            dynamically linked module called "r8a66597_udc" and force all
 276            gadget drivers to also be dynamically linked.
 277
 278 config USB_RENESAS_USBHS_UDC
 279         tristate 'Renesas USBHS controller'
 280         depends on USB_RENESAS_USBHS
 281         help
 282            Renesas USBHS is a discrete USB host and peripheral controller chip
 283            that supports both full and high speed USB 2.0 data transfers.
 284            It has nine or more configurable endpoints, and endpoint zero.
 285
 286            Say "y" to link the driver statically, or "m" to build a
 287            dynamically linked module called "renesas_usbhs" and force all
 288            gadget drivers to also be dynamically linked.
 289
 290 config USB_PXA27X
 291         tristate "PXA 27x"
 292         help
 293            Intel's PXA 27x series XScale ARM v5TE processors include
 294            an integrated full speed USB 1.1 device controller.
 295
 296            It has up to 23 endpoints, as well as endpoint zero (for
 297            control transfers).
 298
 299            Say "y" to link the driver statically, or "m" to build a
 300            dynamically linked module called "pxa27x_udc" and force all
 301            gadget drivers to also be dynamically linked.
 302
 303 config USB_S3C_HSOTG
 304         depends on ARM
 305         tristate "Designware/S3C HS/OtG USB Device controller"
 306         help
 307           The Designware USB2.0 high-speed gadget controller
 308           integrated into many SoCs.
 309
 310 config USB_S3C2410
 311         tristate "S3C2410 USB Device Controller"
 312         depends on ARCH_S3C24XX
 313         help
 314           Samsung's S3C2410 is an ARM-4 processor with an integrated
 315           full speed USB 1.1 device controller.  It has 4 configurable
 316           endpoints, as well as endpoint zero (for control transfers).
 317
 318           This driver has been tested on the S3C2410, S3C2412, and
 319           S3C2440 processors.
 320
 321 config USB_S3C2410_DEBUG
 322         boolean "S3C2410 udc debug messages"
 323         depends on USB_S3C2410
 324
 325 config USB_S3C_HSUDC
 326         tristate "S3C2416, S3C2443 and S3C2450 USB Device Controller"
 327         depends on ARCH_S3C24XX
 328         help
 329           Samsung's S3C2416, S3C2443 and S3C2450 is an ARM9 based SoC
 330           integrated with dual speed USB 2.0 device controller. It has
 331           8 endpoints, as well as endpoint zero.
 332
 333           This driver has been tested on S3C2416 and S3C2450 processors.
 334
 335 config USB_MV_UDC
 336         tristate "Marvell USB2.0 Device Controller"
 337         depends on HAS_DMA
 338         help
 339           Marvell Socs (including PXA and MMP series) include a high speed
 340           USB2.0 OTG controller, which can be configured as high speed or
 341           full speed USB peripheral.
 342
 343 config USB_MV_U3D
 344         depends on HAS_DMA
 345         tristate "MARVELL PXA2128 USB 3.0 controller"
 346         help
 347           MARVELL PXA2128 Processor series include a super speed USB3.0 device
 348           controller, which support super speed USB peripheral.
 349
 350 #
 351 # Controllers available in both integrated and discrete versions
 352 #
 353
 354 config USB_M66592
 355         tristate "Renesas M66592 USB Peripheral Controller"
 356         help
 357            M66592 is a discrete USB peripheral controller chip that
 358            supports both full and high speed USB 2.0 data transfers.
 359            It has seven configurable endpoints, and endpoint zero.
 360
 361            Say "y" to link the driver statically, or "m" to build a
 362            dynamically linked module called "m66592_udc" and force all
 363            gadget drivers to also be dynamically linked.
 364
 365 #
 366 # Controllers available only in discrete form (and all PCI controllers)
 367 #
 368
 369 config USB_AMD5536UDC
 370         tristate "AMD5536 UDC"
 371         depends on PCI
 372         help
 373            The AMD5536 UDC is part of the AMD Geode CS5536, an x86 southbridge.
 374            It is a USB Highspeed DMA capable USB device controller. Beside ep0
 375            it provides 4 IN and 4 OUT endpoints (bulk or interrupt type).
 376            The UDC port supports OTG operation, and may be used as a host port
 377            if it's not being used to implement peripheral or OTG roles.
 378
 379            Say "y" to link the driver statically, or "m" to build a
 380            dynamically linked module called "amd5536udc" and force all
 381            gadget drivers to also be dynamically linked.
 382
 383 config USB_FSL_QE
 384         tristate "Freescale QE/CPM USB Device Controller"
 385         depends on FSL_SOC && (QUICC_ENGINE || CPM)
 386         help
 387            Some of Freescale PowerPC processors have a Full Speed
 388            QE/CPM2 USB controller, which support device mode with 4
 389            programmable endpoints. This driver supports the
 390            controller in the MPC8360 and MPC8272, and should work with
 391            controllers having QE or CPM2, given minor tweaks.
 392
 393            Set CONFIG_USB_GADGET to "m" to build this driver as a
 394            dynamically linked module called "fsl_qe_udc".
 395
 396 config USB_NET2272
 397         tristate "PLX NET2272"
 398         help
 399           PLX NET2272 is a USB peripheral controller which supports
 400           both full and high speed USB 2.0 data transfers.
 401
 402           It has three configurable endpoints, as well as endpoint zero
 403           (for control transfer).
 404           Say "y" to link the driver statically, or "m" to build a
 405           dynamically linked module called "net2272" and force all
 406           gadget drivers to also be dynamically linked.
 407
 408 config USB_NET2272_DMA
 409         boolean "Support external DMA controller"
 410         depends on USB_NET2272 && HAS_DMA
 411         help
 412           The NET2272 part can optionally support an external DMA
 413           controller, but your board has to have support in the
 414           driver itself.
 415
 416           If unsure, say "N" here.  The driver works fine in PIO mode.
 417
 418 config USB_NET2280
 419         tristate "NetChip 228x"
 420         depends on PCI
 421         help
 422            NetChip 2280 / 2282 is a PCI based USB peripheral controller which
 423            supports both full and high speed USB 2.0 data transfers.
 424
 425            It has six configurable endpoints, as well as endpoint zero
 426            (for control transfers) and several endpoints with dedicated
 427            functions.
 428
 429            Say "y" to link the driver statically, or "m" to build a
 430            dynamically linked module called "net2280" and force all
 431            gadget drivers to also be dynamically linked.
 432
 433 config USB_GOKU
 434         tristate "Toshiba TC86C001 'Goku-S'"
 435         depends on PCI
 436         help
 437            The Toshiba TC86C001 is a PCI device which includes controllers
 438            for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI).
 439
 440            The device controller has three configurable (bulk or interrupt)
 441            endpoints, plus endpoint zero (for control transfers).
 442
 443            Say "y" to link the driver statically, or "m" to build a
 444            dynamically linked module called "goku_udc" and to force all
 445            gadget drivers to also be dynamically linked.
 446
 447 config USB_EG20T
 448         tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7213/ML7831) UDC"
 449         depends on PCI
 450         help
 451           This is a USB device driver for EG20T PCH.
 452           EG20T PCH is the platform controller hub that is used in Intel's
 453           general embedded platform. EG20T PCH has USB device interface.
 454           Using this interface, it is able to access system devices connected
 455           to USB device.
 456           This driver enables USB device function.
 457           USB device is a USB peripheral controller which
 458           supports both full and high speed USB 2.0 data transfers.
 459           This driver supports both control transfer and bulk transfer modes.
 460           This driver dose not support interrupt transfer or isochronous
 461           transfer modes.
 462
 463           This driver also can be used for LAPIS Semiconductor's ML7213 which is
 464           for IVI(In-Vehicle Infotainment) use.
 465           ML7831 is for general purpose use.
 466           ML7213/ML7831 is companion chip for Intel Atom E6xx series.
 467           ML7213/ML7831 is completely compatible for Intel EG20T PCH.
 468
 469 #
 470 # LAST -- dummy/emulated controller
 471 #
 472
 473 config USB_DUMMY_HCD
 474         tristate "Dummy HCD (DEVELOPMENT)"
 475         depends on USB=y || (USB=m && USB_GADGET=m)
 476         help
 477           This host controller driver emulates USB, looping all data transfer
 478           requests back to a USB "gadget driver" in the same host.  The host
 479           side is the master; the gadget side is the slave.  Gadget drivers
 480           can be high, full, or low speed; and they have access to endpoints
 481           like those from NET2280, PXA2xx, or SA1100 hardware.
 482
 483           This may help in some stages of creating a driver to embed in a
 484           Linux device, since it lets you debug several parts of the gadget
 485           driver without its hardware or drivers being involved.
 486
 487           Since such a gadget side driver needs to interoperate with a host
 488           side Linux-USB device driver, this may help to debug both sides
 489           of a USB protocol stack.
 490
 491           Say "y" to link the driver statically, or "m" to build a
 492           dynamically linked module called "dummy_hcd" and force all
 493           gadget drivers to also be dynamically linked.
 494
 495 # NOTE:  Please keep dummy_hcd LAST so that "real hardware" appears
 496 # first and will be selected by default.
 497
 498 endmenu
 499
 500 #
 501 # USB Gadget Drivers
 502 #
 503
 504 # composite based drivers
 505 config USB_LIBCOMPOSITE
 506         tristate
 507         select CONFIGFS_FS
 508         depends on USB_GADGET
 509
 510 config USB_F_ACM
 511         tristate
 512
 513 config USB_F_SS_LB
 514         tristate
 515
 516 config USB_U_SERIAL
 517         tristate
 518
 519 config USB_U_ETHER
 520         tristate
 521
 522 config USB_F_SERIAL
 523         tristate
 524
 525 config USB_F_OBEX
 526         tristate
 527
 528 config USB_F_NCM
 529         tristate
 530
 531 config USB_F_ECM
 532         tristate
 533
 534 config USB_F_PHONET
 535         tristate
 536
 537 config USB_F_EEM
 538         tristate
 539
 540 config USB_F_SUBSET
 541         tristate
 542
 543 config USB_F_RNDIS
 544         tristate
 545
 546 config USB_F_MASS_STORAGE
 547         tristate
 548
 549 config USB_F_FS
 550         tristate
 551
 552 choice
 553         tristate "USB Gadget Drivers"
 554         default USB_ETH
 555         help
 556           A Linux "Gadget Driver" talks to the USB Peripheral Controller
 557           driver through the abstract "gadget" API.  Some other operating
 558           systems call these "client" drivers, of which "class drivers"
 559           are a subset (implementing a USB device class specification).
 560           A gadget driver implements one or more USB functions using
 561           the peripheral hardware.
 562
 563           Gadget drivers are hardware-neutral, or "platform independent",
 564           except that they sometimes must understand quirks or limitations
 565           of the particular controllers they work with.  For example, when
 566           a controller doesn't support alternate configurations or provide
 567           enough of the right types of endpoints, the gadget driver might
 568           not be able work with that controller, or might need to implement
 569           a less common variant of a device class protocol.
 570
 571 # this first set of drivers all depend on bulk-capable hardware.
 572
 573 config USB_CONFIGFS
 574         tristate "USB functions configurable through configfs"
 575         select USB_LIBCOMPOSITE
 576         help
 577           A Linux USB "gadget" can be set up through configfs.
 578           If this is the case, the USB functions (which from the host's
 579           perspective are seen as interfaces) and configurations are
 580           specified simply by creating appropriate directories in configfs.
 581           Associating functions with configurations is done by creating
 582           appropriate symbolic links.
 583           For more information see Documentation/usb/gadget_configfs.txt.
 584
 585 config USB_CONFIGFS_SERIAL
 586         boolean "Generic serial bulk in/out"
 587         depends on USB_CONFIGFS
 588         depends on TTY
 589         select USB_U_SERIAL
 590         select USB_F_SERIAL
 591         help
 592           The function talks to the Linux-USB generic serial driver.
 593
 594 config USB_CONFIGFS_ACM
 595         boolean "Abstract Control Model (CDC ACM)"
 596         depends on USB_CONFIGFS
 597         depends on TTY
 598         select USB_U_SERIAL
 599         select USB_F_ACM
 600         help
 601           ACM serial link.  This function can be used to interoperate with
 602           MS-Windows hosts or with the Linux-USB "cdc-acm" driver.
 603
 604 config USB_CONFIGFS_OBEX
 605         boolean "Object Exchange Model (CDC OBEX)"
 606         depends on USB_CONFIGFS
 607         depends on TTY
 608         select USB_U_SERIAL
 609         select USB_F_OBEX
 610         help
 611           You will need a user space OBEX server talking to /dev/ttyGS*,
 612           since the kernel itself doesn't implement the OBEX protocol.
 613
 614 config USB_CONFIGFS_NCM
 615         boolean "Network Control Model (CDC NCM)"
 616         depends on USB_CONFIGFS
 617         depends on NET
 618         select USB_U_ETHER
 619         select USB_F_NCM
 620         help
 621           NCM is an advanced protocol for Ethernet encapsulation, allows
 622           grouping of several ethernet frames into one USB transfer and
 623           different alignment possibilities.
 624
 625 config USB_CONFIGFS_ECM
 626         boolean "Ethernet Control Model (CDC ECM)"
 627         depends on USB_CONFIGFS
 628         depends on NET
 629         select USB_U_ETHER
 630         select USB_F_ECM
 631         help
 632           The "Communication Device Class" (CDC) Ethernet Control Model.
 633           That protocol is often avoided with pure Ethernet adapters, in
 634           favor of simpler vendor-specific hardware, but is widely
 635           supported by firmware for smart network devices.
 636
 637 config USB_CONFIGFS_ECM_SUBSET
 638         boolean "Ethernet Control Model (CDC ECM) subset"
 639         depends on USB_CONFIGFS
 640         depends on NET
 641         select USB_U_ETHER
 642         select USB_F_SUBSET
 643         help
 644           On hardware that can't implement the full protocol,
 645           a simple CDC subset is used, placing fewer demands on USB.
 646
 647 config USB_CONFIGFS_RNDIS
 648         bool "RNDIS"
 649         depends on USB_CONFIGFS
 650         depends on NET
 651         select USB_U_ETHER
 652         select USB_F_RNDIS
 653         help
 654            Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol,
 655            and Microsoft provides redistributable binary RNDIS drivers for
 656            older versions of Windows.
 657
 658            To make MS-Windows work with this, use Documentation/usb/linux.inf
 659            as the "driver info file".  For versions of MS-Windows older than
 660            XP, you'll need to download drivers from Microsoft's website; a URL
 661            is given in comments found in that info file.
 662
 663 config USB_CONFIGFS_EEM
 664         bool "Ethernet Emulation Model (EEM)"
 665         depends on USB_CONFIGFS
 666         depends on NET
 667         select USB_U_ETHER
 668         select USB_F_EEM
 669         help
 670           CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM
 671           and therefore can be supported by more hardware.  Technically ECM and
 672           EEM are designed for different applications.  The ECM model extends
 673           the network interface to the target (e.g. a USB cable modem), and the
 674           EEM model is for mobile devices to communicate with hosts using
 675           ethernet over USB.  For Linux gadgets, however, the interface with
 676           the host is the same (a usbX device), so the differences are minimal.
 677
 678 config USB_CONFIGFS_PHONET
 679         boolean "Phonet protocol"
 680         depends on USB_CONFIGFS
 681         depends on NET
 682         depends on PHONET
 683         select USB_U_ETHER
 684         select USB_F_PHONET
 685         help
 686           The Phonet protocol implementation for USB device.
 687
 688 config USB_CONFIGFS_MASS_STORAGE
 689         boolean "Mass storage"
 690         depends on USB_CONFIGFS
 691         depends on BLOCK
 692         select USB_F_MASS_STORAGE
 693         help
 694           The Mass Storage Gadget acts as a USB Mass Storage disk drive.
 695           As its storage repository it can use a regular file or a block
 696           device (in much the same way as the "loop" device driver),
 697           specified as a module parameter or sysfs option.
 698
 699 config USB_CONFIGFS_F_LB_SS
 700         boolean "Loopback and sourcesink function (for testing)"
 701         depends on USB_CONFIGFS
 702         select USB_F_SS_LB
 703         help
 704           Loopback function loops back a configurable number of transfers.
 705           Sourcesink function either sinks and sources bulk data.
 706           It also implements control requests, for "chapter 9" conformance.
 707           Make this be the first driver you try using on top of any new
 708           USB peripheral controller driver.  Then you can use host-side
 709           test software, like the "usbtest" driver, to put your hardware
 710           and its driver through a basic set of functional tests.
 711
 712 config USB_CONFIGFS_F_FS
 713         boolean "Function filesystem (FunctionFS)"
 714         depends on USB_CONFIGFS
 715         select USB_F_FS
 716         help
 717           The Function Filesystem (FunctionFS) lets one create USB
 718           composite functions in user space in the same way GadgetFS
 719           lets one create USB gadgets in user space.  This allows creation
 720           of composite gadgets such that some of the functions are
 721           implemented in kernel space (for instance Ethernet, serial or
 722           mass storage) and other are implemented in user space.
 723
 724 config USB_ZERO
 725         tristate "Gadget Zero (DEVELOPMENT)"
 726         select USB_LIBCOMPOSITE
 727         select USB_F_SS_LB
 728         help
 729           Gadget Zero is a two-configuration device.  It either sinks and
 730           sources bulk data; or it loops back a configurable number of
 731           transfers.  It also implements control requests, for "chapter 9"
 732           conformance.  The driver needs only two bulk-capable endpoints, so
 733           it can work on top of most device-side usb controllers.  It's
 734           useful for testing, and is also a working example showing how
 735           USB "gadget drivers" can be written.
 736
 737           Make this be the first driver you try using on top of any new
 738           USB peripheral controller driver.  Then you can use host-side
 739           test software, like the "usbtest" driver, to put your hardware
 740           and its driver through a basic set of functional tests.
 741
 742           Gadget Zero also works with the host-side "usb-skeleton" driver,
 743           and with many kinds of host-side test software.  You may need
 744           to tweak product and vendor IDs before host software knows about
 745           this device, and arrange to select an appropriate configuration.
 746
 747           Say "y" to link the driver statically, or "m" to build a
 748           dynamically linked module called "g_zero".
 749
 750 config USB_ZERO_HNPTEST
 751         boolean "HNP Test Device"
 752         depends on USB_ZERO && USB_OTG
 753         help
 754           You can configure this device to enumerate using the device
 755           identifiers of the USB-OTG test device.  That means that when
 756           this gadget connects to another OTG device, with this one using
 757           the "B-Peripheral" role, that device will use HNP to let this
 758           one serve as the USB host instead (in the "B-Host" role).
 759
 760 config USB_AUDIO
 761         tristate "Audio Gadget"
 762         depends on SND
 763         select USB_LIBCOMPOSITE
 764         select SND_PCM
 765         help
 766           This Gadget Audio driver is compatible with USB Audio Class
 767           specification 2.0. It implements 1 AudioControl interface,
 768           1 AudioStreaming Interface each for USB-OUT and USB-IN.
 769           Number of channels, sample rate and sample size can be
 770           specified as module parameters.
 771           This driver doesn't expect any real Audio codec to be present
 772           on the device - the audio streams are simply sinked to and
 773           sourced from a virtual ALSA sound card created. The user-space
 774           application may choose to do whatever it wants with the data
 775           received from the USB Host and choose to provide whatever it
 776           wants as audio data to the USB Host.
 777
 778           Say "y" to link the driver statically, or "m" to build a
 779           dynamically linked module called "g_audio".
 780
 781 config GADGET_UAC1
 782         bool "UAC 1.0 (Legacy)"
 783         depends on USB_AUDIO
 784         help
 785           If you instead want older UAC Spec-1.0 driver that also has audio
 786           paths hardwired to the Audio codec chip on-board and doesn't work
 787           without one.
 788
 789 config USB_ETH
 790         tristate "Ethernet Gadget (with CDC Ethernet support)"
 791         depends on NET
 792         select USB_LIBCOMPOSITE
 793         select USB_U_ETHER
 794         select USB_F_ECM
 795         select USB_F_SUBSET
 796         select CRC32
 797         help
 798           This driver implements Ethernet style communication, in one of
 799           several ways:
 800
 801            - The "Communication Device Class" (CDC) Ethernet Control Model.
 802              That protocol is often avoided with pure Ethernet adapters, in
 803              favor of simpler vendor-specific hardware, but is widely
 804              supported by firmware for smart network devices.
 805
 806            - On hardware can't implement that protocol, a simple CDC subset
 807              is used, placing fewer demands on USB.
 808
 809            - CDC Ethernet Emulation Model (EEM) is a newer standard that has
 810              a simpler interface that can be used by more USB hardware.
 811
 812           RNDIS support is an additional option, more demanding than than
 813           subset.
 814
 815           Within the USB device, this gadget driver exposes a network device
 816           "usbX", where X depends on what other networking devices you have.
 817           Treat it like a two-node Ethernet link:  host, and gadget.
 818
 819           The Linux-USB host-side "usbnet" driver interoperates with this
 820           driver, so that deep I/O queues can be supported.  On 2.4 kernels,
 821           use "CDCEther" instead, if you're using the CDC option. That CDC
 822           mode should also interoperate with standard CDC Ethernet class
 823           drivers on other host operating systems.
 824
 825           Say "y" to link the driver statically, or "m" to build a
 826           dynamically linked module called "g_ether".
 827
 828 config USB_ETH_RNDIS
 829         bool "RNDIS support"
 830         depends on USB_ETH
 831         select USB_LIBCOMPOSITE
 832         select USB_F_RNDIS
 833         default y
 834         help
 835            Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol,
 836            and Microsoft provides redistributable binary RNDIS drivers for
 837            older versions of Windows.
 838
 839            If you say "y" here, the Ethernet gadget driver will try to provide
 840            a second device configuration, supporting RNDIS to talk to such
 841            Microsoft USB hosts.
 842
 843            To make MS-Windows work with this, use Documentation/usb/linux.inf
 844            as the "driver info file".  For versions of MS-Windows older than
 845            XP, you'll need to download drivers from Microsoft's website; a URL
 846            is given in comments found in that info file.
 847
 848 config USB_ETH_EEM
 849        bool "Ethernet Emulation Model (EEM) support"
 850        depends on USB_ETH
 851         select USB_LIBCOMPOSITE
 852         select USB_F_EEM
 853        default n
 854        help
 855          CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM
 856          and therefore can be supported by more hardware.  Technically ECM and
 857          EEM are designed for different applications.  The ECM model extends
 858          the network interface to the target (e.g. a USB cable modem), and the
 859          EEM model is for mobile devices to communicate with hosts using
 860          ethernet over USB.  For Linux gadgets, however, the interface with
 861          the host is the same (a usbX device), so the differences are minimal.
 862
 863          If you say "y" here, the Ethernet gadget driver will use the EEM
 864          protocol rather than ECM.  If unsure, say "n".
 865
 866 config USB_G_NCM
 867         tristate "Network Control Model (NCM) support"
 868         depends on NET
 869         select USB_LIBCOMPOSITE
 870         select USB_U_ETHER
 871         select USB_F_NCM
 872         select CRC32
 873         help
 874           This driver implements USB CDC NCM subclass standard. NCM is
 875           an advanced protocol for Ethernet encapsulation, allows grouping
 876           of several ethernet frames into one USB transfer and different
 877           alignment possibilities.
 878
 879           Say "y" to link the driver statically, or "m" to build a
 880           dynamically linked module called "g_ncm".
 881
 882 config USB_GADGETFS
 883         tristate "Gadget Filesystem"
 884         help
 885           This driver provides a filesystem based API that lets user mode
 886           programs implement a single-configuration USB device, including
 887           endpoint I/O and control requests that don't relate to enumeration.
 888           All endpoints, transfer speeds, and transfer types supported by
 889           the hardware are available, through read() and write() calls.
 890
 891           Say "y" to link the driver statically, or "m" to build a
 892           dynamically linked module called "gadgetfs".
 893
 894 config USB_FUNCTIONFS
 895         tristate "Function Filesystem"
 896         select USB_LIBCOMPOSITE
 897         select USB_F_FS
 898         select USB_FUNCTIONFS_GENERIC if !(USB_FUNCTIONFS_ETH || USB_FUNCTIONFS_RNDIS)
 899         help
 900           The Function Filesystem (FunctionFS) lets one create USB
 901           composite functions in user space in the same way GadgetFS
 902           lets one create USB gadgets in user space.  This allows creation
 903           of composite gadgets such that some of the functions are
 904           implemented in kernel space (for instance Ethernet, serial or
 905           mass storage) and other are implemented in user space.
 906
 907           If you say "y" or "m" here you will be able what kind of
 908           configurations the gadget will provide.
 909
 910           Say "y" to link the driver statically, or "m" to build
 911           a dynamically linked module called "g_ffs".
 912
 913 config USB_FUNCTIONFS_ETH
 914         bool "Include configuration with CDC ECM (Ethernet)"
 915         depends on USB_FUNCTIONFS && NET
 916         select USB_U_ETHER
 917         select USB_F_ECM
 918         select USB_F_SUBSET
 919         help
 920           Include a configuration with CDC ECM function (Ethernet) and the
 921           Function Filesystem.
 922
 923 config USB_FUNCTIONFS_RNDIS
 924         bool "Include configuration with RNDIS (Ethernet)"
 925         depends on USB_FUNCTIONFS && NET
 926         select USB_U_ETHER
 927         select USB_F_RNDIS
 928         help
 929           Include a configuration with RNDIS function (Ethernet) and the Filesystem.
 930
 931 config USB_FUNCTIONFS_GENERIC
 932         bool "Include 'pure' configuration"
 933         depends on USB_FUNCTIONFS
 934         help
 935           Include a configuration with the Function Filesystem alone with
 936           no Ethernet interface.
 937
 938 config USB_MASS_STORAGE
 939         tristate "Mass Storage Gadget"
 940         depends on BLOCK
 941         select USB_LIBCOMPOSITE
 942         select USB_F_MASS_STORAGE
 943         help
 944           The Mass Storage Gadget acts as a USB Mass Storage disk drive.
 945           As its storage repository it can use a regular file or a block
 946           device (in much the same way as the "loop" device driver),
 947           specified as a module parameter or sysfs option.
 948
 949           This driver is a replacement for now removed File-backed
 950           Storage Gadget (g_file_storage).
 951
 952           Say "y" to link the driver statically, or "m" to build
 953           a dynamically linked module called "g_mass_storage".
 954
 955 config USB_GADGET_TARGET
 956         tristate "USB Gadget Target Fabric Module"
 957         depends on TARGET_CORE
 958         select USB_LIBCOMPOSITE
 959         help
 960           This fabric is an USB gadget. Two USB protocols are supported that is
 961           BBB or BOT (Bulk Only Transport) and UAS (USB Attached SCSI). BOT is
 962           advertised on alternative interface 0 (primary) and UAS is on
 963           alternative interface 1. Both protocols can work on USB2.0 and USB3.0.
 964           UAS utilizes the USB 3.0 feature called streams support.
 965
 966 config USB_G_SERIAL
 967         tristate "Serial Gadget (with CDC ACM and CDC OBEX support)"
 968         depends on TTY
 969         select USB_U_SERIAL
 970         select USB_F_ACM
 971         select USB_F_SERIAL
 972         select USB_F_OBEX
 973         select USB_LIBCOMPOSITE
 974         help
 975           The Serial Gadget talks to the Linux-USB generic serial driver.
 976           This driver supports a CDC-ACM module option, which can be used
 977           to interoperate with MS-Windows hosts or with the Linux-USB
 978           "cdc-acm" driver.
 979
 980           This driver also supports a CDC-OBEX option.  You will need a
 981           user space OBEX server talking to /dev/ttyGS*, since the kernel
 982           itself doesn't implement the OBEX protocol.
 983
 984           Say "y" to link the driver statically, or "m" to build a
 985           dynamically linked module called "g_serial".
 986
 987           For more information, see Documentation/usb/gadget_serial.txt
 988           which includes instructions and a "driver info file" needed to
 989           make MS-Windows work with CDC ACM.
 990
 991 config USB_MIDI_GADGET
 992         tristate "MIDI Gadget"
 993         depends on SND
 994         select USB_LIBCOMPOSITE
 995         select SND_RAWMIDI
 996         help
 997           The MIDI Gadget acts as a USB Audio device, with one MIDI
 998           input and one MIDI output. These MIDI jacks appear as
 999           a sound "card" in the ALSA sound system. Other MIDI
1000           connections can then be made on the gadget system, using
1001           ALSA's aconnect utility etc.
1002
1003           Say "y" to link the driver statically, or "m" to build a
1004           dynamically linked module called "g_midi".
1005
1006 config USB_G_PRINTER
1007         tristate "Printer Gadget"
1008         select USB_LIBCOMPOSITE
1009         help
1010           The Printer Gadget channels data between the USB host and a
1011           userspace program driving the print engine. The user space
1012           program reads and writes the device file /dev/g_printer to
1013           receive or send printer data. It can use ioctl calls to
1014           the device file to get or set printer status.
1015
1016           Say "y" to link the driver statically, or "m" to build a
1017           dynamically linked module called "g_printer".
1018
1019           For more information, see Documentation/usb/gadget_printer.txt
1020           which includes sample code for accessing the device file.
1021
1022 if TTY
1023
1024 config USB_CDC_COMPOSITE
1025         tristate "CDC Composite Device (Ethernet and ACM)"
1026         depends on NET
1027         select USB_LIBCOMPOSITE
1028         select USB_U_SERIAL
1029         select USB_U_ETHER
1030         select USB_F_ACM
1031         select USB_F_ECM
1032         help
1033           This driver provides two functions in one configuration:
1034           a CDC Ethernet (ECM) link, and a CDC ACM (serial port) link.
1035
1036           This driver requires four bulk and two interrupt endpoints,
1037           plus the ability to handle altsettings.  Not all peripheral
1038           controllers are that capable.
1039
1040           Say "y" to link the driver statically, or "m" to build a
1041           dynamically linked module.
1042
1043 config USB_G_NOKIA
1044         tristate "Nokia composite gadget"
1045         depends on PHONET
1046         select USB_LIBCOMPOSITE
1047         select USB_U_SERIAL
1048         select USB_U_ETHER
1049         select USB_F_ACM
1050         select USB_F_OBEX
1051         select USB_F_PHONET
1052         select USB_F_ECM
1053         help
1054           The Nokia composite gadget provides support for acm, obex
1055           and phonet in only one composite gadget driver.
1056
1057           It's only really useful for N900 hardware. If you're building
1058           a kernel for N900, say Y or M here. If unsure, say N.
1059
1060 config USB_G_ACM_MS
1061         tristate "CDC Composite Device (ACM and mass storage)"
1062         depends on BLOCK
1063         select USB_LIBCOMPOSITE
1064         select USB_U_SERIAL
1065         select USB_F_ACM
1066         select USB_F_MASS_STORAGE
1067         help
1068           This driver provides two functions in one configuration:
1069           a mass storage, and a CDC ACM (serial port) link.
1070
1071           Say "y" to link the driver statically, or "m" to build a
1072           dynamically linked module called "g_acm_ms".
1073
1074 config USB_G_MULTI
1075         tristate "Multifunction Composite Gadget"
1076         depends on BLOCK && NET
1077         select USB_G_MULTI_CDC if !USB_G_MULTI_RNDIS
1078         select USB_LIBCOMPOSITE
1079         select USB_U_SERIAL
1080         select USB_U_ETHER
1081         select USB_F_ACM
1082         select USB_F_MASS_STORAGE
1083         help
1084           The Multifunction Composite Gadget provides Ethernet (RNDIS
1085           and/or CDC Ethernet), mass storage and ACM serial link
1086           interfaces.
1087
1088           You will be asked to choose which of the two configurations is
1089           to be available in the gadget.  At least one configuration must
1090           be chosen to make the gadget usable.  Selecting more than one
1091           configuration will prevent Windows from automatically detecting
1092           the gadget as a composite gadget, so an INF file will be needed to
1093           use the gadget.
1094
1095           Say "y" to link the driver statically, or "m" to build a
1096           dynamically linked module called "g_multi".
1097
1098 config USB_G_MULTI_RNDIS
1099         bool "RNDIS + CDC Serial + Storage configuration"
1100         depends on USB_G_MULTI
1101         select USB_F_RNDIS
1102         default y
1103         help
1104           This option enables a configuration with RNDIS, CDC Serial and
1105           Mass Storage functions available in the Multifunction Composite
1106           Gadget.  This is the configuration dedicated for Windows since RNDIS
1107           is Microsoft's protocol.
1108
1109           If unsure, say "y".
1110
1111 config USB_G_MULTI_CDC
1112         bool "CDC Ethernet + CDC Serial + Storage configuration"
1113         depends on USB_G_MULTI
1114         default n
1115         select USB_F_ECM
1116         help
1117           This option enables a configuration with CDC Ethernet (ECM), CDC
1118           Serial and Mass Storage functions available in the Multifunction
1119           Composite Gadget.
1120
1121           If unsure, say "y".
1122
1123 endif # TTY
1124
1125 config USB_G_HID
1126         tristate "HID Gadget"
1127         select USB_LIBCOMPOSITE
1128         help
1129           The HID gadget driver provides generic emulation of USB
1130           Human Interface Devices (HID).
1131
1132           For more information, see Documentation/usb/gadget_hid.txt which
1133           includes sample code for accessing the device files.
1134
1135           Say "y" to link the driver statically, or "m" to build a
1136           dynamically linked module called "g_hid".
1137
1138 # Standalone / single function gadgets
1139 config USB_G_DBGP
1140         tristate "EHCI Debug Device Gadget"
1141         depends on TTY
1142         select USB_LIBCOMPOSITE
1143         help
1144           This gadget emulates an EHCI Debug device. This is useful when you want
1145           to interact with an EHCI Debug Port.
1146
1147           Say "y" to link the driver statically, or "m" to build a
1148           dynamically linked module called "g_dbgp".
1149
1150 if USB_G_DBGP
1151 choice
1152         prompt "EHCI Debug Device mode"
1153         default USB_G_DBGP_SERIAL
1154
1155 config USB_G_DBGP_PRINTK
1156         depends on USB_G_DBGP
1157         bool "printk"
1158         help
1159           Directly printk() received data. No interaction.
1160
1161 config USB_G_DBGP_SERIAL
1162         depends on USB_G_DBGP
1163         select USB_U_SERIAL
1164         bool "serial"
1165         help
1166           Userland can interact using /dev/ttyGSxxx.
1167 endchoice
1168 endif
1169
1170 # put drivers that need isochronous transfer support (for audio
1171 # or video class gadget drivers), or specific hardware, here.
1172 config USB_G_WEBCAM
1173         tristate "USB Webcam Gadget"
1174         depends on VIDEO_DEV
1175         select USB_LIBCOMPOSITE
1176         select VIDEOBUF2_VMALLOC
1177         help
1178           The Webcam Gadget acts as a composite USB Audio and Video Class
1179           device. It provides a userspace API to process UVC control requests
1180           and stream video data to the host.
1181
1182           Say "y" to link the driver statically, or "m" to build a
1183           dynamically linked module called "g_webcam".
1184
1185 endchoice
1186
1187 endif # USB_GADGET