linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 216822] Thunderbolt USB Controller (Maple Ridge) and its upstream pcie port fail to runtime resume
Date: Thu, 22 Dec 2022 08:13:09 +0000	[thread overview]
Message-ID: <bug-216822-208809-QDjrBx1v4E@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216822-208809@https.bugzilla.kernel.org/>

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

--- Comment #4 from Max Lee (max.lee@canonical.com) ---
On this platforms, OEM didn't design RTD3 on Maple Ridge.
Since the MR AIC is to share with other desktop projects, and the NVM was set
to Native + RTD3 enabled.
This cause the driver to get the RTD3 enabled from NVM. and set Linux TBT
controller in D3 state then PME doesn't toggled by device hot plug.
Current BIOS sent _S0W to TBT RP and the NVM native +RTD3 doesn't change to
native only. Is this a correct setting on the NVM to support non-RTD3 platform?
should BIOS sent command to modify NVM offset to disable RTD3?

-- 
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:[~2022-12-22  8:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19  3:39 [Bug 216822] New: Thunderbolt USB Controller (Maple Ridge) and its upstream pcie port fail to runtime resume bugzilla-daemon
2022-12-19  3:40 ` [Bug 216822] " bugzilla-daemon
2022-12-19  3:43 ` bugzilla-daemon
2022-12-22  3:50 ` bugzilla-daemon
2022-12-22  8:13 ` bugzilla-daemon [this message]
2022-12-22 14:22 ` 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-216822-208809-QDjrBx1v4E@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).