1# 2# USB Core configuration 3# 4config USB_DEBUG 5 bool "USB verbose debug messages" 6 depends on USB 7 help 8 Say Y here if you want the USB core & hub drivers to produce a bunch 9 of debug messages to the system log. Select this if you are having a 10 problem with USB support and want to see more of what is going on. 11 12comment "Miscellaneous USB options" 13 depends on USB 14 15config USB_DEVICEFS 16 bool "USB device filesystem" 17 depends on USB 18 ---help--- 19 If you say Y here (and to "/proc file system support" in the "File 20 systems" section, above), you will get a file /proc/bus/usb/devices 21 which lists the devices currently connected to your USB bus or 22 busses, and for every connected device a file named 23 "/proc/bus/usb/xxx/yyy", where xxx is the bus number and yyy the 24 device number; the latter files can be used by user space programs 25 to talk directly to the device. These files are "virtual", meaning 26 they are generated on the fly and not stored on the hard drive. 27 28 You may need to mount the usbfs file system to see the files, use 29 mount -t usbfs none /proc/bus/usb 30 31 For the format of the various /proc/bus/usb/ files, please read 32 <file:Documentation/usb/proc_usb_info.txt>. 33 34 Please note that this code is completely unrelated to devfs, the 35 "/dev file system support". 36 37 Most users want to say Y here. 38 39config USB_BANDWIDTH 40 bool "Enforce USB bandwidth allocation (EXPERIMENTAL)" 41 depends on USB && EXPERIMENTAL 42 help 43 If you say Y here, the USB subsystem enforces USB bandwidth 44 allocation and will prevent some device opens from succeeding 45 if they would cause USB bandwidth usage to go above 90% of 46 the bus bandwidth. 47 48 If you say N here, these conditions will cause warning messages 49 about USB bandwidth usage to be logged and some devices or 50 drivers may not work correctly. 51 52config USB_DYNAMIC_MINORS 53 bool "Dynamic USB minor allocation (EXPERIMENTAL)" 54 depends on USB && EXPERIMENTAL 55 help 56 If you say Y here, the USB subsystem will use dynamic minor 57 allocation for any device that uses the USB major number. 58 This means that you can have more than 16 of a single type 59 of device (like USB printers). 60 61 If you are unsure about this, say N here. 62 63config USB_SUSPEND 64 bool "USB selective suspend/resume and wakeup (EXPERIMENTAL)" 65 depends on USB && PM && EXPERIMENTAL 66 help 67 If you say Y here, you can use driver calls or the sysfs 68 "power/state" file to suspend or resume individual USB 69 peripherals. 70 71 Also, USB "remote wakeup" signaling is supported, whereby some 72 USB devices (like keyboards and network adapters) can wake up 73 their parent hub. That wakeup cascades up the USB tree, and 74 could wake the system from states like suspend-to-RAM. 75 76 If you are unsure about this, say N here. 77 78 79config USB_OTG 80 bool 81 depends on USB && EXPERIMENTAL 82 select USB_SUSPEND 83 default n 84 85 86config USB_OTG_WHITELIST 87 bool "Rely on OTG Targeted Peripherals List" 88 depends on USB_OTG 89 default y 90 help 91 If you say Y here, the "otg_whitelist.h" file will be used as a 92 product whitelist, so USB peripherals not listed there will be 93 rejected during enumeration. This behavior is required by the 94 USB OTG specification for all devices not on your product's 95 "Targeted Peripherals List". 96 97 Otherwise, peripherals not listed there will only generate a 98 warning and enumeration will continue. That's more like what 99 normal Linux-USB hosts do (other than the warning), and is 100 convenient for many stages of product development. 101 102 103