From: Francesco Dolcini <francesco@dolcini.it>
To: linux-usb@vger.kernel.org, Xu Yang <xu.yang_2@nxp.com>,
Peter Chen <peter.chen@kernel.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, ritesh.kumar@toradex.com
Subject: USB EHCI chipidea regression on NXP i.MX7
Date: Wed, 8 Jan 2025 10:31:01 +0100 [thread overview]
Message-ID: <20250108093101.GA22448@francesco-nb> (raw)
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
next reply other threads:[~2025-01-08 9:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 9:31 Francesco Dolcini [this message]
2025-01-09 7:35 ` USB EHCI chipidea regression on NXP i.MX7 Xu Yang
2025-01-09 9:20 ` Francesco Dolcini
2025-01-10 6:51 ` Xu Yang
2025-01-10 8:16 ` Francesco Dolcini
2025-02-03 11:47 ` Stefan Eichenberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250108093101.GA22448@francesco-nb \
--to=francesco@dolcini.it \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@kernel.org \
--cc=ritesh.kumar@toradex.com \
--cc=stern@rowland.harvard.edu \
--cc=xu.yang_2@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.