Linux USB
 help / color / mirror / Atom feed
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: Mon, 5 Sep 2022 10:07:04 +0300	[thread overview]
Message-ID: <YxWgGKIAvsxwSz85@black.fi.intel.com> (raw)
In-Reply-To: <20220905065622.1573811-1-kai.heng.feng@canonical.com>

Hi,

On Mon, Sep 05, 2022 at 02:56:22PM +0800, Kai-Heng Feng wrote:
> AMD USB4 can not detect external PCIe devices like external NVMe when
> it's hotplugged, because card/link are not up:
> 
> pcieport 0000:00:04.1: pciehp: pciehp_check_link_active: lnk_status = 1101

I think the correct solution is then to block them from runtime
suspending entirely.

> Use `lspci` to resume pciehp bridges can find external devices.
> 
> A long delay before checking card/link presence doesn't help, either.
> The only way to make the hotplug work is to enable pciehp interrupt and
> check card presence after the TB switch is added.
> 
> Since the topology of USB4 and its PCIe bridges are siblings, hardcode
> the bridge ID so TBT driver can wake them up to check presence.

Let's not add PCI things into TBT driver unless absolutely necessary.

At least on Intel hardware the PCIe hotplug is signaled by SCI when the
root port is in D3, I wonder if AMD has something similar.

  reply	other threads:[~2022-09-05  7:08 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 [this message]
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
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=YxWgGKIAvsxwSz85@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox