Kconfig 5.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199
  1. #
  2. # USB device configuration
  3. #
  4. config USB_OHCI_BIG_ENDIAN_DESC
  5. bool
  6. config USB_OHCI_BIG_ENDIAN_MMIO
  7. bool
  8. config USB_OHCI_LITTLE_ENDIAN
  9. bool
  10. default n if STB03xxx || PPC_MPC52xx
  11. default y
  12. config USB_EHCI_BIG_ENDIAN_MMIO
  13. bool
  14. config USB_EHCI_BIG_ENDIAN_DESC
  15. bool
  16. menuconfig USB_SUPPORT
  17. bool "USB support"
  18. depends on HAS_IOMEM
  19. default y
  20. ---help---
  21. This option adds core support for Universal Serial Bus (USB).
  22. You will also need drivers from the following menu to make use of it.
  23. if USB_SUPPORT
  24. config USB_COMMON
  25. tristate
  26. config USB_ARCH_HAS_HCD
  27. def_bool y
  28. config USB
  29. tristate "Support for Host-side USB"
  30. depends on USB_ARCH_HAS_HCD
  31. select USB_COMMON
  32. select NLS # for UTF-8 strings
  33. ---help---
  34. Universal Serial Bus (USB) is a specification for a serial bus
  35. subsystem which offers higher speeds and more features than the
  36. traditional PC serial port. The bus supplies power to peripherals
  37. and allows for hot swapping. Up to 127 USB peripherals can be
  38. connected to a single USB host in a tree structure.
  39. The USB host is the root of the tree, the peripherals are the
  40. leaves and the inner nodes are special USB devices called hubs.
  41. Most PCs now have USB host ports, used to connect peripherals
  42. such as scanners, keyboards, mice, modems, cameras, disks,
  43. flash memory, network links, and printers to the PC.
  44. Say Y here if your computer has a host-side USB port and you want
  45. to use USB devices. You then need to say Y to at least one of the
  46. Host Controller Driver (HCD) options below. Choose a USB 1.1
  47. controller, such as "UHCI HCD support" or "OHCI HCD support",
  48. and "EHCI HCD (USB 2.0) support" except for older systems that
  49. do not have USB 2.0 support. It doesn't normally hurt to select
  50. them all if you are not certain.
  51. If your system has a device-side USB port, used in the peripheral
  52. side of the USB protocol, see the "USB Gadget" framework instead.
  53. After choosing your HCD, then select drivers for the USB peripherals
  54. you'll be using. You may want to check out the information provided
  55. in <file:Documentation/usb/> and especially the links given in
  56. <file:Documentation/usb/usb-help.txt>.
  57. To compile this driver as a module, choose M here: the
  58. module will be called usbcore.
  59. config USB_PCI
  60. bool "PCI based USB host interface"
  61. depends on PCI
  62. default y
  63. ---help---
  64. A lot of embeded system SOC (e.g. freescale T2080) have both
  65. PCI and USB modules. But USB module is controlled by registers
  66. directly, it have no relationship with PCI module.
  67. When say N here it will not build PCI related code in USB driver.
  68. if USB
  69. source "drivers/usb/core/Kconfig"
  70. source "drivers/usb/mon/Kconfig"
  71. source "drivers/usb/wusbcore/Kconfig"
  72. source "drivers/usb/host/Kconfig"
  73. source "drivers/usb/renesas_usbhs/Kconfig"
  74. source "drivers/usb/class/Kconfig"
  75. source "drivers/usb/storage/Kconfig"
  76. source "drivers/usb/image/Kconfig"
  77. source "drivers/usb/usbip/Kconfig"
  78. endif
  79. source "drivers/usb/mtu3/Kconfig"
  80. source "drivers/usb/musb/Kconfig"
  81. source "drivers/usb/dwc3/Kconfig"
  82. source "drivers/usb/dwc2/Kconfig"
  83. source "drivers/usb/chipidea/Kconfig"
  84. source "drivers/usb/isp1760/Kconfig"
  85. comment "USB port drivers"
  86. if USB
  87. config USB_USS720
  88. tristate "USS720 parport driver"
  89. depends on PARPORT
  90. select PARPORT_NOT_PC
  91. ---help---
  92. This driver is for USB parallel port adapters that use the Lucent
  93. Technologies USS-720 chip. These cables are plugged into your USB
  94. port and provide USB compatibility to peripherals designed with
  95. parallel port interfaces.
  96. The chip has two modes: automatic mode and manual mode. In automatic
  97. mode, it looks to the computer like a standard USB printer. Only
  98. printers may be connected to the USS-720 in this mode. The generic
  99. USB printer driver ("USB Printer support", above) may be used in
  100. that mode, and you can say N here if you want to use the chip only
  101. in this mode.
  102. Manual mode is not limited to printers, any parallel port
  103. device should work. This driver utilizes manual mode.
  104. Note however that some operations are three orders of magnitude
  105. slower than on a PCI/ISA Parallel Port, so timing critical
  106. applications might not work.
  107. Say Y here if you own an USS-720 USB->Parport cable and intend to
  108. connect anything other than a printer to it.
  109. To compile this driver as a module, choose M here: the
  110. module will be called uss720.
  111. source "drivers/usb/serial/Kconfig"
  112. source "drivers/usb/misc/Kconfig"
  113. source "drivers/usb/atm/Kconfig"
  114. endif # USB
  115. source "drivers/usb/phy/Kconfig"
  116. source "drivers/usb/gadget/Kconfig"
  117. source "drivers/usb/typec/Kconfig"
  118. config USB_LED_TRIG
  119. bool "USB LED Triggers"
  120. depends on LEDS_CLASS && LEDS_TRIGGERS
  121. select USB_COMMON
  122. help
  123. This option adds LED triggers for USB host and/or gadget activity.
  124. Say Y here if you are working on a system with led-class supported
  125. LEDs and you want to use them as activity indicators for USB host or
  126. gadget.
  127. config USB_ULPI_BUS
  128. tristate "USB ULPI PHY interface support"
  129. select USB_COMMON
  130. help
  131. UTMI+ Low Pin Interface (ULPI) is specification for a commonly used
  132. USB 2.0 PHY interface. The ULPI specification defines a standard set
  133. of registers that can be used to detect the vendor and product which
  134. allows ULPI to be handled as a bus. This module is the driver for that
  135. bus.
  136. The ULPI interfaces (the buses) are registered by the drivers for USB
  137. controllers which support ULPI register access and have ULPI PHY
  138. attached to them. The ULPI PHY drivers themselves are normal PHY
  139. drivers.
  140. ULPI PHYs provide often functions such as ADP sensing/probing (OTG
  141. protocol) and USB charger detection.
  142. To compile this driver as a module, choose M here: the module will
  143. be called ulpi.
  144. endif # USB_SUPPORT