Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Wed, 21 Sep 2022 17:45:09 +0200
From:   Greg KH <gregkh@linuxfoundation.org>
To:     Mario Limonciello <mario.limonciello@amd.com>
Cc:     Mika Westerberg <mika.westerberg@linux.intel.com>,
        linux-usb@vger.kernel.org,
        Andreas Noever <andreas.noever@gmail.com>,
        Michael Jamet <michael.jamet@intel.com>,
        Yehezkel Bernat <YehezkelShB@gmail.com>, sanju.mehta@amd.com,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Fix some hotplug event issues
Message-ID: <YysxhSh73nwMC1Kb@kroah.com>
References: <20220921145434.21659-1-mario.limonciello@amd.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20220921145434.21659-1-mario.limonciello@amd.com>
Precedence: bulk

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