Kconfig revision f3f3253d644d36a2ea5464005a9c2cf28804d200
11da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds# 21da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds# USB Core configuration 31da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds# 41da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvaldsconfig USB_DEBUG 51da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds bool "USB verbose debug messages" 61da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds depends on USB 71da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds help 81da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds Say Y here if you want the USB core & hub drivers to produce a bunch 91da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds of debug messages to the system log. Select this if you are having a 101da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds problem with USB support and want to see more of what is going on. 111da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 121da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvaldscomment "Miscellaneous USB options" 131da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds depends on USB 141da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 151da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvaldsconfig USB_DEVICEFS 161da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds bool "USB device filesystem" 171da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds depends on USB 181da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds ---help--- 191da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds If you say Y here (and to "/proc file system support" in the "File 201da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds systems" section, above), you will get a file /proc/bus/usb/devices 211da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds which lists the devices currently connected to your USB bus or 221da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds busses, and for every connected device a file named 231da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds "/proc/bus/usb/xxx/yyy", where xxx is the bus number and yyy the 241da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds device number; the latter files can be used by user space programs 251da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds to talk directly to the device. These files are "virtual", meaning 261da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds they are generated on the fly and not stored on the hard drive. 271da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 281da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds You may need to mount the usbfs file system to see the files, use 291da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds mount -t usbfs none /proc/bus/usb 301da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 311da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds For the format of the various /proc/bus/usb/ files, please read 321da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds <file:Documentation/usb/proc_usb_info.txt>. 331da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 341da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds Please note that this code is completely unrelated to devfs, the 351da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds "/dev file system support". 361da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 371da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds Most users want to say Y here. 381da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 391da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvaldsconfig USB_BANDWIDTH 401da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds bool "Enforce USB bandwidth allocation (EXPERIMENTAL)" 411da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds depends on USB && EXPERIMENTAL 421da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds help 431da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds If you say Y here, the USB subsystem enforces USB bandwidth 441da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds allocation and will prevent some device opens from succeeding 451da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds if they would cause USB bandwidth usage to go above 90% of 461da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds the bus bandwidth. 471da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 481da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds If you say N here, these conditions will cause warning messages 491da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds about USB bandwidth usage to be logged and some devices or 501da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds drivers may not work correctly. 511da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 521da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvaldsconfig USB_DYNAMIC_MINORS 531da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds bool "Dynamic USB minor allocation (EXPERIMENTAL)" 541da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds depends on USB && EXPERIMENTAL 551da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds help 561da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds If you say Y here, the USB subsystem will use dynamic minor 571da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds allocation for any device that uses the USB major number. 581da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds This means that you can have more than 16 of a single type 591da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds of device (like USB printers). 601da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 611da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds If you are unsure about this, say N here. 621da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 631da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvaldsconfig USB_SUSPEND 64f3f3253d644d36a2ea5464005a9c2cf28804d200David Brownell bool "USB selective suspend/resume and wakeup (EXPERIMENTAL)" 651da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds depends on USB && PM && EXPERIMENTAL 661da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds help 671da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds If you say Y here, you can use driver calls or the sysfs 681da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds "power/state" file to suspend or resume individual USB 69f3f3253d644d36a2ea5464005a9c2cf28804d200David Brownell peripherals. 70f3f3253d644d36a2ea5464005a9c2cf28804d200David Brownell 71f3f3253d644d36a2ea5464005a9c2cf28804d200David Brownell Also, USB "remote wakeup" signaling is supported, whereby some 72f3f3253d644d36a2ea5464005a9c2cf28804d200David Brownell USB devices (like keyboards and network adapters) can wake up 73f3f3253d644d36a2ea5464005a9c2cf28804d200David Brownell their parent hub. That wakeup cascades up the USB tree, and 74f3f3253d644d36a2ea5464005a9c2cf28804d200David Brownell could wake the system from states like suspend-to-RAM. 751da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 761da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds If you are unsure about this, say N here. 771da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 781da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 791da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvaldsconfig USB_OTG 801da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds bool 811da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds depends on USB && EXPERIMENTAL 821da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds select USB_SUSPEND 831da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds default n 841da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 851da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 861da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvaldsconfig USB_OTG_WHITELIST 871da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds bool "Rely on OTG Targeted Peripherals List" 881da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds depends on USB_OTG 891da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds default y 901da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds help 911da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds If you say Y here, the "otg_whitelist.h" file will be used as a 921da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds product whitelist, so USB peripherals not listed there will be 931da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds rejected during enumeration. This behavior is required by the 941da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds USB OTG specification for all devices not on your product's 951da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds "Targeted Peripherals List". 961da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 971da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds Otherwise, peripherals not listed there will only generate a 981da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds warning and enumeration will continue. That's more like what 991da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds normal Linux-USB hosts do (other than the warning), and is 1001da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds convenient for many stages of product development. 1011da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 1021da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 103