Re: [PATCH RFC] thunderbolt: Re-add DP resources on resume

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

On Wed, Sep 17, 2025 at 06:12:31PM +0800, 李佳怡 wrote:
> 
> As requested, I've attached the complete dmesg output (from boot to after
> resume) reproducing the issue.
> 
> Testing Methodology:
> 1. Start with the Targus Thunderbolt dock already connected to the system
> 2. Enter S3 suspend (sleep) with no DP monitor connected to the dock
> 3. Resume from S3
> 4. After the system has fully resumed, connect the DP monitor to the dock

Thanks! It is badly line wrapped. I wonder if you can just attach it?
Anyways I found some unexpected things there:

> [    8.647850] With USB4 patch v1.0.0

What is this? ;-)

> [    8.647860] ACPI: bus type thunderbolt registered
> [    8.664660] [7] nhi_probe:1326: thunderbolt 0000:2c:00.0: total paths: 21
> [    8.665209] [7] tb_ring_alloc:586: thunderbolt 0000:2c:00.0: allocating
> TX ring 0 of size 10
> [    8.665243] [7] tb_ring_alloc:586: thunderbolt 0000:2c:00.0: allocating
> RX ring 0 of size 10
> [    8.665267] [7] tb_ctl_alloc:665: thunderbolt 0000:2c:00.0: control
> channel created
> [    8.665272] [7] icm_probe:2549: thunderbolt 0000:2c:00.0: ICM not
> supported on this controller
> [    8.665285] [7] tb_ring_free:840: thunderbolt 0000:2c:00.0: freeing RX
> ring 0
> [    8.665294] [7] tb_ring_free:840: thunderbolt 0000:2c:00.0: freeing TX
> ring 0

What is this?

Is this Intel TB/USB4 controller or something else? All USB4 compliant
controllers should go directly to tb.c as that's the part dealing with
software connection manager. The above looks like it tries first with the
firmware connection manager and that should not happen outside of Intel
Thunderbolt 3 hosts.