[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6438b5a3-a0f4-4c7d-9f56-59cdf7f5148f@kernel.org>
Date: Mon, 19 Jan 2026 13:59:21 -0600
From: "Mario Limonciello (AMD) (kernel.org)" <superm1@...nel.org>
To: "Katiyar, Pooja" <pooja.katiyar@...ux.intel.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc: "open list:THUNDERBOLT DRIVER" <linux-usb@...r.kernel.org>,
linux-kernel@...r.kernel.org, Andreas Noever <andreas.noever@...il.com>,
Yehezkel Bernat <YehezkelShB@...il.com>,
Pooja Katiyar <pooja.katiyar@...el.com>,
Rene Sapiens <rene.sapiens@...ux.intel.com>
Subject: Re: [PATCH v2 0/2] thunderbolt: Fix S4 resume incongruities
On 1/17/2026 10:57 AM, Katiyar, Pooja wrote:
>> I have confirmation the hack patch does help the issue for us too.
>>
>> If your patch doesn't work another logical solution could be to destroy
>> all the tunnels as part of the PM freeze callback (not just the DP
>> resources). Maybe even unify the suspend and freeze codepaths for more
>> opportunities for code reuse?
>>
>
> Thanks for confirming the hack patch helps!
>
> We are actually working on a solution that releases the DP resources and
> suspends the switch as part of the freeze sequence. This way the hibernation
> image that is stored doesn't contain any active tunnels, and during resume
> we get a DP hotplug notification for a new tunnel, similar to S5. So far
> this patch is working fine but is under review.
>
Thanks. If you want early testing from us too before you're ready to
post publicly feel free to ping it offline to me too.
Thanks,
Powered by blists - more mailing lists