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
 12config 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
 27comment "Miscellaneous USB options"
 28	depends on USB
 29
 30config USB_DEVICEFS
 31	bool "USB device filesystem (DEPRECATED)"
 32	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
 49	  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.
 58
 59config USB_DEVICE_CLASS
 60	bool "USB device class-devices (DEPRECATED)"
 61	depends on USB
 62	default y
 63	---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
 69	  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.
 75
 76	  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"
 81
 82config USB_DYNAMIC_MINORS
 83	bool "Dynamic USB minor allocation"
 84	depends on USB
 85	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
 94	bool "USB runtime power management (autosuspend) and wakeup"
 95	depends on USB && PM_RUNTIME
 96	help
 97	  If you say Y here, you can use driver calls or the sysfs
 98	  "power/control" file to enable or disable autosuspend for
 99	  individual USB peripherals (see
100	  Documentation/usb/power-management.txt for more details).
101
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.
106
107	  If you are unsure about this, say N here.
108
109config USB_OTG
110	bool "OTG support"
111	depends on USB && EXPERIMENTAL
112	depends on USB_SUSPEND
113	default n
114	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.
120
121	  Select this only if your board has Mini-AB/Micro-AB
122	  connector.
123
124config USB_OTG_WHITELIST
125	bool "Rely on OTG Targeted Peripherals List"
126	depends on USB_OTG || EXPERT
127	default y if USB_OTG
128	default n if EXPERT
129	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
134	  "Targeted Peripherals List".  "Embedded Hosts" are likewise
135	  allowed to support only a limited number of peripherals.
136
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
142config USB_OTG_BLACKLIST_HUB
143	bool "Disable external hubs"
144	depends on USB_OTG || EXPERT
145	help
146	  If you say Y here, then Linux will refuse to enumerate
147	  external hubs.  OTG hosts are allowed to reduce hardware
148	  and software costs by not supporting external hubs.  So
149	  are "Embedded Hosts" that don't offer OTG support.
150

  1#
  2# USB Core configuration
  3#
 
 
 
 
 
 
 
 
  4config USB_ANNOUNCE_NEW_DEVICES
  5	bool "USB announce new devices"
 
 
  6	help
  7	  Say Y here if you want the USB core to always announce the
  8	  idVendor, idProduct, Manufacturer, Product, and SerialNumber
  9	  strings for every new USB device to the syslog.  This option is
 10	  usually used by distro vendors to help with debugging and to
 11	  let users know what specific device was added to the machine
 12	  in what location.
 13
 14	  If you do not want this kind of information sent to the system
 15	  log, or have any doubts about this, say N here.
 16
 17comment "Miscellaneous USB options"
 
 18
 19config USB_DEFAULT_PERSIST
 20	bool "Enable USB persist by default"
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 21	default y
 22	help
 23	  Say N here if you don't want USB power session persistence
 24	  enabled by default.  If you say N it will make suspended USB
 25	  devices that lose power get reenumerated as if they had been
 26	  unplugged, causing any mounted filesystems to be lost.  The
 27	  persist feature can still be enabled for individual devices
 28	  through the power/persist sysfs node. See
 29	  Documentation/usb/persist.txt for more info.
 30
 31	  If you have any questions about this, say Y here, only say N
 32	  if you know exactly what you are doing.
 
 
 
 
 
 
 
 33
 34config USB_DYNAMIC_MINORS
 35	bool "Dynamic USB minor allocation"
 
 36	help
 37	  If you say Y here, the USB subsystem will use dynamic minor
 38	  allocation for any device that uses the USB major number.
 39	  This means that you can have more than 16 of a single type
 40	  of device (like USB printers).
 41
 42	  If you are unsure about this, say N here.
 43
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 44config USB_OTG
 45	bool "OTG support"
 46	depends on PM
 
 47	default n
 48	help
 49	  The most notable feature of USB OTG is support for a
 50	  "Dual-Role" device, which can act as either a device
 51	  or a host. The initial role is decided by the type of
 52	  plug inserted and can be changed later when two dual
 53	  role devices talk to each other.
 54
 55	  Select this only if your board has Mini-AB/Micro-AB
 56	  connector.
 57
 58config USB_OTG_WHITELIST
 59	bool "Rely on OTG and EH Targeted Peripherals List"
 60	depends on USB
 
 
 61	help
 62	  If you say Y here, the "otg_whitelist.h" file will be used as a
 63	  product whitelist, so USB peripherals not listed there will be
 64	  rejected during enumeration.  This behavior is required by the
 65	  USB OTG and EH specification for all devices not on your product's
 66	  "Targeted Peripherals List".  "Embedded Hosts" are likewise
 67	  allowed to support only a limited number of peripherals.
 68
 
 
 
 
 
 69config USB_OTG_BLACKLIST_HUB
 70	bool "Disable external hubs"
 71	depends on USB_OTG || EXPERT
 72	help
 73	  If you say Y here, then Linux will refuse to enumerate
 74	  external hubs.  OTG hosts are allowed to reduce hardware
 75	  and software costs by not supporting external hubs.  So
 76	  are "Embedded Hosts" that don't offer OTG support.
 77
 78config USB_OTG_FSM
 79	tristate "USB 2.0 OTG FSM implementation"
 80	depends on USB && USB_OTG
 81	select USB_PHY
 82	help
 83	  Implements OTG Finite State Machine as specified in On-The-Go
 84	  and Embedded Host Supplement to the USB Revision 2.0 Specification.
 85
 86config USB_ULPI_BUS
 87	tristate "USB ULPI PHY interface support"
 88	depends on USB_SUPPORT
 89	help
 90	  UTMI+ Low Pin Interface (ULPI) is specification for a commonly used
 91	  USB 2.0 PHY interface. The ULPI specification defines a standard set
 92	  of registers that can be used to detect the vendor and product which
 93	  allows ULPI to be handled as a bus. This module is the driver for that
 94	  bus.
 95
 96	  The ULPI interfaces (the buses) are registered by the drivers for USB
 97	  controllers which support ULPI register access and have ULPI PHY
 98	  attached to them. The ULPI PHY drivers themselves are normal PHY
 99	  drivers.
100
101	  ULPI PHYs provide often functions such as ADP sensing/probing (OTG
102	  protocol) and USB charger detection.
103
104	  To compile this driver as a module, choose M here: the module will
105	  be called ulpi.