From: "Mario Limonciello (AMD) (kernel.org)" <superm1@kernel.org>
To: "Katiyar, Pooja" <pooja.katiyar@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: "open list:THUNDERBOLT DRIVER" <linux-usb@vger.kernel.org>,
linux-kernel@vger.kernel.org,
Andreas Noever <andreas.noever@gmail.com>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
Pooja Katiyar <pooja.katiyar@intel.com>,
Rene Sapiens <rene.sapiens@linux.intel.com>
Subject: Re: [PATCH v2 0/2] thunderbolt: Fix S4 resume incongruities
Date: Mon, 19 Jan 2026 13:59:21 -0600 [thread overview]
Message-ID: <6438b5a3-a0f4-4c7d-9f56-59cdf7f5148f@kernel.org> (raw)
In-Reply-To: <5834100b-788c-4520-9b70-f462f65149ca@linux.intel.com>
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,
next prev parent reply other threads:[~2026-01-19 19:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 5:37 Mario Limonciello (AMD)
2026-01-06 5:37 ` [PATCH v2 1/2] thunderbolt: Move nhi_reset before pmops declaration Mario Limonciello (AMD)
2026-01-06 5:37 ` [PATCH v2 2/2] thunderbolt: Reset NHI during S4 restore_noirq() callback Mario Limonciello (AMD)
2026-01-07 9:33 ` [PATCH v2 0/2] thunderbolt: Fix S4 resume incongruities Mika Westerberg
2026-01-07 20:50 ` Mario Limonciello
2026-01-08 11:42 ` Mika Westerberg
2026-01-08 19:18 ` Mario Limonciello
2026-01-09 7:23 ` Mika Westerberg
2026-01-09 15:38 ` Mario Limonciello
2026-01-10 0:42 ` Katiyar, Pooja
2026-01-13 18:44 ` Mario Limonciello (AMD) (kernel.org)
2026-01-17 16:57 ` Katiyar, Pooja
2026-01-19 19:59 ` Mario Limonciello (AMD) (kernel.org) [this message]
2026-01-19 22:13 ` Kenneth Crudup
2026-01-29 23:13 ` Katiyar, Pooja
2026-01-30 1:39 ` Kenneth Crudup
2026-01-30 1:42 ` Kenneth Crudup
2026-02-04 0:50 ` Katiyar, Pooja
2026-05-05 21:21 ` Mario Limonciello
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=6438b5a3-a0f4-4c7d-9f56-59cdf7f5148f@kernel.org \
--to=superm1@kernel.org \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=pooja.katiyar@intel.com \
--cc=pooja.katiyar@linux.intel.com \
--cc=rene.sapiens@linux.intel.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
all inboxes | Powered by JetHome®