2fc0f88a3d860818947002ed91d8213a51d22f8f
[deliverable/linux.git] / drivers / usb / core / Kconfig
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 Most users want to say Y here.
35
36 config USB_DYNAMIC_MINORS
37 bool "Dynamic USB minor allocation (EXPERIMENTAL)"
38 depends on USB && EXPERIMENTAL
39 help
40 If you say Y here, the USB subsystem will use dynamic minor
41 allocation for any device that uses the USB major number.
42 This means that you can have more than 16 of a single type
43 of device (like USB printers).
44
45 If you are unsure about this, say N here.
46
47 config USB_SUSPEND
48 bool "USB selective suspend/resume and wakeup (EXPERIMENTAL)"
49 depends on USB && PM && EXPERIMENTAL
50 help
51 If you say Y here, you can use driver calls or the sysfs
52 "power/state" file to suspend or resume individual USB
53 peripherals.
54
55 Also, USB "remote wakeup" signaling is supported, whereby some
56 USB devices (like keyboards and network adapters) can wake up
57 their parent hub. That wakeup cascades up the USB tree, and
58 could wake the system from states like suspend-to-RAM.
59
60 If you are unsure about this, say N here.
61
62 config USB_OTG
63 bool
64 depends on USB && EXPERIMENTAL
65 select USB_SUSPEND
66 default n
67
68
69 config USB_OTG_WHITELIST
70 bool "Rely on OTG Targeted Peripherals List"
71 depends on USB_OTG
72 default y
73 help
74 If you say Y here, the "otg_whitelist.h" file will be used as a
75 product whitelist, so USB peripherals not listed there will be
76 rejected during enumeration. This behavior is required by the
77 USB OTG specification for all devices not on your product's
78 "Targeted Peripherals List".
79
80 Otherwise, peripherals not listed there will only generate a
81 warning and enumeration will continue. That's more like what
82 normal Linux-USB hosts do (other than the warning), and is
83 convenient for many stages of product development.
84
85 config USB_OTG_BLACKLIST_HUB
86 bool "Disable external hubs"
87 depends on USB_OTG
88 help
89 If you say Y here, then Linux will refuse to enumerate
90 external hubs. OTG hosts are allowed to reduce hardware
91 and software costs by not supporting external hubs.
92
This page took 0.031701 seconds and 4 git commands to generate.