Merge branch 'next/drivers' into HEAD
[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 config USB_ANNOUNCE_NEW_DEVICES
13 bool "USB announce new devices"
14 depends on USB
15 default N
16 help
17 Say Y here if you want the USB core to always announce the
18 idVendor, idProduct, Manufacturer, Product, and SerialNumber
19 strings for every new USB device to the syslog. This option is
20 usually used by distro vendors to help with debugging and to
21 let users know what specific device was added to the machine
22 in what location.
23
24 If you do not want this kind of information sent to the system
25 log, or have any doubts about this, say N here.
26
27 comment "Miscellaneous USB options"
28 depends on USB
29
30 config USB_DYNAMIC_MINORS
31 bool "Dynamic USB minor allocation"
32 depends on USB
33 help
34 If you say Y here, the USB subsystem will use dynamic minor
35 allocation for any device that uses the USB major number.
36 This means that you can have more than 16 of a single type
37 of device (like USB printers).
38
39 If you are unsure about this, say N here.
40
41 config USB_SUSPEND
42 bool "USB runtime power management (autosuspend) and wakeup"
43 depends on USB && PM_RUNTIME
44 help
45 If you say Y here, you can use driver calls or the sysfs
46 "power/control" file to enable or disable autosuspend for
47 individual USB peripherals (see
48 Documentation/usb/power-management.txt for more details).
49
50 Also, USB "remote wakeup" signaling is supported, whereby some
51 USB devices (like keyboards and network adapters) can wake up
52 their parent hub. That wakeup cascades up the USB tree, and
53 could wake the system from states like suspend-to-RAM.
54
55 If you are unsure about this, say N here.
56
57 config USB_OTG
58 bool "OTG support"
59 depends on USB
60 depends on USB_SUSPEND
61 default n
62 help
63 The most notable feature of USB OTG is support for a
64 "Dual-Role" device, which can act as either a device
65 or a host. The initial role is decided by the type of
66 plug inserted and can be changed later when two dual
67 role devices talk to each other.
68
69 Select this only if your board has Mini-AB/Micro-AB
70 connector.
71
72 config USB_OTG_WHITELIST
73 bool "Rely on OTG Targeted Peripherals List"
74 depends on USB_OTG || EXPERT
75 default y if USB_OTG
76 help
77 If you say Y here, the "otg_whitelist.h" file will be used as a
78 product whitelist, so USB peripherals not listed there will be
79 rejected during enumeration. This behavior is required by the
80 USB OTG specification for all devices not on your product's
81 "Targeted Peripherals List". "Embedded Hosts" are likewise
82 allowed to support only a limited number of peripherals.
83
84 Otherwise, peripherals not listed there will only generate a
85 warning and enumeration will continue. That's more like what
86 normal Linux-USB hosts do (other than the warning), and is
87 convenient for many stages of product development.
88
89 config USB_OTG_BLACKLIST_HUB
90 bool "Disable external hubs"
91 depends on USB_OTG || EXPERT
92 help
93 If you say Y here, then Linux will refuse to enumerate
94 external hubs. OTG hosts are allowed to reduce hardware
95 and software costs by not supporting external hubs. So
96 are "Embedded Hosts" that don't offer OTG support.
97
This page took 0.047644 seconds and 5 git commands to generate.