From: Greg KH <greg@kroah.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: Reset thunderbolt topologies at bootup
Date: Tue, 23 Apr 2024 12:50:00 -0700 [thread overview]
Message-ID: <2024042347-humongous-unifier-5375@gregkh> (raw)
In-Reply-To: <a06d9047-114f-4e63-b3b4-efcd83ca6d1e@amd.com>
On Tue, Apr 23, 2024 at 01:54:27PM -0500, Mario Limonciello wrote:
> Hi,
>
> We've got a collection of bug reports about how if a Thunderbolt device is
> connected at bootup it doesn't behave the same as if it were hotplugged by
> the user after bootup. Issues range from non-functional devices or display
> devices working at lower performance.
>
> All of the issues stem from a pre-OS firmware initializing the USB4
> controller and the OS re-using those tunnels. This has been fixed in
> 6.9-rc1 by resetting the controller to a fresh state and discarding whatever
> firmware has done. I'd like to bring it back to 6.6.y LTS and 6.8.y stable.
>
> 01da6b99d49f6 thunderbolt: Introduce tb_port_reset()
> b35c1d7b11da8 thunderbolt: Introduce tb_path_deactivate_hop()
> ec8162b3f0683 thunderbolt: Make tb_switch_reset() support Thunderbolt 2, 3
> and USB4 routers
> 9a54c5f3dbde thunderbolt: Reset topology created by the boot firmware
The last one seems wrong, it's really
59a54c5f3dbde00b8ad30aef27fe35b1fe07bf5c, right?
thanks,
greg k-h
next prev parent reply other threads:[~2024-04-23 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 18:54 Reset thunderbolt topologies at bootup Mario Limonciello
2024-04-23 19:50 ` Greg KH [this message]
2024-04-23 19:51 ` Mario Limonciello
2024-04-23 19:52 ` Greg KH
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=2024042347-humongous-unifier-5375@gregkh \
--to=greg@kroah.com \
--cc=mario.limonciello@amd.com \
--cc=stable@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