From: Leo Li <firstname.lastname@example.org>
To: "email@example.com" <firstname.lastname@example.org>,
Cc: "email@example.com" <firstname.lastname@example.org>,
Subject: RE: bug: usb: gadget: FSL_UDC_CORE Corrupted request list leads to unrecoverable loop.
Date: Thu, 2 Dec 2021 20:35:40 +0000 [thread overview]
Message-ID: <AS8PR04MB894614C61E57A80EB4FF7C758F699@AS8PR04MB8946.eurprd04.prod.outlook.com> (raw)
> -----Original Message-----
> From: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
> Sent: Wednesday, December 1, 2021 8:19 AM
> To: email@example.com; Leo Li <firstname.lastname@example.org>;
> Eugene_Bordenkircher@selinc.com; email@example.com; linuxppc-
> Cc: firstname.lastname@example.org; email@example.com
> Subject: Re: bug: usb: gadget: FSL_UDC_CORE Corrupted request list leads to
> unrecoverable loop.
> On Tue, 2021-11-30 at 12:56 +0100, Joakim Tjernlund wrote:
> > On Mon, 2021-11-29 at 23:48 +0000, Eugene Bordenkircher wrote:
> > > Agreed,
> > >
> > > We are happy pick up the torch on this, but I'd like to try and hear from
> Joakim first before we do. The patch set is his, so I'd like to give him the
> opportunity. I think he's the only one that can add a truly proper description
> as well because he mentioned that this includes a "few more fixes" than just
> the one we ran into. I'd rather hear from him than try to reverse engineer
> what was being addressed.
> > >
> > > Joakim, if you are still watching the thread, would you like to take a stab
> at it? If I don't hear from you in a couple days, we'll pick up the torch and do
> what we can.
> > >
> > I am far away from this now and still on 4.19. I don't mind if you tweak
> tweak the patches for better "upstreamability"
> Even better would be to migrate to the chipidea driver, I am told just a few
> tweaks are needed but this is probably something NXP should do as they
> have access to other SOC's using chipidea.
I agree with this direction but the problem was with bandwidth. As this controller was only used on legacy platforms, it is harder to justify new effort on it now.
next prev parent reply other threads:[~2021-12-02 20:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 17:14 bug: usb: gadget: FSL_UDC_CORE Corrupted request list leads to unrecoverable loop Eugene Bordenkircher
2021-10-29 17:24 ` Eugene Bordenkircher
2021-10-29 23:14 ` Li Yang
2021-10-30 14:20 ` Joakim Tjernlund
2021-11-02 21:15 ` Joakim Tjernlund
2021-11-15 8:36 ` Thorsten Leemhuis
2021-11-16 19:11 ` Eugene Bordenkircher
2021-11-25 13:59 ` Thorsten Leemhuis
2021-11-29 17:24 ` Eugene Bordenkircher
2021-11-29 23:37 ` Leo Li
2021-11-29 23:48 ` Eugene Bordenkircher
2021-11-30 11:56 ` Joakim Tjernlund
2021-12-01 14:19 ` Joakim Tjernlund
2021-12-02 20:35 ` Leo Li [this message]
2021-12-02 22:45 ` Joakim Tjernlund
2021-12-04 0:40 ` Leo Li
2022-01-20 12:54 ` Thorsten Leemhuis
2022-02-18 7:11 ` Thorsten Leemhuis
2022-02-18 10:21 ` Joakim Tjernlund
2022-02-18 10:39 ` gregkh
2022-02-18 11:17 ` Joakim Tjernlund
2022-02-18 11:48 ` gregkh
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).