Kconfig 3.1 KB

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