Linux USB
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Basavaraj Natikar <bnatikar@amd.com>
Cc: Mario Limonciello <mario.limonciello@amd.com>,
	Basavaraj Natikar <Basavaraj.Natikar@amd.com>,
	andreas.noever@gmail.com, westeri@kernel.org,
	YehezkelShB@gmail.com, linux-usb@vger.kernel.org,
	Sanath S <Sanath.S@amd.com>
Subject: Re: [PATCH] thunderbolt: Assert downstream port reset on shutdown
Date: Tue, 9 Jun 2026 12:05:28 +0200	[thread overview]
Message-ID: <20260609100528.GM2990@black.igk.intel.com> (raw)
In-Reply-To: <0e482be6-3b60-4322-8554-53c48a2aa629@amd.com>

On Tue, Jun 09, 2026 at 01:25:55AM -0500, Basavaraj Natikar wrote:
> 
> On 6/8/2026 10:25 AM, Mario Limonciello wrote:
> > > > 
> > > > I guess I see two approaches.
> > > > 
> > > > 1) Move to shutdown only (your suggestion).
> > > > 
> > > > Corner case of user who unloads before shutdown means they could
> > > > be exposed
> > > > to this.
> > > > 
> > > > 2) Link the DPR behavior to host_reset module behavior.
> > > > 
> > > > IE If a user set host_reset=0 avoid host reset on module load
> > > > and avoid DPR
> > > > on module unload/shutdown.
> > > > 
> > > > If user kept host_reset=1 then do DPR on unload.
> > > > 
> > > > Always do on shutdown (regardless of host_reset value).
> > > > 
> > > > What do you think of #2?
> > > 
> > > That sounds better. Also we could restrict this more for links that
> > > are TB3
> > > e.g no need to do for USB4, assuming that is simple to do.
> > 
> > OK thanks.  Basavaraj, thoughts?
> > 
> > The way that this was found was by looking at the traces of what Windows
> > and Linux were doing differently at shutdown.
> > 
> > Maybe before we make a decision to tie it only to TBT3 we should double
> > check if Windows was also doing the DPR for USB4 too.
> 
> So the traces confirm Windows only asserts DPR for TB3 and not for USB4
> docks, which matches what Mika suggested. For v2 I will restrict the
> reset to legacy TB3 devices (skip USB4 routers) and fold in the
> host_reset changes (the second approach).

Sounds good to me.

      reply	other threads:[~2026-06-09 10:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-03 18:01 [PATCH] thunderbolt: Assert downstream port reset on shutdown Basavaraj Natikar
2026-06-03 19:02 ` Mario Limonciello
2026-06-04  5:03 ` Mika Westerberg
2026-06-05 16:27   ` Basavaraj Natikar
2026-06-08  6:40     ` Mika Westerberg
2026-06-08 15:13       ` Mario Limonciello
2026-06-08 15:22         ` Mika Westerberg
2026-06-08 15:25           ` Mario Limonciello
2026-06-09  6:25             ` Basavaraj Natikar
2026-06-09 10:05               ` Mika Westerberg [this message]

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=20260609100528.GM2990@black.igk.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=Basavaraj.Natikar@amd.com \
    --cc=Sanath.S@amd.com \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=bnatikar@amd.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=mario.limonciello@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox