mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Kuen-Han Tsai <khtsai@google.com>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	stable <stable@kernel.org>
Subject: Re: [PATCH] usb: dwc3: Ignore late xferNotReady event to prevent halt timeout
Date: Thu, 7 Aug 2025 00:55:59 +0000	[thread overview]
Message-ID: <20250807005558.72hmwuwsjknejhsb@synopsys.com> (raw)
In-Reply-To: <CAKzKK0r7StRcA=dEZSzK2=yN-HdFyKDsDV=+yzTdE0_UJboORw@mail.gmail.com>

On Wed, Aug 06, 2025, Kuen-Han Tsai wrote:
> Hi Thinh,
> 
> Thank you for your review.
> 
> On Wed, Aug 6, 2025 at 7:28 AM Thinh Nguyen <Thinh.Nguyen@synopsys.com> wrote:
> >
> > On Tue, Aug 05, 2025, Kuen-Han Tsai wrote:
> > > During a device-initiated disconnect, the End Transfer command resets
> > > the event filter, allowing a new xferNotReady event to be generated
> > > before the controller is fully halted. Processing this late event
> > > incorrectly triggers a Start Transfer, which prevents the controller
> > > from halting and results in a DSTS.DEVCTLHLT bit polling timeout.
> > >
> > > Ignore the late xferNotReady event if the controller is already in a
> > > disconnected state.
> > >
> > > Fixes: 8f608e8ab628 ("usb: dwc3: gadget: remove unnecessary 'dwc' parameter")
> >
> > The Fixes should target since the beginning of the driver:
> > 72246da40f37 ("usb: Introduce DesignWare USB3 DRD Driver")
> 
> Commit 72246da40f37 doesn't have the dwc->connected member. Should we
> change the Fixes tag to f09ddcfcb8c5 ("usb: dwc3: gadget: Prevent EP
> queuing while stopping transfers")?
> That's the commit where the "dwc->connected = false" logic was moved before
> stopping active transfers within the pullup function.
> 

The Fixes tag should point to where the issue first introduced that this
patch fixes, not necessarily where it can be backported to. You can give
hints to how far back you want the fix to be backported, but may not
have to.

Thanks,
Thinh

      reply	other threads:[~2025-08-07  0:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-05  6:34 Kuen-Han Tsai
2025-08-05 23:28 ` Thinh Nguyen
2025-08-06 10:17   ` Kuen-Han Tsai
2025-08-07  0:55     ` Thinh Nguyen [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=20250807005558.72hmwuwsjknejhsb@synopsys.com \
    --to=thinh.nguyen@synopsys.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=khtsai@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stable@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®