| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame^] | 1 | # |
| 2 | # USB Core configuration |
| 3 | # |
| 4 | config 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 | |
| 12 | comment "Miscellaneous USB options" |
| 13 | depends on USB |
| 14 | |
| 15 | config 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 | |
| 39 | config 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 | |
| 52 | config 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 | |
| 63 | config USB_SUSPEND |
| 64 | bool "USB suspend/resume (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. There are many related features, such as |
| 70 | remote wakeup and driver-specific suspend processing, that |
| 71 | may not yet work as expected. |
| 72 | |
| 73 | If you are unsure about this, say N here. |
| 74 | |
| 75 | |
| 76 | config USB_OTG |
| 77 | bool |
| 78 | depends on USB && EXPERIMENTAL |
| 79 | select USB_SUSPEND |
| 80 | default n |
| 81 | |
| 82 | |
| 83 | config USB_OTG_WHITELIST |
| 84 | bool "Rely on OTG Targeted Peripherals List" |
| 85 | depends on USB_OTG |
| 86 | default y |
| 87 | help |
| 88 | If you say Y here, the "otg_whitelist.h" file will be used as a |
| 89 | product whitelist, so USB peripherals not listed there will be |
| 90 | rejected during enumeration. This behavior is required by the |
| 91 | USB OTG specification for all devices not on your product's |
| 92 | "Targeted Peripherals List". |
| 93 | |
| 94 | Otherwise, peripherals not listed there will only generate a |
| 95 | warning and enumeration will continue. That's more like what |
| 96 | normal Linux-USB hosts do (other than the warning), and is |
| 97 | convenient for many stages of product development. |
| 98 | |
| 99 | |