Re: [PATCH] thunderbolt: Disable CL states for the Anker Prime TB5 dock

[Mika Westerberg <mika.westerberg@linux.intel.com>]

Hi,

On Fri, Sep 25, 2026 at 12:02:28AM +0000, Kurt Lieber wrote:
> Hi Mika,
> 
> On Thu, Sep 24, 2026 at 02:54:56PM +0000, Mika Westerberg wrote:
> > 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?
> 
> Dynamic debug with thunderbolt.clx left at Y, dock plugged in (route 1,
> DROM 01ea:83b5, NVM 62.2). The same sequence repeats about once a
> second. CL2 does not appear in the trace. What it enables is CL0s/CL1:
> 
>   thunderbolt 0000:00:0d.3: 1: current link speed 20.0 Gb/s
>   thunderbolt 0000:00:0d.3: 1: current link width symmetric, single lane
>   thunderbolt 0000:00:0d.3: 1: link width set to symmetric, dual lanes
>   thunderbolt 0000:00:0d.3: 1:1: CLx: CL0s/CL1 supported
>   thunderbolt 0000:00:0d.3: 0:1: CLx: CL0s/CL1 supported
>   thunderbolt 0000:00:0d.3: 1: CLx: CL0s/CL1 enabled
>   thunderbolt 0000:00:0d.3: 1: TMU: mode change off -> uni-directional, LowRes requested
>   thunderbolt 0000:00:0d.3: 1: TMU: failed to enable mode uni-directional, LowRes: -107
>   thunderbolt 0000:00:0d.3: 1: failed to enable TMU
>   thunderbolt 0000:00:0d.3: 1: USB3 tunnel creation failed
>   thunderbolt 0000:00:0d.3: 1:12: DP tunnel activation failed, aborting
>   thunderbolt 0-1: device disconnected

I just tried on my side MTL/PTL + BR Hub and works fine with CL0s/CL1
enabled. Also checked release notes of the NVM and there are no mention
about issues with CLx with the one you are running.

There is one more thing that we can check though, can you run:

  # tbdump -r 1 -a 1 -vv -N 1 PORT_CS_18

and provide the output?