[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YysxhSh73nwMC1Kb@kroah.com>
Date: Wed, 21 Sep 2022 17:45:09 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Mario Limonciello <mario.limonciello@....com>
Cc: Mika Westerberg <mika.westerberg@...ux.intel.com>,
linux-usb@...r.kernel.org,
Andreas Noever <andreas.noever@...il.com>,
Michael Jamet <michael.jamet@...el.com>,
Yehezkel Bernat <YehezkelShB@...il.com>, sanju.mehta@....com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] Fix some hotplug event issues
On Wed, Sep 21, 2022 at 09:54:31AM -0500, Mario Limonciello wrote:
> On AMD Pink Sardine it's been observed that if another CM has run before
> the Linux CM that some registers may not match expectations which leads
> to a non-functional hotplug for PCIe devices.
>
> Explicitly set these registers that have been observed to cause problems
> with hotplug to the defaults of the USB4 spec.
>
> Mario Limonciello (2):
> thunderbolt: Explicitly reset plug events delay back to USB4 spec
> value
> thunderbolt: Explicitly enable lane adapter hotplug events at startup
>
> drivers/thunderbolt/switch.c | 5 +++++
> drivers/thunderbolt/tb.h | 1 +
> drivers/thunderbolt/tb_regs.h | 1 +
> drivers/thunderbolt/usb4.c | 19 +++++++++++++++++++
> 4 files changed, 26 insertions(+)
Any specific reason these were not tagged for stable backports?
thanks,
greg k-h
Powered by blists - more mailing lists