NOP USB transceiver should be selected when PCIe-based platforms are enabled. Because it need initialize usb phy platform device for binding related phy driver when pci gule are probing. If NOP USB transceiver is disabled, during dwc3-pci probing process, the driver can not find transceivers of both USB2 and USB3 PHY with below message. [ 337.517644] Registering platform device 'nop_usb_xceiv.0'. Parent at platform [ 337.524794] device: 'nop_usb_xceiv.0': device_add [ 337.529529] bus: 'platform': add device nop_usb_xceiv.0 [ 337.534788] PM: Adding info for platform:nop_usb_xceiv.0 [ 337.540161] Registering platform device 'nop_usb_xceiv.1'. Parent at platform [ 337.547311] device: 'nop_usb_xceiv.1': device_add [ 337.552034] bus: 'platform': add device nop_usb_xceiv.1 [ 337.557291] PM: Adding info for platform:nop_usb_xceiv.1 [ 337.562644] Registering platform device 'dwc3.0.auto'. Parent at 0000:05:00.0 [ 337.569794] device: 'dwc3.0.auto': device_add [ 337.574160] bus: 'platform': add device dwc3.0.auto [ 337.579068] PM: Adding info for platform:dwc3.0.auto [ 337.584058] bus: 'platform': driver_probe_device: matched device dwc3.0.auto with driver dwc3 [ 337.592585] bus: 'platform': really_probe: probing driver dwc3 with device dwc3.0.auto [ 337.600570] unable to find transceiver of type USB2 PHY [ 337.605793] unable to find transceiver of type USB3 PHY Cc: Paul Zimmerman <Paul.Zimmerman@xxxxxxxxxxxx> Signed-off-by: Huang Rui <ray.huang@xxxxxxx> --- drivers/usb/dwc3/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/usb/dwc3/Kconfig b/drivers/usb/dwc3/Kconfig index 3e225d5..49e6215 100644 --- a/drivers/usb/dwc3/Kconfig +++ b/drivers/usb/dwc3/Kconfig @@ -62,6 +62,7 @@ config USB_DWC3_EXYNOS config USB_DWC3_PCI tristate "PCIe-based Platforms" depends on PCI + select NOP_USB_XCEIV default USB_DWC3 help If you're using the DesignWare Core IP with a PCIe, please say -- 1.7.10.4 -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
