Kconfig 3.2 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091
  1. #
  2. # USB Core configuration
  3. #
  4. config USB_DEBUG
  5. bool "USB verbose debug messages"
  6. help
  7. Say Y here if you want the USB core & hub drivers to produce a bunch
  8. of debug messages to the system log. Select this if you are having a
  9. problem with USB support and want to see more of what is going on.
  10. config USB_ANNOUNCE_NEW_DEVICES
  11. bool "USB announce new devices"
  12. default N
  13. help
  14. Say Y here if you want the USB core to always announce the
  15. idVendor, idProduct, Manufacturer, Product, and SerialNumber
  16. strings for every new USB device to the syslog. This option is
  17. usually used by distro vendors to help with debugging and to
  18. let users know what specific device was added to the machine
  19. in what location.
  20. If you do not want this kind of information sent to the system
  21. log, or have any doubts about this, say N here.
  22. comment "Miscellaneous USB options"
  23. config USB_DEFAULT_PERSIST
  24. bool "Enable USB persist by default"
  25. default y
  26. help
  27. Say N here if you don't want USB power session persistance
  28. enabled by default. If you say N it will make suspended USB
  29. devices that lose power get reenumerated as if they had been
  30. unplugged, causing any mounted filesystems to be lost. The
  31. persist feature can still be enabled for individual devices
  32. through the power/persist sysfs node. See
  33. Documentation/usb/persist.txt for more info.
  34. If you have any questions about this, say Y here, only say N
  35. if you know exactly what you are doing.
  36. config USB_DYNAMIC_MINORS
  37. bool "Dynamic USB minor allocation"
  38. help
  39. If you say Y here, the USB subsystem will use dynamic minor
  40. allocation for any device that uses the USB major number.
  41. This means that you can have more than 16 of a single type
  42. of device (like USB printers).
  43. If you are unsure about this, say N here.
  44. config USB_OTG
  45. bool "OTG support"
  46. depends on PM_RUNTIME
  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. Select this only if your board has Mini-AB/Micro-AB
  55. connector.
  56. config USB_OTG_WHITELIST
  57. bool "Rely on OTG Targeted Peripherals List"
  58. depends on USB_OTG || EXPERT
  59. default y if USB_OTG
  60. help
  61. If you say Y here, the "otg_whitelist.h" file will be used as a
  62. product whitelist, so USB peripherals not listed there will be
  63. rejected during enumeration. This behavior is required by the
  64. USB OTG specification for all devices not on your product's
  65. "Targeted Peripherals List". "Embedded Hosts" are likewise
  66. allowed to support only a limited number of peripherals.
  67. Otherwise, peripherals not listed there will only generate a
  68. warning and enumeration will continue. That's more like what
  69. normal Linux-USB hosts do (other than the warning), and is
  70. convenient for many stages of product development.
  71. config USB_OTG_BLACKLIST_HUB
  72. bool "Disable external hubs"
  73. depends on USB_OTG || EXPERT
  74. help
  75. If you say Y here, then Linux will refuse to enumerate
  76. external hubs. OTG hosts are allowed to reduce hardware
  77. and software costs by not supporting external hubs. So
  78. are "Embedded Hosts" that don't offer OTG support.