Re: [BUG] thunderbolt: Anker Prime TB5 (1ea:83b5) reconnect-loops on Meteor Lake (8086:7ec3) unless clx=0

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

Hi,

On Thu, Sep 24, 2026 at 07:57:10AM +0000, Kurt Lieber wrote:
> Hi Mika,
> 
> On Thu, Sep 24, 2026 at 07:35:22AM +0000, Mika Westerberg wrote:
> > Can you test with the dynamic debug enabled and provide full dmesg? Or
> > alternatively run:
> >
> >   # tbdump -r 1 -a 1 -vv -N2 LANE_ADP_CS_0
> >
> > and provide the output. This needs to be done when the dock is connected
> > (with clx=0 is okay). This should show if the dock claims to support CL
> > states.
> 
> The dock was connected and authorized. thunderbolt is loaded with clx=0
> (/sys/module/thunderbolt/parameters/clx reads N). 
> 
> # tbdump -r 1 -a 1 -vv -N2 LANE_ADP_CS_0
> 0x0036 0x1cfe01c0 0b00011100 11111110 00000001 11000000 .... LANE_ADP_CS_0
>   [00:07]       0xc0 Next Capability Pointer
>   [08:15]        0x1 Capability ID
>   [16:19]        0xe Supported Link Speeds
>   [20:21]        0x3 Supported Link Widths (SLW)
>   [22:23]        0x3 Gen 4 Asymmetric Support (G4AS)
>   [26:26]        0x1 CL0s Support
>   [27:27]        0x1 CL1 Support
>   [28:28]        0x1 CL2 Support

Yeah this is what I suspected. It claims to support all of them but
probably actually does not. This should have an entry in quirks.c then.
Want to do that? If not let me know and I'll make a patch.