From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Kurt Lieber <kurt@lieber.org>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"andreas.noever@gmail.com" <andreas.noever@gmail.com>,
"westeri@kernel.org" <westeri@kernel.org>,
"YehezkelShB@gmail.com" <YehezkelShB@gmail.com>
Subject: Re: [PATCH] thunderbolt: Disable CL states for the Anker Prime TB5 dock
Date: Thu, 24 Sep 2026 16:54:47 +0200 [thread overview]
Message-ID: <20260924145447.GR106095@black.igk.intel.com> (raw)
In-Reply-To: <SJ0PR15MB469651A447568D8E66757EB1A3812@SJ0PR15MB4696.namprd15.prod.outlook.com>
On Thu, Sep 24, 2026 at 01:33:01PM +0000, Kurt Lieber wrote:
> Hello -
>
> > Hmm, I missed that it's Barlow Ridge. That should definitely support CL
> > states. I have one here and it for sure works.
> >
> > What's the NVM version can you check? It could be that some older ones have
> > issues.
>
> The dock router (route 0-1, DROM 01ea:83b5) reports:
>
> /sys/bus/thunderbolt/devices/0-1/nvm_version
> 62.2
>
> Read with the dock authorized and thunderbolt.clx=0.
Okay that's recent enough. I do wonder if we try to enable CL2 too. We
should only do that for Gen 4 link. Can you still take dynamic debug log
for me without clx=0 so we can see that it tries to enable?
next prev parent reply other threads:[~2026-09-24 14:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 7:18 [BUG] thunderbolt: Anker Prime TB5 (1ea:83b5) reconnect-loops on Meteor Lake (8086:7ec3) unless clx=0 Kurt Lieber
2026-09-24 7:35 ` Mika Westerberg
2026-09-24 7:57 ` Kurt Lieber
2026-09-24 10:10 ` Mika Westerberg
2026-09-24 12:26 ` [PATCH] thunderbolt: Disable CL states for the Anker Prime TB5 dock Kurt Lieber
2026-09-24 12:57 ` Mika Westerberg
2026-09-24 13:33 ` Kurt Lieber
2026-09-24 14:54 ` Mika Westerberg [this message]
2026-09-25 0:02 ` Kurt Lieber
2026-09-25 5:01 ` Mika Westerberg
2026-09-26 7:02 ` Kurt Lieber
2026-09-26 10:27 ` Mika Westerberg
2026-09-26 11:37 ` Kurt Lieber
2026-09-28 9:25 ` Mika Westerberg
2026-09-28 9:36 ` Mika Westerberg
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=20260924145447.GR106095@black.igk.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=kurt@lieber.org \
--cc=linux-usb@vger.kernel.org \
--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