All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <superm1@kernel.org>
To: Kenneth Crudup <kenny@panix.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: mario.limonciello@amd.com, andreas.noever@gmail.com,
	westeri@kernel.org, YehezkelShB@gmail.com, Sanath.S@amd.com,
	linux-usb@vger.kernel.org
Subject: Re: [PATCH] thunderbolt: Reset NHI during S4 restore_noirq() callback
Date: Tue, 4 Nov 2025 14:31:09 -0600	[thread overview]
Message-ID: <848584ae-897a-4b82-8532-059c148db9ed@kernel.org> (raw)
In-Reply-To: <00b5f5a6-27eb-4949-88ab-eb78badedc58@panix.com>

On 11/4/25 2:22 PM, Kenneth Crudup wrote:
> 
> On 11/4/25 11:12, Mario Limonciello wrote:
> 
>> V2 caused nonsensical testing failures that I haven't figured out yet 
>> so I didn't put it out on the list.
>> Try V1 and let me know how it goes!
> 
> Will do ... the transition from work to home (with totally different 
> setups) is where I usually see this issue come up, so I'll know more 
> tonight, but at least just a quick suspend-resume cycle RN hasn't blown 
> anything up, so that's promising :)
> 
> -Kenny
> 

Are you doing S4 at all?  Or only s2idle/s3?  The patch was specifically 
for resume from S4.

  reply	other threads:[~2025-11-04 20:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-23  5:03 [PATCH] thunderbolt: Reset NHI during S4 restore_noirq() callback Mario Limonciello (AMD)
2025-10-23  5:56 ` Mika Westerberg
2025-10-23 14:13   ` Mario Limonciello
2025-11-04 19:11     ` Kenneth Crudup
2025-11-04 19:12       ` Mario Limonciello
2025-11-04 20:22         ` Kenneth Crudup
2025-11-04 20:31           ` Mario Limonciello [this message]
2025-11-04 21:19             ` Kenneth Crudup
2025-11-04 21:21               ` Mario Limonciello
2025-11-05 19:06                 ` Kenneth Crudup
2025-11-05 19:16                   ` Mario Limonciello (AMD) (kernel.org)

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=848584ae-897a-4b82-8532-059c148db9ed@kernel.org \
    --to=superm1@kernel.org \
    --cc=Sanath.S@amd.com \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=kenny@panix.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=westeri@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.