From: Stefan Eichenberger <eichest@gmail.com>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: Xu Yang <xu.yang_2@nxp.com>,
ritesh.kumar@toradex.com, linux-usb@vger.kernel.org,
Peter Chen <peter.chen@kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: USB EHCI chipidea regression on NXP i.MX7
Date: Mon, 3 Feb 2025 12:47:28 +0100 [thread overview]
Message-ID: <Z6Cs0PeC2O6enO7R@eichest-laptop> (raw)
In-Reply-To: <Z4DXUuHwTsbiir5I@gaggiata.pivistrello.it>
Hi everyone,
On Fri, Jan 10, 2025 at 09:16:18AM +0100, Francesco Dolcini wrote:
> Hello,
>
> On Fri, Jan 10, 2025 at 02:51:01PM +0800, Xu Yang wrote:
> > On Thu, Jan 09, 2025 at 10:20:20AM +0100, Francesco Dolcini wrote:
> > > On Thu, Jan 09, 2025 at 03:35:00PM +0800, Xu Yang wrote:
> > > > > 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.
> > > >
> > > > Does this happen 100%?
> > > > I tried many time on i.MX7ULP-EVK board, but I can't reproduce this issue.
> > >
> > > The issue happens with i.MX7D.
> >
> > Then I think this issue is not related to that commit.
> > I also tried on i.MX7D, but I still can't reproduce it.
> >
> > Please firstly confirm few questions in last mail.
>
> Thanks Xu Yang for trying this out.
>
> Ritesh: can you help here?
We did some more tests on our (Toradex) side and the issue is not
related to the mentioned commit. We sent a first patch which tries to
address the issue:
https://lore.kernel.org/all/20250203105840.17539-1-eichest@gmail.com/
Sorry for the false alert.
Regards,
Stefan
prev parent reply other threads:[~2025-02-03 11:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 9:31 USB EHCI chipidea regression on NXP i.MX7 Francesco Dolcini
2025-01-09 7:35 ` 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 [this message]
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=Z6Cs0PeC2O6enO7R@eichest-laptop \
--to=eichest@gmail.com \
--cc=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.