From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 218987] USB devices are not detected after Save/Restore error on Intel xHC
Date: Wed, 26 Jun 2024 10:12:51 +0000 [thread overview]
Message-ID: <bug-218987-208809-hJtjZifNjX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218987-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218987
--- Comment #4 from Remi Pommarel (repk@triplefau.lt) ---
Thanks for looking into this issue.
(In reply to Mathias Nyman from comment #3)
...
> Issue 2 is probably due to PORTSC not immediately showing connected devices
> after host is restarted. This is especially true for USB3 devices where
> device only shows up in PORTSC after successful link training.
Weirdly enough this issue seems to happen only on the USB 2.0 root hub part of
the port not the USB 3.0 one. I first tried to add delay to see if my port
events showed but no luck on that. Anyway that does not matter much.
> How about a solution that is similar to your patch but doesn't touch
> pending_portevent. Instead we always resume roothubs in case xHC was reset
> during resume.
>
> Does the oneliner below work for you?
Yes it works. While I did initially try that, I switched to pending_portevent
patch version to avoid unneeded xhci_pending_portevent() and msleep(120) calls.
But both are very fine with me.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-06-26 10:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 13:06 [Bug 218987] New: USB devices are not detected after Save/Restore error on Intel xHC bugzilla-daemon
2024-06-25 13:07 ` [Bug 218987] " bugzilla-daemon
2024-06-25 13:08 ` bugzilla-daemon
2024-06-26 9:10 ` bugzilla-daemon
2024-06-26 10:12 ` bugzilla-daemon [this message]
2024-06-27 13:04 ` bugzilla-daemon
2024-06-27 13:10 ` bugzilla-daemon
2024-06-27 14:03 ` bugzilla-daemon
2024-06-27 14:56 ` bugzilla-daemon
2024-06-27 15:36 ` bugzilla-daemon
2024-06-28 8:51 ` bugzilla-daemon
2024-06-28 17:00 ` 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-218987-208809-hJtjZifNjX@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;
as well as URLs for NNTP newsgroup(s).