public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: linux-usb@vger.kernel.org, stern@rowland.harvard.edu,
	oneukum@suse.com, konrad.dybcio@oss.qualcomm.com,
	broonie@kernel.org, stable@kernel.org
Subject: Re: [RFT PATCH v3 1/1] usb: hub: Fix flushing of delayed work used for post resume purposes
Date: Mon, 30 Jun 2025 13:19:18 +0200	[thread overview]
Message-ID: <2025063001-angled-caretaker-4494@gregkh> (raw)
In-Reply-To: <cea37477-319a-4090-b878-7bcbf348b6d8@linux.intel.com>

On Mon, Jun 30, 2025 at 01:07:29PM +0300, Mathias Nyman wrote:
> On 28.6.2025 17.46, Greg KH wrote:
> > On Fri, Jun 27, 2025 at 07:43:48PM +0300, Mathias Nyman wrote:
> > > Delayed work that prevents USB3 hubs from runtime-suspending too early
> > > needed to be flushed in hub_quiesce() to resolve issues detected on
> > > QC SC8280XP CRD board during suspend resume testing.
> > > 
> > > This flushing did however trigger new issues on Raspberry Pi 3B+, which
> > > doesn't have USB3 ports, and doesn't queue any post resume delayed work.
> > > 
> > > The flushed 'hub->init_work' item is used for several purposes, and
> > > is originally initialized with a 'NULL' work function. The work function
> > > is also changed on the fly, which may contribute to the issue.
> > > 
> > > Solve this by creating a dedicated delayed work item for post resume work,
> > > and flush that delayed work in hub_quiesce()
> > > 
> > > Cc: stable@kernel.org
> > > Fixes: a49e1e2e785f ("usb: hub: Fix flushing and scheduling of delayed work that tunes runtime pm")
> > > Reported-by: Mark Brown <broonie@kernel.org>
> > > Closes: https://lore.kernel.org/linux-usb/aF5rNp1l0LWITnEB@finisterre.sirena.org.uk
> > > Signed-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>
> > > ---
> > > v3:
> > >   - Rebase on top of a49e1e2e785f ("usb: hub: Fix flushing and scheduling of delayed work that tunes runtime pm")
> > >   - Rewrite commit message
> > > 
> > > v2:
> > >   - Add and use dedicated delayed work struct for post resume work
> > >   - Add commit message section about dedicated work
> > 
> > This seems to work, want me to take this, or are you going to submit
> > another one?  I'll hold off on sending the pull request to Linus for
> > -rc4 because of this.
> > 
> > thanks,
> > 
> > greg k-h
> 
> Sorry about the response delay, was offline during weekend

As one should be!  :)

> I'll do some quick additional smoketests, suspending and disconnecting runtime suspended
> chained USB3 hubs. Shouldn't take more than a couple of hours

Ok, no rush, thanks for letting me know.

greg k-h

  reply	other threads:[~2025-06-30 11:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-27 16:43 [RFT PATCH v3 0/1] Fix "detection of high tier USB3 devices" patch in usb-linus Mathias Nyman
2025-06-27 16:43 ` [RFT PATCH v3 1/1] usb: hub: Fix flushing of delayed work used for post resume purposes Mathias Nyman
2025-06-27 21:42   ` Mark Brown
2025-06-27 22:40   ` Konrad Dybcio
2025-06-28 14:46   ` Greg KH
2025-06-30 10:07     ` Mathias Nyman
2025-06-30 11:19       ` Greg KH [this message]
2025-06-30 13:15         ` Mathias Nyman
2025-06-30 13:36           ` Greg KH

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=2025063001-angled-caretaker-4494@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=broonie@kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=oneukum@suse.com \
    --cc=stable@kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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