Kconfig 2.7 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586
  1. config USB_DWC2
  2. bool "DesignWare USB2 DRD Core Support"
  3. depends on USB
  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 gadget mode, there will be a single
  13. module called dwc2_gadget.ko.
  14. NOTE: The s3c-hsotg driver is now renamed to dwc2_gadget. The
  15. host and gadget drivers are still currently separate drivers.
  16. There are plans to merge the dwc2_gadget driver with the dwc2
  17. host driver in the near future to create a dual-role driver.
  18. if USB_DWC2
  19. config USB_DWC2_HOST
  20. tristate "Host only mode"
  21. depends on USB
  22. help
  23. The Designware USB2.0 high-speed host controller
  24. integrated into many SoCs.
  25. config USB_DWC2_PLATFORM
  26. bool "DWC2 Platform"
  27. depends on USB_DWC2_HOST
  28. default USB_DWC2_HOST
  29. help
  30. The Designware USB2.0 platform interface module for
  31. controllers directly connected to the CPU. This is only
  32. used for host mode.
  33. config USB_DWC2_PCI
  34. bool "DWC2 PCI"
  35. depends on USB_DWC2_HOST && PCI
  36. default USB_DWC2_HOST
  37. help
  38. The Designware USB2.0 PCI interface module for controllers
  39. connected to a PCI bus. This is only used for host mode.
  40. comment "Gadget mode requires USB Gadget support to be enabled"
  41. config USB_DWC2_PERIPHERAL
  42. tristate "Gadget only mode"
  43. depends on USB_GADGET
  44. help
  45. The Designware USB2.0 high-speed gadget controller
  46. integrated into many SoCs.
  47. config USB_DWC2_DEBUG
  48. bool "Enable Debugging Messages"
  49. help
  50. Say Y here to enable debugging messages in the DWC2 Driver.
  51. config USB_DWC2_VERBOSE
  52. bool "Enable Verbose Debugging Messages"
  53. depends on USB_DWC2_DEBUG
  54. help
  55. Say Y here to enable verbose debugging messages in the DWC2 Driver.
  56. WARNING: Enabling this will quickly fill your message log.
  57. If in doubt, say N.
  58. config USB_DWC2_TRACK_MISSED_SOFS
  59. bool "Enable Missed SOF Tracking"
  60. help
  61. Say Y here to enable logging of missed SOF events to the dmesg log.
  62. WARNING: This feature is still experimental.
  63. If in doubt, say N.
  64. config USB_DWC2_DEBUG_PERIODIC
  65. bool "Enable Debugging Messages For Periodic Transfers"
  66. depends on USB_DWC2_DEBUG || USB_DWC2_VERBOSE
  67. default y
  68. help
  69. Say N here to disable (verbose) debugging messages to be
  70. logged for periodic transfers. This allows better debugging of
  71. non-periodic transfers, but of course the debug logs will be
  72. incomplete. Note that this also disables some debug messages
  73. for which the transfer type cannot be deduced.
  74. endif