Hi Peter, On 2018-06-01 03:30, Peter Chen wrote:
After bisecting usb-next starting from tag 'v4.16' to current head I found that the commit: commit 4e88d4c083016454f179686529ae65d70b933b58 Author: Martin Blumenstingl <martin.blumenstingl@xxxxxxxxxxxxxx> Date: Sat Mar 3 22:43:03 2018 +0100 usb: add a flag to skip PHY initialization to struct usb_hcd causes a regression for me on my SolidRun Hummingboard (NXP i.MX6 DL SoC with chipidea controller). Example: -- Cold boot of system. -- Plug in USB memory stick --> Attached OK. -- Mount disk --> OK, "ls" works -- Unmount disk --> OK -- Unplug USB stick --> Nothing happens. "udevadm monitor" see no events. -- Plug in/unplug stick again --> Still nothing. -- Plug in stick and try mounting --> Somehow causes both detach and attach of the stick (mounting fails but mounting again now works). -- All tested USB devices are working in a similar way. I.e first attach after boot works and then trouble starts. -- Tested using default device tree from kernel tree (arch/arm/boot/dts/imx6dl-hummingboard.dts). Please ask if you think I can help in any way to track down the issue.Hi Mats, I have tested the latest usb-next tree, the hot plug works at my imx6sx-sdb board. Would you please check the value of hcd->skip_phy_initialization at the end of function host_start?
hcd->skip_phy_initialization=1 BR // Mats -- 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
