From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: andreas.noever@gmail.com, michael.jamet@intel.com,
YehezkelShB@gmail.com, sanju.mehta@amd.com,
mario.limonciello@amd.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] thunderbolt: Resume PCIe bridges after switch is found on AMD USB4 controller
Date: Tue, 6 Sep 2022 18:22:27 +0300 [thread overview]
Message-ID: <Yxdls5XlZ0EBGfON@black.fi.intel.com> (raw)
In-Reply-To: <YxdgZavuLU78lqIL@black.fi.intel.com>
On Tue, Sep 06, 2022 at 05:59:49PM +0300, Mika Westerberg wrote:
> This reminded me that in Intel hardware there is an ACPI power resource that is
> shared between related devices. IIRC there is _PR0() method under the root
> port, xHCI and the TBT NHI that returns the same power resource. Now, when the
> power resource is turned on for any of the devices the kernel wakes up the rest
> too to make sure they get properly re-initialized if they went into
> D0unitialized or something like that. The commit that added this is
> 4533771c1e53 ("ACPI / PM: Introduce concept of a _PR0 dependent device").
Probably has nothing to do with this actually.
next prev parent reply other threads:[~2022-09-06 16:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 6:56 [PATCH] thunderbolt: Resume PCIe bridges after switch is found on AMD USB4 controller Kai-Heng Feng
2022-09-05 7:07 ` Mika Westerberg
2022-09-05 7:26 ` Kai-Heng Feng
2022-09-05 7:50 ` Mika Westerberg
2022-09-05 13:18 ` Mika Westerberg
2022-09-05 15:24 ` Kai-Heng Feng
2022-09-05 15:36 ` Mika Westerberg
2022-09-05 15:21 ` Kai-Heng Feng
2022-09-05 15:34 ` Mika Westerberg
2022-09-06 12:57 ` Kai-Heng Feng
2022-09-06 13:37 ` Mika Westerberg
2022-09-06 14:29 ` Kai-Heng Feng
2022-09-06 14:59 ` Mika Westerberg
2022-09-06 15:22 ` Mika Westerberg [this message]
2022-09-05 7:29 ` Greg KH
2022-09-07 16:30 ` Limonciello, Mario
2022-09-08 14:02 ` Kai-Heng Feng
2022-09-08 15:22 ` Limonciello, Mario
2022-09-12 7:35 ` Kai-Heng Feng
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=Yxdls5XlZ0EBGfON@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=michael.jamet@intel.com \
--cc=sanju.mehta@amd.com \
/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.