blob: 18d02e32a3d5f6d38adcd3f1f90bafc4a84a6f1c [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
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
Greg Kroah-Hartmanf2a383e2007-11-26 22:11:55 -080012config 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
Linus Torvalds1da177e2005-04-16 15:20:36 -070027comment "Miscellaneous USB options"
28 depends on USB
29
30config USB_DEVICEFS
Greg Kroah-Hartmane12df022009-07-09 21:35:49 -070031 bool "USB device filesystem (DEPRECATED)"
Linus Torvalds1da177e2005-04-16 15:20:36 -070032 depends on USB
33 ---help---
34 If you say Y here (and to "/proc file system support" in the "File
35 systems" section, above), you will get a file /proc/bus/usb/devices
36 which lists the devices currently connected to your USB bus or
37 busses, and for every connected device a file named
38 "/proc/bus/usb/xxx/yyy", where xxx is the bus number and yyy the
39 device number; the latter files can be used by user space programs
40 to talk directly to the device. These files are "virtual", meaning
41 they are generated on the fly and not stored on the hard drive.
42
43 You may need to mount the usbfs file system to see the files, use
44 mount -t usbfs none /proc/bus/usb
45
46 For the format of the various /proc/bus/usb/ files, please read
47 <file:Documentation/usb/proc_usb_info.txt>.
48
Scott James Remnantcc713292009-04-21 17:21:40 +010049 Modern Linux systems do not use this.
50
51 Usbfs entries are files and not character devices; usbfs can't
52 handle Access Control Lists (ACL) which are the default way to
53 grant access to USB devices for untrusted users of a desktop
54 system.
55
56 The usbfs functionality is replaced by real device-nodes managed by
57 udev. These nodes lived in /dev/bus/usb and are used by libusb.
Kay Sievers9f8b17e2007-03-13 15:59:31 +010058
59config USB_DEVICE_CLASS
60 bool "USB device class-devices (DEPRECATED)"
61 depends on USB
Kay Sieversdda034b2007-05-27 17:04:58 +020062 default y
Kay Sievers9f8b17e2007-03-13 15:59:31 +010063 ---help---
64 Userspace access to USB devices is granted by device-nodes exported
65 directly from the usbdev in sysfs. Old versions of the driver
66 core and udev needed additional class devices to export device nodes.
67
68 These additional devices are difficult to handle in userspace, if
Kay Sieversdda034b2007-05-27 17:04:58 +020069 information about USB interfaces must be available. One device
70 contains the device node, the other device contains the interface
71 data. Both devices are at the same level in sysfs (siblings) and one
72 can't access the other. The device node created directly by the
73 usb device is the parent device of the interface and therefore
74 easily accessible from the interface event.
Kay Sievers9f8b17e2007-03-13 15:59:31 +010075
Kay Sieversdda034b2007-05-27 17:04:58 +020076 This option provides backward compatibility for libusb device
77 nodes (lsusb) when usbfs is not used, and the following udev rule
78 doesn't exist:
79 SUBSYSTEM=="usb", ACTION=="add", ENV{DEVTYPE}=="usb_device", \
80 NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", MODE="0644"
Linus Torvalds1da177e2005-04-16 15:20:36 -070081
Linus Torvalds1da177e2005-04-16 15:20:36 -070082config USB_DYNAMIC_MINORS
Robert P. J. Dayb6719992008-03-08 03:12:44 -050083 bool "Dynamic USB minor allocation"
84 depends on USB
Linus Torvalds1da177e2005-04-16 15:20:36 -070085 help
86 If you say Y here, the USB subsystem will use dynamic minor
87 allocation for any device that uses the USB major number.
88 This means that you can have more than 16 of a single type
89 of device (like USB printers).
90
91 If you are unsure about this, say N here.
92
93config USB_SUSPEND
Alan Stern2dab3942010-09-24 11:41:46 -040094 bool "USB runtime power management (autosuspend) and wakeup"
Alan Stern9bbdf1e2010-01-08 12:57:28 -050095 depends on USB && PM_RUNTIME
Linus Torvalds1da177e2005-04-16 15:20:36 -070096 help
97 If you say Y here, you can use driver calls or the sysfs
Alan Stern2dab3942010-09-24 11:41:46 -040098 "power/control" file to enable or disable autosuspend for
99 individual USB peripherals (see
Alan Sternc2c8d1f2008-02-25 11:43:32 -0500100 Documentation/usb/power-management.txt for more details).
David Brownellf3f32532005-09-22 22:37:29 -0700101
102 Also, USB "remote wakeup" signaling is supported, whereby some
103 USB devices (like keyboards and network adapters) can wake up
104 their parent hub. That wakeup cascades up the USB tree, and
105 could wake the system from states like suspend-to-RAM.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700106
107 If you are unsure about this, say N here.
108
Linus Torvalds1da177e2005-04-16 15:20:36 -0700109config USB_OTG
Pavankumar Kondetif4ce9082010-12-16 14:32:24 +0530110 bool "OTG support"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700111 depends on USB && EXPERIMENTAL
Anand Gadiyar6d602612010-03-29 16:54:51 +0530112 depends on USB_SUSPEND
Linus Torvalds1da177e2005-04-16 15:20:36 -0700113 default n
Pavankumar Kondetif4ce9082010-12-16 14:32:24 +0530114 help
115 The most notable feature of USB OTG is support for a
116 "Dual-Role" device, which can act as either a device
117 or a host. The initial role is decided by the type of
118 plug inserted and can be changed later when two dual
119 role devices talk to each other.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700120
Pavankumar Kondetif4ce9082010-12-16 14:32:24 +0530121 Select this only if your board has Mini-AB/Micro-AB
122 connector.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700123
124config USB_OTG_WHITELIST
125 bool "Rely on OTG Targeted Peripherals List"
David Rientjes6a108a12011-01-20 14:44:16 -0800126 depends on USB_OTG || EXPERT
Robin Getz22552b22008-03-05 23:17:38 -0800127 default y if USB_OTG
David Rientjes6a108a12011-01-20 14:44:16 -0800128 default n if EXPERT
Linus Torvalds1da177e2005-04-16 15:20:36 -0700129 help
130 If you say Y here, the "otg_whitelist.h" file will be used as a
131 product whitelist, so USB peripherals not listed there will be
132 rejected during enumeration. This behavior is required by the
133 USB OTG specification for all devices not on your product's
Robin Getz22552b22008-03-05 23:17:38 -0800134 "Targeted Peripherals List". "Embedded Hosts" are likewise
135 allowed to support only a limited number of peripherals.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700136
137 Otherwise, peripherals not listed there will only generate a
138 warning and enumeration will continue. That's more like what
139 normal Linux-USB hosts do (other than the warning), and is
140 convenient for many stages of product development.
141
David Brownell89ccbdc2006-04-02 10:18:09 -0800142config USB_OTG_BLACKLIST_HUB
143 bool "Disable external hubs"
David Rientjes6a108a12011-01-20 14:44:16 -0800144 depends on USB_OTG || EXPERT
David Brownell89ccbdc2006-04-02 10:18:09 -0800145 help
146 If you say Y here, then Linux will refuse to enumerate
147 external hubs. OTG hosts are allowed to reduce hardware
Robin Getz22552b22008-03-05 23:17:38 -0800148 and software costs by not supporting external hubs. So
Peter Korsgaardbc45df92008-09-08 10:14:47 +0200149 are "Embedded Hosts" that don't offer OTG support.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700150