Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 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). |
Matt LaPlante | cab0089 | 2006-10-03 22:36:44 +0200 | [diff] [blame] | 10 | # - Some systems have both kinds of controllers. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 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 | # |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 15 | |
Denis Cheng | b75be4a | 2008-01-24 16:36:31 +0800 | [diff] [blame] | 16 | menuconfig USB_GADGET |
| 17 | tristate "USB Gadget Support" |
Alan Stern | 86dc243 | 2011-11-17 16:42:24 -0500 | [diff] [blame] | 18 | select NLS |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 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 |
Jules Villard | e113f29 | 2006-08-22 22:40:15 +0200 | [diff] [blame] | 29 | familiar host side controllers have names like "EHCI", "OHCI", |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 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 | |
Denis Cheng | b75be4a | 2008-01-24 16:36:31 +0800 | [diff] [blame] | 45 | if USB_GADGET |
| 46 | |
David Brownell | 70790f6 | 2007-07-01 17:35:28 -0700 | [diff] [blame] | 47 | config USB_GADGET_DEBUG |
Robert P. J. Day | afd0e0f | 2008-03-10 15:09:51 -0400 | [diff] [blame] | 48 | boolean "Debugging messages (DEVELOPMENT)" |
David Brownell | 36e893d | 2008-09-12 09:39:06 -0700 | [diff] [blame] | 49 | depends on DEBUG_KERNEL |
David Brownell | 70790f6 | 2007-07-01 17:35:28 -0700 | [diff] [blame] | 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 | |
Andreas Larsson | cd10869 | 2013-10-11 08:07:00 +0200 | [diff] [blame] | 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 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 75 | config USB_GADGET_DEBUG_FILES |
Robert P. J. Day | afd0e0f | 2008-03-10 15:09:51 -0400 | [diff] [blame] | 76 | boolean "Debugging information files (DEVELOPMENT)" |
David Brownell | 36e893d | 2008-09-12 09:39:06 -0700 | [diff] [blame] | 77 | depends on PROC_FS |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 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 | |
Haavard Skinnemoen | 914a3f3 | 2007-10-10 02:29:43 -0700 | [diff] [blame] | 86 | config USB_GADGET_DEBUG_FS |
Robert P. J. Day | afd0e0f | 2008-03-10 15:09:51 -0400 | [diff] [blame] | 87 | boolean "Debugging information files in debugfs (DEVELOPMENT)" |
David Brownell | 36e893d | 2008-09-12 09:39:06 -0700 | [diff] [blame] | 88 | depends on DEBUG_FS |
Haavard Skinnemoen | 914a3f3 | 2007-10-10 02:29:43 -0700 | [diff] [blame] | 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 | |
David Brownell | 36e893d | 2008-09-12 09:39:06 -0700 | [diff] [blame] | 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 | |
Per Forlin | 6532c7f | 2011-08-19 21:21:27 +0200 | [diff] [blame] | 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 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 130 | # |
| 131 | # USB Peripheral Controller Support |
| 132 | # |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 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 | # |
Alexander Shishkin | ed6c6f4 | 2012-05-08 23:29:00 +0300 | [diff] [blame] | 140 | menu "USB Peripheral Controller" |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 141 | |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 142 | # |
| 143 | # Integrated controllers |
| 144 | # |
| 145 | |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 146 | config USB_AT91 |
| 147 | tristate "Atmel AT91 USB Device Port" |
Jean-Christophe PLAGNIOL-VILLARD | d1494a3 | 2012-01-28 22:35:36 +0800 | [diff] [blame] | 148 | depends on ARCH_AT91 |
Thomas Dahlmann | 55d402d | 2007-07-16 21:40:54 -0700 | [diff] [blame] | 149 | help |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 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). |
Thomas Dahlmann | 55d402d | 2007-07-16 21:40:54 -0700 | [diff] [blame] | 153 | |
| 154 | Say "y" to link the driver statically, or "m" to build a |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 155 | dynamically linked module called "at91_udc" and force all |
Thomas Dahlmann | 55d402d | 2007-07-16 21:40:54 -0700 | [diff] [blame] | 156 | gadget drivers to also be dynamically linked. |
| 157 | |
Roland Stigge | 24a28e4 | 2012-04-29 16:47:05 +0200 | [diff] [blame] | 158 | config USB_LPC32XX |
| 159 | tristate "LPC32XX USB Peripheral Controller" |
Arnd Bergmann | 38e0c10 | 2014-05-08 15:52:20 +0200 | [diff] [blame] | 160 | depends on ARCH_LPC32XX && I2C |
Roland Stigge | 24a28e4 | 2012-04-29 16:47:05 +0200 | [diff] [blame] | 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 | |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 169 | config USB_ATMEL_USBA |
| 170 | tristate "Atmel USBA" |
Jean-Christophe PLAGNIOL-VILLARD | 4a3ae93 | 2013-05-03 20:22:57 +0800 | [diff] [blame] | 171 | depends on AVR32 || ARCH_AT91 |
Haavard Skinnemoen | 914a3f3 | 2007-10-10 02:29:43 -0700 | [diff] [blame] | 172 | help |
| 173 | USBA is the integrated high-speed USB Device controller on |
Nicolas Ferre | ba45ca4 | 2008-04-08 13:59:18 +0100 | [diff] [blame] | 174 | the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel. |
Haavard Skinnemoen | 914a3f3 | 2007-10-10 02:29:43 -0700 | [diff] [blame] | 175 | |
Kevin Cernekee | 613065e | 2012-08-25 12:38:52 -0700 | [diff] [blame] | 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 | |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 187 | config USB_FSL_USB2 |
| 188 | tristate "Freescale Highspeed USB DR Peripheral Controller" |
Guennadi Liakhovetski | 54e4026b | 2009-04-15 14:25:33 +0200 | [diff] [blame] | 189 | depends on FSL_SOC || ARCH_MXC |
Marc Kleine-Budde | 018b97d | 2010-10-29 11:04:49 +0200 | [diff] [blame] | 190 | select USB_FSL_MPH_DR_OF if OF |
Li Yang | b504882 | 2007-04-23 10:54:25 -0700 | [diff] [blame] | 191 | help |
Fabio Estevam | 00c16f9 | 2012-04-09 17:14:16 -0300 | [diff] [blame] | 192 | Some of Freescale PowerPC and i.MX processors have a High Speed |
Li Yang | b504882 | 2007-04-23 10:54:25 -0700 | [diff] [blame] | 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 | |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 202 | config USB_FUSB300 |
| 203 | tristate "Faraday FUSB300 USB Peripheral Controller" |
Geert Uytterhoeven | b2fb945 | 2013-08-18 22:20:41 +0200 | [diff] [blame] | 204 | depends on !PHYS_ADDR_T_64BIT && HAS_DMA |
Yuan-Hsin Chen | 0fe6f1d | 2011-01-18 14:49:28 +0800 | [diff] [blame] | 205 | help |
| 206 | Faraday usb device controller FUSB300 driver |
| 207 | |
Yuan-Hsin Chen | b84a8de | 2013-05-30 15:41:01 +0000 | [diff] [blame] | 208 | config USB_FOTG210_UDC |
Geert Uytterhoeven | bfcbd02 | 2013-07-11 15:54:03 +0200 | [diff] [blame] | 209 | depends on HAS_DMA |
Yuan-Hsin Chen | b84a8de | 2013-05-30 15:41:01 +0000 | [diff] [blame] | 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 | |
Andreas Larsson | 27e9dcc | 2013-12-23 21:25:49 +0100 | [diff] [blame] | 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 | |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 226 | config USB_OMAP |
| 227 | tristate "OMAP USB Device Controller" |
Tony Lindgren | b924b20 | 2012-06-04 00:56:15 -0700 | [diff] [blame] | 228 | depends on ARCH_OMAP1 |
Arnd Bergmann | 38e0c10 | 2014-05-08 15:52:20 +0200 | [diff] [blame] | 229 | depends on ISP1301_OMAP || !(MACH_OMAP_H2 || MACH_OMAP_H3) |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 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 | |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 241 | config USB_PXA25X |
| 242 | tristate "PXA 25x or IXP 4xx" |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 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 | |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 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 |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 259 | depends on USB_PXA25X |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 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 | |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 266 | config USB_R8A66597 |
| 267 | tristate "Renesas R8A66597 USB Peripheral Controller" |
Geert Uytterhoeven | 4ee4f23 | 2013-08-18 22:20:42 +0200 | [diff] [blame] | 268 | depends on HAS_DMA |
Yoshihiro Shimoda | c414424 | 2009-08-19 04:59:39 +0000 | [diff] [blame] | 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 | |
Kuninori Morimoto | 030ed1f | 2011-07-07 02:17:37 -0700 | [diff] [blame] | 278 | config USB_RENESAS_USBHS_UDC |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 279 | tristate 'Renesas USBHS controller' |
Kuninori Morimoto | 030ed1f | 2011-07-07 02:17:37 -0700 | [diff] [blame] | 280 | depends on USB_RENESAS_USBHS |
Kuninori Morimoto | 2f98382 | 2011-04-05 11:40:54 +0900 | [diff] [blame] | 281 | help |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 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. |
Kuninori Morimoto | 2f98382 | 2011-04-05 11:40:54 +0900 | [diff] [blame] | 285 | |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 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. |
Kuninori Morimoto | 2f98382 | 2011-04-05 11:40:54 +0900 | [diff] [blame] | 289 | |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 290 | config USB_PXA27X |
| 291 | tristate "PXA 27x" |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 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 | |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 303 | config USB_S3C2410 |
| 304 | tristate "S3C2410 USB Device Controller" |
Kukjin Kim | b130d5c | 2012-02-03 14:29:23 +0900 | [diff] [blame] | 305 | depends on ARCH_S3C24XX |
Arnaud Patard | 3fc154b | 2007-06-06 21:05:49 -0700 | [diff] [blame] | 306 | help |
| 307 | Samsung's S3C2410 is an ARM-4 processor with an integrated |
| 308 | full speed USB 1.1 device controller. It has 4 configurable |
| 309 | endpoints, as well as endpoint zero (for control transfers). |
| 310 | |
| 311 | This driver has been tested on the S3C2410, S3C2412, and |
| 312 | S3C2440 processors. |
| 313 | |
Arnaud Patard | 3fc154b | 2007-06-06 21:05:49 -0700 | [diff] [blame] | 314 | config USB_S3C2410_DEBUG |
| 315 | boolean "S3C2410 udc debug messages" |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 316 | depends on USB_S3C2410 |
Arnaud Patard | 3fc154b | 2007-06-06 21:05:49 -0700 | [diff] [blame] | 317 | |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 318 | config USB_S3C_HSUDC |
| 319 | tristate "S3C2416, S3C2443 and S3C2450 USB Device Controller" |
Kukjin Kim | b130d5c | 2012-02-03 14:29:23 +0900 | [diff] [blame] | 320 | depends on ARCH_S3C24XX |
Thomas Abraham | a9df304 | 2011-05-07 22:28:04 +0200 | [diff] [blame] | 321 | help |
| 322 | Samsung's S3C2416, S3C2443 and S3C2450 is an ARM9 based SoC |
| 323 | integrated with dual speed USB 2.0 device controller. It has |
| 324 | 8 endpoints, as well as endpoint zero. |
| 325 | |
| 326 | This driver has been tested on S3C2416 and S3C2450 processors. |
| 327 | |
Neil Zhang | 5e6c86b | 2011-12-20 13:20:21 +0800 | [diff] [blame] | 328 | config USB_MV_UDC |
| 329 | tristate "Marvell USB2.0 Device Controller" |
Martin Schwidefsky | 0244ad0 | 2013-08-30 09:39:53 +0200 | [diff] [blame] | 330 | depends on HAS_DMA |
cxie4 | e7cddda | 2010-11-30 13:35:15 +0800 | [diff] [blame] | 331 | help |
Neil Zhang | 5e6c86b | 2011-12-20 13:20:21 +0800 | [diff] [blame] | 332 | Marvell Socs (including PXA and MMP series) include a high speed |
| 333 | USB2.0 OTG controller, which can be configured as high speed or |
| 334 | full speed USB peripheral. |
Felipe Balbi | 72246da | 2011-08-19 18:10:58 +0300 | [diff] [blame] | 335 | |
Yu Xu | 3d4eb9d | 2012-06-15 21:45:08 +0800 | [diff] [blame] | 336 | config USB_MV_U3D |
Geert Uytterhoeven | 91f6b84 | 2013-07-11 15:54:04 +0200 | [diff] [blame] | 337 | depends on HAS_DMA |
Yu Xu | 3d4eb9d | 2012-06-15 21:45:08 +0800 | [diff] [blame] | 338 | tristate "MARVELL PXA2128 USB 3.0 controller" |
Yu Xu | 3d4eb9d | 2012-06-15 21:45:08 +0800 | [diff] [blame] | 339 | help |
| 340 | MARVELL PXA2128 Processor series include a super speed USB3.0 device |
| 341 | controller, which support super speed USB peripheral. |
| 342 | |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 343 | # |
| 344 | # Controllers available in both integrated and discrete versions |
| 345 | # |
| 346 | |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 347 | config USB_M66592 |
| 348 | tristate "Renesas M66592 USB Peripheral Controller" |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 349 | help |
| 350 | M66592 is a discrete USB peripheral controller chip that |
| 351 | supports both full and high speed USB 2.0 data transfers. |
| 352 | It has seven configurable endpoints, and endpoint zero. |
David Brownell | bae4bd8 | 2006-01-22 10:32:37 -0800 | [diff] [blame] | 353 | |
| 354 | Say "y" to link the driver statically, or "m" to build a |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 355 | dynamically linked module called "m66592_udc" and force all |
David Brownell | bae4bd8 | 2006-01-22 10:32:37 -0800 | [diff] [blame] | 356 | gadget drivers to also be dynamically linked. |
| 357 | |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 358 | # |
| 359 | # Controllers available only in discrete form (and all PCI controllers) |
| 360 | # |
| 361 | |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 362 | config USB_AMD5536UDC |
| 363 | tristate "AMD5536 UDC" |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 364 | depends on PCI |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 365 | help |
| 366 | The AMD5536 UDC is part of the AMD Geode CS5536, an x86 southbridge. |
| 367 | It is a USB Highspeed DMA capable USB device controller. Beside ep0 |
| 368 | it provides 4 IN and 4 OUT endpoints (bulk or interrupt type). |
| 369 | The UDC port supports OTG operation, and may be used as a host port |
| 370 | if it's not being used to implement peripheral or OTG roles. |
| 371 | |
| 372 | Say "y" to link the driver statically, or "m" to build a |
| 373 | dynamically linked module called "amd5536udc" and force all |
| 374 | gadget drivers to also be dynamically linked. |
| 375 | |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 376 | config USB_FSL_QE |
| 377 | tristate "Freescale QE/CPM USB Device Controller" |
Li Yang | 3948f0e | 2008-09-02 19:58:10 +0800 | [diff] [blame] | 378 | depends on FSL_SOC && (QUICC_ENGINE || CPM) |
| 379 | help |
| 380 | Some of Freescale PowerPC processors have a Full Speed |
| 381 | QE/CPM2 USB controller, which support device mode with 4 |
| 382 | programmable endpoints. This driver supports the |
| 383 | controller in the MPC8360 and MPC8272, and should work with |
| 384 | controllers having QE or CPM2, given minor tweaks. |
| 385 | |
| 386 | Set CONFIG_USB_GADGET to "m" to build this driver as a |
Matt LaPlante | 692105b | 2009-01-26 11:12:25 +0100 | [diff] [blame] | 387 | dynamically linked module called "fsl_qe_udc". |
Li Yang | 3948f0e | 2008-09-02 19:58:10 +0800 | [diff] [blame] | 388 | |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 389 | config USB_NET2272 |
| 390 | tristate "PLX NET2272" |
Seth Levy | ceb8036 | 2011-06-06 19:42:44 -0400 | [diff] [blame] | 391 | help |
| 392 | PLX NET2272 is a USB peripheral controller which supports |
| 393 | both full and high speed USB 2.0 data transfers. |
| 394 | |
| 395 | It has three configurable endpoints, as well as endpoint zero |
| 396 | (for control transfer). |
| 397 | Say "y" to link the driver statically, or "m" to build a |
| 398 | dynamically linked module called "net2272" and force all |
| 399 | gadget drivers to also be dynamically linked. |
| 400 | |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 401 | config USB_NET2272_DMA |
Seth Levy | ceb8036 | 2011-06-06 19:42:44 -0400 | [diff] [blame] | 402 | boolean "Support external DMA controller" |
Geert Uytterhoeven | 272b05a | 2013-08-18 22:20:43 +0200 | [diff] [blame] | 403 | depends on USB_NET2272 && HAS_DMA |
Seth Levy | ceb8036 | 2011-06-06 19:42:44 -0400 | [diff] [blame] | 404 | help |
| 405 | The NET2272 part can optionally support an external DMA |
| 406 | controller, but your board has to have support in the |
| 407 | driver itself. |
| 408 | |
| 409 | If unsure, say "N" here. The driver works fine in PIO mode. |
| 410 | |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 411 | config USB_NET2280 |
Ricardo Ribalda Delgado | adc82f7 | 2014-05-20 18:30:03 +0200 | [diff] [blame] | 412 | tristate "NetChip 228x / PLX USB338x" |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 413 | depends on PCI |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 414 | help |
| 415 | NetChip 2280 / 2282 is a PCI based USB peripheral controller which |
| 416 | supports both full and high speed USB 2.0 data transfers. |
| 417 | |
| 418 | It has six configurable endpoints, as well as endpoint zero |
| 419 | (for control transfers) and several endpoints with dedicated |
| 420 | functions. |
| 421 | |
Ricardo Ribalda Delgado | adc82f7 | 2014-05-20 18:30:03 +0200 | [diff] [blame] | 422 | PLX 3380 / 3382 is a PCIe based USB peripheral controller which |
| 423 | supports full, high speed USB 2.0 and super speed USB 3.0 |
| 424 | data transfers. |
| 425 | |
| 426 | It has eight configurable endpoints, as well as endpoint zero |
| 427 | (for control transfers) and several endpoints with dedicated |
| 428 | functions. |
| 429 | |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 430 | Say "y" to link the driver statically, or "m" to build a |
| 431 | dynamically linked module called "net2280" and force all |
| 432 | gadget drivers to also be dynamically linked. |
| 433 | |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 434 | config USB_GOKU |
| 435 | tristate "Toshiba TC86C001 'Goku-S'" |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 436 | depends on PCI |
| 437 | help |
| 438 | The Toshiba TC86C001 is a PCI device which includes controllers |
| 439 | for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI). |
| 440 | |
| 441 | The device controller has three configurable (bulk or interrupt) |
| 442 | endpoints, plus endpoint zero (for control transfers). |
| 443 | |
| 444 | Say "y" to link the driver statically, or "m" to build a |
| 445 | dynamically linked module called "goku_udc" and to force all |
| 446 | gadget drivers to also be dynamically linked. |
| 447 | |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 448 | config USB_EG20T |
Tomoya MORINAGA | 731ad81 | 2011-10-28 09:37:34 +0900 | [diff] [blame] | 449 | tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7213/ML7831) UDC" |
Martin Schwidefsky | 0244ad0 | 2013-08-30 09:39:53 +0200 | [diff] [blame] | 450 | depends on PCI |
Toshiharu Okada | f646cf9 | 2010-11-11 18:27:57 +0900 | [diff] [blame] | 451 | help |
| 452 | This is a USB device driver for EG20T PCH. |
| 453 | EG20T PCH is the platform controller hub that is used in Intel's |
| 454 | general embedded platform. EG20T PCH has USB device interface. |
| 455 | Using this interface, it is able to access system devices connected |
| 456 | to USB device. |
| 457 | This driver enables USB device function. |
| 458 | USB device is a USB peripheral controller which |
| 459 | supports both full and high speed USB 2.0 data transfers. |
| 460 | This driver supports both control transfer and bulk transfer modes. |
| 461 | This driver dose not support interrupt transfer or isochronous |
| 462 | transfer modes. |
| 463 | |
Tomoya MORINAGA | 731ad81 | 2011-10-28 09:37:34 +0900 | [diff] [blame] | 464 | This driver also can be used for LAPIS Semiconductor's ML7213 which is |
Tomoya MORINAGA | 06f1b97 | 2011-01-06 09:16:31 +0900 | [diff] [blame] | 465 | for IVI(In-Vehicle Infotainment) use. |
Tomoya MORINAGA | 731ad81 | 2011-10-28 09:37:34 +0900 | [diff] [blame] | 466 | ML7831 is for general purpose use. |
| 467 | ML7213/ML7831 is companion chip for Intel Atom E6xx series. |
| 468 | ML7213/ML7831 is completely compatible for Intel EG20T PCH. |
Tomoya MORINAGA | 06f1b97 | 2011-01-06 09:16:31 +0900 | [diff] [blame] | 469 | |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 470 | # |
| 471 | # LAST -- dummy/emulated controller |
| 472 | # |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 473 | |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 474 | config USB_DUMMY_HCD |
| 475 | tristate "Dummy HCD (DEVELOPMENT)" |
Robert P. J. Day | afd0e0f | 2008-03-10 15:09:51 -0400 | [diff] [blame] | 476 | depends on USB=y || (USB=m && USB_GADGET=m) |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 477 | help |
| 478 | This host controller driver emulates USB, looping all data transfer |
| 479 | requests back to a USB "gadget driver" in the same host. The host |
| 480 | side is the master; the gadget side is the slave. Gadget drivers |
| 481 | can be high, full, or low speed; and they have access to endpoints |
| 482 | like those from NET2280, PXA2xx, or SA1100 hardware. |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 483 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 484 | This may help in some stages of creating a driver to embed in a |
| 485 | Linux device, since it lets you debug several parts of the gadget |
| 486 | driver without its hardware or drivers being involved. |
Felipe Balbi | 193ab2a | 2011-06-22 17:28:10 +0300 | [diff] [blame] | 487 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 488 | Since such a gadget side driver needs to interoperate with a host |
| 489 | side Linux-USB device driver, this may help to debug both sides |
| 490 | of a USB protocol stack. |
| 491 | |
| 492 | Say "y" to link the driver statically, or "m" to build a |
| 493 | dynamically linked module called "dummy_hcd" and force all |
| 494 | gadget drivers to also be dynamically linked. |
| 495 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 496 | # NOTE: Please keep dummy_hcd LAST so that "real hardware" appears |
| 497 | # first and will be selected by default. |
| 498 | |
Alexander Shishkin | ed6c6f4 | 2012-05-08 23:29:00 +0300 | [diff] [blame] | 499 | endmenu |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 500 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 501 | # |
| 502 | # USB Gadget Drivers |
| 503 | # |
Sebastian Andrzej Siewior | a84d9e5 | 2012-09-06 20:11:09 +0200 | [diff] [blame] | 504 | |
| 505 | # composite based drivers |
| 506 | config USB_LIBCOMPOSITE |
| 507 | tristate |
Sebastian Andrzej Siewior | 88af8bb | 2012-12-23 21:10:24 +0100 | [diff] [blame] | 508 | select CONFIGFS_FS |
Sebastian Andrzej Siewior | a84d9e5 | 2012-09-06 20:11:09 +0200 | [diff] [blame] | 509 | depends on USB_GADGET |
| 510 | |
Sebastian Andrzej Siewior | ff47f59 | 2012-12-23 21:10:07 +0100 | [diff] [blame] | 511 | config USB_F_ACM |
| 512 | tristate |
| 513 | |
Sebastian Andrzej Siewior | cf9a08a | 2012-12-23 21:10:01 +0100 | [diff] [blame] | 514 | config USB_F_SS_LB |
| 515 | tristate |
| 516 | |
Sebastian Andrzej Siewior | 3249ca2 | 2012-12-23 21:10:04 +0100 | [diff] [blame] | 517 | config USB_U_SERIAL |
| 518 | tristate |
| 519 | |
Andrzej Pietrasiewicz | f1a1823 | 2013-05-23 09:22:03 +0200 | [diff] [blame] | 520 | config USB_U_ETHER |
| 521 | tristate |
| 522 | |
Andrzej Pietrasiewicz | 60540ea | 2013-03-18 09:52:57 +0100 | [diff] [blame] | 523 | config USB_F_SERIAL |
| 524 | tristate |
| 525 | |
Andrzej Pietrasiewicz | 1d8fc25 | 2013-03-21 15:33:42 +0100 | [diff] [blame] | 526 | config USB_F_OBEX |
| 527 | tristate |
| 528 | |
Andrzej Pietrasiewicz | 40d133d | 2013-05-23 09:22:06 +0200 | [diff] [blame] | 529 | config USB_F_NCM |
| 530 | tristate |
| 531 | |
Andrzej Pietrasiewicz | fee562a | 2013-05-23 10:32:03 +0200 | [diff] [blame] | 532 | config USB_F_ECM |
| 533 | tristate |
| 534 | |
Andrzej Pietrasiewicz | fcbdf12 | 2013-05-23 10:51:11 +0200 | [diff] [blame] | 535 | config USB_F_PHONET |
| 536 | tristate |
| 537 | |
Andrzej Pietrasiewicz | b29002a | 2013-05-28 09:15:47 +0200 | [diff] [blame] | 538 | config USB_F_EEM |
| 539 | tristate |
| 540 | |
Andrzej Pietrasiewicz | 8cedba7 | 2013-05-28 09:15:53 +0200 | [diff] [blame] | 541 | config USB_F_SUBSET |
| 542 | tristate |
| 543 | |
Andrzej Pietrasiewicz | f466c63 | 2013-05-28 09:15:57 +0200 | [diff] [blame] | 544 | config USB_F_RNDIS |
| 545 | tristate |
| 546 | |
Andrzej Pietrasiewicz | e5eaa0d | 2013-10-09 10:06:01 +0200 | [diff] [blame] | 547 | config USB_F_MASS_STORAGE |
| 548 | tristate |
| 549 | |
Andrzej Pietrasiewicz | 5920cda | 2013-12-03 15:15:33 +0100 | [diff] [blame] | 550 | config USB_F_FS |
| 551 | tristate |
| 552 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 553 | choice |
| 554 | tristate "USB Gadget Drivers" |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 555 | default USB_ETH |
| 556 | help |
| 557 | A Linux "Gadget Driver" talks to the USB Peripheral Controller |
| 558 | driver through the abstract "gadget" API. Some other operating |
| 559 | systems call these "client" drivers, of which "class drivers" |
| 560 | are a subset (implementing a USB device class specification). |
| 561 | A gadget driver implements one or more USB functions using |
| 562 | the peripheral hardware. |
| 563 | |
| 564 | Gadget drivers are hardware-neutral, or "platform independent", |
| 565 | except that they sometimes must understand quirks or limitations |
| 566 | of the particular controllers they work with. For example, when |
| 567 | a controller doesn't support alternate configurations or provide |
| 568 | enough of the right types of endpoints, the gadget driver might |
| 569 | not be able work with that controller, or might need to implement |
| 570 | a less common variant of a device class protocol. |
| 571 | |
| 572 | # this first set of drivers all depend on bulk-capable hardware. |
| 573 | |
Andrzej Pietrasiewicz | d1c0245 | 2013-06-13 10:37:24 +0200 | [diff] [blame] | 574 | config USB_CONFIGFS |
| 575 | tristate "USB functions configurable through configfs" |
| 576 | select USB_LIBCOMPOSITE |
| 577 | help |
| 578 | A Linux USB "gadget" can be set up through configfs. |
| 579 | If this is the case, the USB functions (which from the host's |
| 580 | perspective are seen as interfaces) and configurations are |
| 581 | specified simply by creating appropriate directories in configfs. |
| 582 | Associating functions with configurations is done by creating |
| 583 | appropriate symbolic links. |
Philippe De Swert | 9c1d696 | 2013-08-18 13:51:43 +0300 | [diff] [blame] | 584 | For more information see Documentation/usb/gadget_configfs.txt. |
Andrzej Pietrasiewicz | d1c0245 | 2013-06-13 10:37:24 +0200 | [diff] [blame] | 585 | |
| 586 | config USB_CONFIGFS_SERIAL |
| 587 | boolean "Generic serial bulk in/out" |
| 588 | depends on USB_CONFIGFS |
| 589 | depends on TTY |
| 590 | select USB_U_SERIAL |
| 591 | select USB_F_SERIAL |
| 592 | help |
| 593 | The function talks to the Linux-USB generic serial driver. |
| 594 | |
| 595 | config USB_CONFIGFS_ACM |
| 596 | boolean "Abstract Control Model (CDC ACM)" |
| 597 | depends on USB_CONFIGFS |
| 598 | depends on TTY |
| 599 | select USB_U_SERIAL |
| 600 | select USB_F_ACM |
| 601 | help |
| 602 | ACM serial link. This function can be used to interoperate with |
| 603 | MS-Windows hosts or with the Linux-USB "cdc-acm" driver. |
| 604 | |
| 605 | config USB_CONFIGFS_OBEX |
| 606 | boolean "Object Exchange Model (CDC OBEX)" |
| 607 | depends on USB_CONFIGFS |
| 608 | depends on TTY |
| 609 | select USB_U_SERIAL |
| 610 | select USB_F_OBEX |
| 611 | help |
| 612 | You will need a user space OBEX server talking to /dev/ttyGS*, |
| 613 | since the kernel itself doesn't implement the OBEX protocol. |
| 614 | |
| 615 | config USB_CONFIGFS_NCM |
| 616 | boolean "Network Control Model (CDC NCM)" |
| 617 | depends on USB_CONFIGFS |
| 618 | depends on NET |
| 619 | select USB_U_ETHER |
| 620 | select USB_F_NCM |
| 621 | help |
| 622 | NCM is an advanced protocol for Ethernet encapsulation, allows |
| 623 | grouping of several ethernet frames into one USB transfer and |
| 624 | different alignment possibilities. |
| 625 | |
| 626 | config USB_CONFIGFS_ECM |
| 627 | boolean "Ethernet Control Model (CDC ECM)" |
| 628 | depends on USB_CONFIGFS |
| 629 | depends on NET |
| 630 | select USB_U_ETHER |
| 631 | select USB_F_ECM |
| 632 | help |
| 633 | The "Communication Device Class" (CDC) Ethernet Control Model. |
| 634 | That protocol is often avoided with pure Ethernet adapters, in |
| 635 | favor of simpler vendor-specific hardware, but is widely |
| 636 | supported by firmware for smart network devices. |
| 637 | |
Andrzej Pietrasiewicz | 02832e5 | 2013-05-28 09:15:56 +0200 | [diff] [blame] | 638 | config USB_CONFIGFS_ECM_SUBSET |
| 639 | boolean "Ethernet Control Model (CDC ECM) subset" |
| 640 | depends on USB_CONFIGFS |
| 641 | depends on NET |
| 642 | select USB_U_ETHER |
| 643 | select USB_F_SUBSET |
| 644 | help |
| 645 | On hardware that can't implement the full protocol, |
| 646 | a simple CDC subset is used, placing fewer demands on USB. |
| 647 | |
Andrzej Pietrasiewicz | b3df2fa | 2013-05-28 09:16:01 +0200 | [diff] [blame] | 648 | config USB_CONFIGFS_RNDIS |
| 649 | bool "RNDIS" |
| 650 | depends on USB_CONFIGFS |
| 651 | depends on NET |
| 652 | select USB_U_ETHER |
| 653 | select USB_F_RNDIS |
| 654 | help |
| 655 | Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol, |
| 656 | and Microsoft provides redistributable binary RNDIS drivers for |
| 657 | older versions of Windows. |
| 658 | |
| 659 | To make MS-Windows work with this, use Documentation/usb/linux.inf |
| 660 | as the "driver info file". For versions of MS-Windows older than |
| 661 | XP, you'll need to download drivers from Microsoft's website; a URL |
| 662 | is given in comments found in that info file. |
| 663 | |
Andrzej Pietrasiewicz | 17b8097 | 2013-05-28 09:15:51 +0200 | [diff] [blame] | 664 | config USB_CONFIGFS_EEM |
| 665 | bool "Ethernet Emulation Model (EEM)" |
| 666 | depends on USB_CONFIGFS |
| 667 | depends on NET |
| 668 | select USB_U_ETHER |
| 669 | select USB_F_EEM |
| 670 | help |
| 671 | CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM |
| 672 | and therefore can be supported by more hardware. Technically ECM and |
| 673 | EEM are designed for different applications. The ECM model extends |
| 674 | the network interface to the target (e.g. a USB cable modem), and the |
| 675 | EEM model is for mobile devices to communicate with hosts using |
| 676 | ethernet over USB. For Linux gadgets, however, the interface with |
| 677 | the host is the same (a usbX device), so the differences are minimal. |
| 678 | |
Andrzej Pietrasiewicz | 8340874 | 2013-05-23 10:51:15 +0200 | [diff] [blame] | 679 | config USB_CONFIGFS_PHONET |
| 680 | boolean "Phonet protocol" |
| 681 | depends on USB_CONFIGFS |
| 682 | depends on NET |
| 683 | depends on PHONET |
| 684 | select USB_U_ETHER |
| 685 | select USB_F_PHONET |
| 686 | help |
| 687 | The Phonet protocol implementation for USB device. |
| 688 | |
Andrzej Pietrasiewicz | ef0aa4b | 2013-10-09 10:06:05 +0200 | [diff] [blame] | 689 | config USB_CONFIGFS_MASS_STORAGE |
| 690 | boolean "Mass storage" |
| 691 | depends on USB_CONFIGFS |
Andrzej Pietrasiewicz | bc912b0 | 2013-11-04 13:46:17 +0100 | [diff] [blame] | 692 | depends on BLOCK |
Andrzej Pietrasiewicz | ef0aa4b | 2013-10-09 10:06:05 +0200 | [diff] [blame] | 693 | select USB_F_MASS_STORAGE |
| 694 | help |
| 695 | The Mass Storage Gadget acts as a USB Mass Storage disk drive. |
| 696 | As its storage repository it can use a regular file or a block |
| 697 | device (in much the same way as the "loop" device driver), |
| 698 | specified as a module parameter or sysfs option. |
| 699 | |
Andrzej Pietrasiewicz | 25d8015 | 2013-11-07 08:41:28 +0100 | [diff] [blame] | 700 | config USB_CONFIGFS_F_LB_SS |
| 701 | boolean "Loopback and sourcesink function (for testing)" |
Andrzej Pietrasiewicz | c0501f4 | 2013-11-07 08:41:27 +0100 | [diff] [blame] | 702 | depends on USB_CONFIGFS |
| 703 | select USB_F_SS_LB |
| 704 | help |
Andrzej Pietrasiewicz | 25d8015 | 2013-11-07 08:41:28 +0100 | [diff] [blame] | 705 | Loopback function loops back a configurable number of transfers. |
| 706 | Sourcesink function either sinks and sources bulk data. |
Andrzej Pietrasiewicz | c0501f4 | 2013-11-07 08:41:27 +0100 | [diff] [blame] | 707 | It also implements control requests, for "chapter 9" conformance. |
| 708 | Make this be the first driver you try using on top of any new |
| 709 | USB peripheral controller driver. Then you can use host-side |
| 710 | test software, like the "usbtest" driver, to put your hardware |
| 711 | and its driver through a basic set of functional tests. |
| 712 | |
Andrzej Pietrasiewicz | b658499 | 2013-12-03 15:15:36 +0100 | [diff] [blame] | 713 | config USB_CONFIGFS_F_FS |
| 714 | boolean "Function filesystem (FunctionFS)" |
| 715 | depends on USB_CONFIGFS |
| 716 | select USB_F_FS |
| 717 | help |
| 718 | The Function Filesystem (FunctionFS) lets one create USB |
| 719 | composite functions in user space in the same way GadgetFS |
| 720 | lets one create USB gadgets in user space. This allows creation |
| 721 | of composite gadgets such that some of the functions are |
| 722 | implemented in kernel space (for instance Ethernet, serial or |
| 723 | mass storage) and other are implemented in user space. |
| 724 | |
Andrzej Pietrasiewicz | 8443f2d | 2014-07-15 13:09:44 +0200 | [diff] [blame^] | 725 | source "drivers/usb/gadget/legacy/Kconfig" |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 726 | |
| 727 | endchoice |
| 728 | |
Denis Cheng | b75be4a | 2008-01-24 16:36:31 +0800 | [diff] [blame] | 729 | endif # USB_GADGET |