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. 106