| Kconfig (cc9263874b42bf98209dce0afe698b550648e770) | Kconfig (bc49d1d17dcffd38bd872a4089e86bb7b2bb7eee) |
|---|---|
| 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). --- 195 unchanged lines hidden (view full) --- 204 tristate 205 206config USB_F_PRINTER 207 tristate 208 209config USB_F_TCM 210 tristate 211 | 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). --- 195 unchanged lines hidden (view full) --- 204 tristate 205 206config USB_F_PRINTER 207 tristate 208 209config USB_F_TCM 210 tristate 211 |
| 212choice 213 tristate "USB Gadget Drivers" 214 default USB_ETH 215 help 216 A Linux "Gadget Driver" talks to the USB Peripheral Controller 217 driver through the abstract "gadget" API. Some other operating 218 systems call these "client" drivers, of which "class drivers" 219 are a subset (implementing a USB device class specification). 220 A gadget driver implements one or more USB functions using 221 the peripheral hardware. 222 223 Gadget drivers are hardware-neutral, or "platform independent", 224 except that they sometimes must understand quirks or limitations 225 of the particular controllers they work with. For example, when 226 a controller doesn't support alternate configurations or provide 227 enough of the right types of endpoints, the gadget driver might 228 not be able work with that controller, or might need to implement 229 a less common variant of a device class protocol. 230 | |
| 231# this first set of drivers all depend on bulk-capable hardware. 232 233config USB_CONFIGFS 234 tristate "USB functions configurable through configfs" 235 select USB_LIBCOMPOSITE 236 help 237 A Linux USB "gadget" can be set up through configfs. 238 If this is the case, the USB functions (which from the host's --- 231 unchanged lines hidden (view full) --- 470 help 471 This fabric is a USB gadget component. Two USB protocols are 472 supported that is BBB or BOT (Bulk Only Transport) and UAS 473 (USB Attached SCSI). BOT is advertised on alternative 474 interface 0 (primary) and UAS is on alternative interface 1. 475 Both protocols can work on USB2.0 and USB3.0. 476 UAS utilizes the USB 3.0 feature called streams support. 477 | 212# this first set of drivers all depend on bulk-capable hardware. 213 214config USB_CONFIGFS 215 tristate "USB functions configurable through configfs" 216 select USB_LIBCOMPOSITE 217 help 218 A Linux USB "gadget" can be set up through configfs. 219 If this is the case, the USB functions (which from the host's --- 231 unchanged lines hidden (view full) --- 451 help 452 This fabric is a USB gadget component. Two USB protocols are 453 supported that is BBB or BOT (Bulk Only Transport) and UAS 454 (USB Attached SCSI). BOT is advertised on alternative 455 interface 0 (primary) and UAS is on alternative interface 1. 456 Both protocols can work on USB2.0 and USB3.0. 457 UAS utilizes the USB 3.0 feature called streams support. 458 |
| 459choice 460 tristate "USB Gadget Drivers" 461 default USB_ETH 462 help 463 A Linux "Gadget Driver" talks to the USB Peripheral Controller 464 driver through the abstract "gadget" API. Some other operating 465 systems call these "client" drivers, of which "class drivers" 466 are a subset (implementing a USB device class specification). 467 A gadget driver implements one or more USB functions using 468 the peripheral hardware. 469 470 Gadget drivers are hardware-neutral, or "platform independent", 471 except that they sometimes must understand quirks or limitations 472 of the particular controllers they work with. For example, when 473 a controller doesn't support alternate configurations or provide 474 enough of the right types of endpoints, the gadget driver might 475 not be able work with that controller, or might need to implement 476 a less common variant of a device class protocol. 477 |
|
| 478source "drivers/usb/gadget/legacy/Kconfig" 479 480endchoice 481 482endif # USB_GADGET | 478source "drivers/usb/gadget/legacy/Kconfig" 479 480endchoice 481 482endif # USB_GADGET |