Kconfig 3.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596
  1. config USB_DWC2
  2. tristate "DesignWare USB2 DRD Core Support"
  3. depends on HAS_DMA
  4. depends on USB || USB_GADGET
  5. depends on HAS_IOMEM
  6. help
  7. Say Y here if your system has a Dual Role Hi-Speed USB
  8. controller based on the DesignWare HSOTG IP Core.
  9. For host mode, if you choose to build the driver as dynamically
  10. linked modules, the core module will be called dwc2.ko, the PCI
  11. bus interface module (if you have a PCI bus system) will be
  12. called dwc2_pci.ko, and the platform interface module (for
  13. controllers directly connected to the CPU) will be called
  14. dwc2_platform.ko. For all modes(host, gadget and dual-role), there
  15. will be an additional module named dwc2.ko.
  16. if USB_DWC2
  17. choice
  18. bool "DWC2 Mode Selection"
  19. default USB_DWC2_DUAL_ROLE if (USB && USB_GADGET)
  20. default USB_DWC2_HOST if (USB && !USB_GADGET)
  21. default USB_DWC2_PERIPHERAL if (!USB && USB_GADGET)
  22. config USB_DWC2_HOST
  23. bool "Host only mode"
  24. depends on USB=y || (USB_DWC2=m && USB)
  25. help
  26. The Designware USB2.0 high-speed host controller
  27. integrated into many SoCs. Select this option if you want the
  28. driver to operate in Host-only mode.
  29. comment "Gadget/Dual-role mode requires USB Gadget support to be enabled"
  30. config USB_DWC2_PERIPHERAL
  31. bool "Gadget only mode"
  32. depends on USB_GADGET=y || USB_GADGET=USB_DWC2
  33. help
  34. The Designware USB2.0 high-speed gadget controller
  35. integrated into many SoCs. Select this option if you want the
  36. driver to operate in Peripheral-only mode. This option requires
  37. USB_GADGET to be enabled.
  38. config USB_DWC2_DUAL_ROLE
  39. bool "Dual Role mode"
  40. depends on (USB=y && USB_GADGET=y) || (USB_DWC2=m && USB && USB_GADGET)
  41. help
  42. Select this option if you want the driver to work in a dual-role
  43. mode. In this mode both host and gadget features are enabled, and
  44. the role will be determined by the cable that gets plugged-in. This
  45. option requires USB_GADGET to be enabled.
  46. endchoice
  47. config USB_DWC2_PCI
  48. tristate "DWC2 PCI"
  49. depends on USB_PCI
  50. depends on USB_GADGET || !USB_GADGET
  51. default n
  52. select NOP_USB_XCEIV
  53. help
  54. The Designware USB2.0 PCI interface module for controllers
  55. connected to a PCI bus.
  56. config USB_DWC2_DEBUG
  57. bool "Enable Debugging Messages"
  58. help
  59. Say Y here to enable debugging messages in the DWC2 Driver.
  60. config USB_DWC2_VERBOSE
  61. bool "Enable Verbose Debugging Messages"
  62. depends on USB_DWC2_DEBUG
  63. help
  64. Say Y here to enable verbose debugging messages in the DWC2 Driver.
  65. WARNING: Enabling this will quickly fill your message log.
  66. If in doubt, say N.
  67. config USB_DWC2_TRACK_MISSED_SOFS
  68. bool "Enable Missed SOF Tracking"
  69. help
  70. Say Y here to enable logging of missed SOF events to the dmesg log.
  71. WARNING: This feature is still experimental.
  72. If in doubt, say N.
  73. config USB_DWC2_DEBUG_PERIODIC
  74. bool "Enable Debugging Messages For Periodic Transfers"
  75. depends on USB_DWC2_DEBUG || USB_DWC2_VERBOSE
  76. default y
  77. help
  78. Say N here to disable (verbose) debugging messages to be
  79. logged for periodic transfers. This allows better debugging of
  80. non-periodic transfers, but of course the debug logs will be
  81. incomplete. Note that this also disables some debug messages
  82. for which the transfer type cannot be deduced.
  83. endif