Hello Xu Yang and all,
commit dda4b60ed70b ("usb: ehci: add workaround for chipidea PORTSC.PEC bug")
introduced a regression on NXP i.MX7 SoC.
If the USB port is connected to a USB HUB, and a device is connected at
boot time to such a hub, the following errors are printed and the USB
port is not functional.
[ 1.131847] usbhid: USB HID core driver
[ 9.471549] ci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 1
[ 9.516311] ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00
[ 9.516697] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06
[ 9.516728] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 9.527751] hub 1-0:1.0: USB hub found
[ 9.827109] usb 1-1: new high-speed USB device number 2 using ci_hdrc
[ 10.029600] usb 1-1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
[ 10.071198] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 10.111575] hub 1-1:1.0: USB hub found
[ 10.741225] usb 1-1: USB disconnect, device number 2
[ 10.789292] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ 10.843210] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ 11.361157] usb 1-1: new high-speed USB device number 5 using ci_hdrc
[ 11.891163] usb 1-1: new high-speed USB device number 6 using ci_hdrc
[ 12.231248] usb usb1-port1: unable to enumerate USB device
The issue was reproduced on a recent v6.6 kernel.
Ritesh, in Cc, did the bisect and debugged this issue, he might be able
to provide more details if needed.
- Any suggestion?
- Can you please specify with SoCs are affected by this frame babble bug?
- How can I reproduce this frame babble bug? Is there an easy way to test it?
Thanks,
Francesco
