All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 28 Jun 2024 17:00:32 +0000	[thread overview]
Message-ID: <bug-218987-208809-sy3Qy5vxVc@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 #11 from Remi Pommarel (repk@triplefau.lt) ---
(In reply to Mathias Nyman from comment #10)
> About SRE, 
> 

...

> Not sure if it makes a difference but could be worth testing if skipping the
> soft reset impacts SRE.
> 
> Can be done by setting quirk:
> xhci->quirks |= XHCI_NO_SOFT_RETRY

Thanks.

Unfortunately this does not help.

What is funny is that it is related to if the HDMI is plugged or not. So I
think it is related to DP alt mode of type C. I don't know if xHC needs to even
know about alternate mode, it does not look like so to 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.

      parent reply	other threads:[~2024-06-28 17:00 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
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 [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=bug-218987-208809-sy3Qy5vxVc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.