From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Mohammad Rahimi <rahimi.mhmmd@gmail.com>
Cc: andreas.noever@gmail.com, michael.jamet@intel.com,
YehezkelShB@gmail.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] thunderbolt: Disable Gen 4 Recovery on Asymmetric Transitions
Date: Mon, 3 Feb 2025 14:39:44 +0200 [thread overview]
Message-ID: <20250203123944.GJ3713119@black.fi.intel.com> (raw)
In-Reply-To: <wxgsteiuto6qivnfttzuyw6jijs6ypcq4oyepqr6zbjgeez3ac@flvlpzswuyco>
Hi,
On Mon, Feb 03, 2025 at 12:25:21PM +0000, Mohammad Rahimi wrote:
> Hello.
>
> On Mon, Feb 03, 2025 at 10:42:24AM GMT, Mika Westerberg wrote:
> > Hi,
> >
> > On Fri, Jan 31, 2025 at 01:41:27AM +0000, Mohammad Rahimi wrote:
> > > Updates the Connection Manager to disable the Gen 4 Link Recovery
> > > flow before transitioning from a Symmetric Link to an Asymmetric
> > > Link, as specified in recent changes to the USB4 v2 specification.
> > >
> > > According to the "USB4 2.0 ENGINEERING CHANGE NOTICE FORM"
> > > published in September 2024, the rationale for this change is:
> > >
> > > "Since the default value of the Target Asymmetric Link might be
> > > different than Symmetric Link and Gen 4 Link Recovery flow checks
> > > this field to make sure it matched the actual Negotiated Link Width,
> > > we’re removing the condition for a Disconnect in the Gen 4 Link
> > > Recovery flow when Target Asymmetric Link doesn’t match the actual
> > > Link width and adding a Connection Manager note to Disable Gen 4 Link
> > > Recovery flow before doing Asymmetric Transitions."
> > >
> > > Signed-off-by: Mohammad Rahimi <rahimi.mhmmd@gmail.com>
> >
> > I did some minor modifications and applied to thunderbolt.git/next. Please
> > let me know if I missed something.
> >
>
> Looks great. Just one question:
>
> In tb_configure_asym(), if tb_switch_set_link_width() fails, we won’t restore
> the link recovery status. Is that okay?
Good question :) Looking at the ECR, does it actually say anywhere that the
CM should needs to re-enable it? I'm thinking that we could just disable it
and be done with it?
next prev parent reply other threads:[~2025-02-03 12:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 1:41 [PATCH v4 Cover Letter] thunderbolt: Disable Gen 4 Recovery on Asymmetric Transitions Mohammad Rahimi
2025-01-31 1:41 ` [PATCH v4] " Mohammad Rahimi
2025-02-03 8:42 ` Mika Westerberg
2025-02-03 12:25 ` Mohammad Rahimi
2025-02-03 12:39 ` Mika Westerberg [this message]
2025-02-03 12:43 ` Mohammad Rahimi
2025-02-03 12:59 ` Mika Westerberg
2025-02-04 11:16 ` Mika Westerberg
2025-02-04 11:39 ` Mika Westerberg
2025-02-04 2:35 ` Mohammad Rahimi
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=20250203123944.GJ3713119@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michael.jamet@intel.com \
--cc=rahimi.mhmmd@gmail.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 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.