public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220904] [BUG] ucsi_acpi: USB 3.0 SuperSpeed not negotiated on USB-C hot-plug
Date: Tue, 20 Jan 2026 15:54:18 +0000	[thread overview]
Message-ID: <bug-220904-208809-hR3JZrlHgk@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220904-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=220904

--- Comment #11 from Mathias Nyman (mathias.nyman@linux.intel.com) ---
The usb device at 2-3 is set to U3 suspended state before the xhci host at
0000:00:0d.0 suspends to D3cold. 

xHCI host controller is then reset and reinitialized during resume.
This should only be done during restore phase (resume from s4 hibernate) or if
there an error in resume. Not in normal s2idle resume. 
Logs don't show any error during resume.

This host controller reset may trigger a warm port reset on USB3 ports.
The device at 2-3 is probably unaware of the host controller reset, and
remains in suspended u3 state until a warm reset is suddenly issued.

Right after we get the host re-initialuzed and up and running we read the port
status registers, and see that port 2-3 is stuck with "reset asserted" bit set,
and remain this way.

First we should figure out why host is reset during resumed for a normal s2idle
suspend/resume.
If the host reset is needed theb we might need to work around this and try
disabling/power off ports before resetting the host in resume.

would it be possible for you to try some testpatches on this setup if I write
them?

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2026-01-20 15:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-24 12:00 [Bug 220904] New: [BUG] ucsi_acpi: USB 3.0 SuperSpeed not negotiated on USB-C hot-plug bugzilla-daemon
2025-12-30 11:54 ` [Bug 220904] " bugzilla-daemon
2025-12-30 18:42 ` bugzilla-daemon
2025-12-31  5:59 ` bugzilla-daemon
2025-12-31  8:54 ` bugzilla-daemon
2025-12-31  9:24 ` bugzilla-daemon
2025-12-31 10:31 ` bugzilla-daemon
2025-12-31 13:31 ` bugzilla-daemon
2025-12-31 14:46 ` bugzilla-daemon
2026-01-05 15:28 ` bugzilla-daemon
2026-01-09 12:19 ` bugzilla-daemon
2026-01-20 15:54 ` bugzilla-daemon [this message]
2026-01-20 18:56 ` bugzilla-daemon
2026-02-13 15:01 ` bugzilla-daemon
2026-02-17 11:44 ` bugzilla-daemon
2026-02-18 16:51 ` bugzilla-daemon

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=bug-220904-208809-hR3JZrlHgk@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@vger.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