diff options
| author | Mathias Nyman <[email protected]> | 2025-06-26 13:01:02 +0000 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2025-06-26 14:57:39 +0000 |
| commit | a49e1e2e785fb3621f2d748581881b23a364998a (patch) | |
| tree | af51c4e4285d1669ebe9f9f7edcdd9ed24215f08 /tools/perf/scripts/python/syscall-counts-by-pid.py | |
| parent | usb: typec: displayport: Fix potential deadlock (diff) | |
| download | kernel-a49e1e2e785fb3621f2d748581881b23a364998a.tar.gz kernel-a49e1e2e785fb3621f2d748581881b23a364998a.zip | |
usb: hub: Fix flushing and scheduling of delayed work that tunes runtime pm
Delayed work to prevent USB3 hubs from runtime-suspending immediately
after resume was added in commit 8f5b7e2bec1c ("usb: hub: fix detection
of high tier USB3 devices behind suspended hubs").
This delayed work needs be flushed if system suspends, or hub needs to
be quiesced for other reasons right after resume. Not flushing it
triggered issues on QC SC8280XP CRD board during suspend/resume testing.
Fix it by flushing the delayed resume work in hub_quiesce()
The delayed work item that allow hub runtime suspend is also scheduled
just before calling autopm get. Alan pointed out there is a small risk
that work is run before autopm get, which would call autopm put before
get, and mess up the runtime pm usage order.
Swap the order of work sheduling and calling autopm get to solve this.
Cc: stable <[email protected]>
Fixes: 8f5b7e2bec1c ("usb: hub: fix detection of high tier USB3 devices behind suspended hubs")
Reported-by: Konrad Dybcio <[email protected]>
Closes: https://lore.kernel.org/linux-usb/[email protected]
Reported-by: Alan Stern <[email protected]>
Closes: https://lore.kernel.org/linux-usb/[email protected]
Signed-off-by: Mathias Nyman <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts-by-pid.py')
0 files changed, 0 insertions, 0 deletions