linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: linux-usb@vger.kernel.org,
	Andreas Noever <andreas.noever@gmail.com>,
	Michael Jamet <michael.jamet@intel.com>,
	Mika Westerberg <westeri@kernel.org>,
	Yehezkel Bernat <YehezkelShB@gmail.com>,
	Imre Deak <imre.deak@intel.com>
Subject: Re: TB 5 Dock DP-Out non-functional
Date: Mon, 3 Nov 2025 12:26:48 +0100	[thread overview]
Message-ID: <20251103112648.GI2912318@black.igk.intel.com> (raw)
In-Reply-To: <lerwgbxoidxvfv3ajszi467rupujg465ukh3fcokihxpv2ikjr@rbke2a76anld>

Hi,

On Mon, Nov 03, 2025 at 12:01:06PM +0100, Frederik Schwan wrote:
> Whole log attached.

Great, thanks!

From that log the last BW allocation done by i915 is 12.5G:

[   51.572497] thunderbolt 0000:8a:00.0: 0:13 <-> 1:12 (DP): bandwidth allocation changed to 0/12500 Mb/s

> > Regarding the script, that's odd too but it could be that you have more
> > than one host router there (it is not clear from the truncated log). You
> > need to build the tbtools binaries though.
> 
> I do package tbtools for Arch so these are available.
> 
> tblist gives me:
> Domain 0 Route 0: 8087:7eb2 Intel Gen14
> Domain 1 Route 0: 17ef:a583 Lenovo ThinkPad P1 Gen8 / T1g Gen8
> Domain 1 Route 1: 0108:234d Lenovo ThinkPad Thunderbolt 5 Smart Dock 7500 - 40BA

Okay this has discrete Barlow Ridge TB5 host router.

> tbadapters --domain 1 --route 1:
>  1: Lane 0 (upstream)             CL0
>  2: Lane 1                        CL0
>  3: Lane 0                        CLd
>  4: Lane 1                        CLd
>  5: Lane 0                        CLd
>  6: Lane 1                        CLd
>  7: Lane 0                        CLd
>  8: Lane 1                        CLd
>  9: PCIe Up                       L1
> 10: PCIe Down                     Disabled
> 11: DisplayPort OUT               Disabled
> 12: DisplayPort OUT               Enabled

And this confirms that the DP tunnel is up.

That tb-bandwidth.sh script should work too (or tbtunnels -d1 -vv).

Anyways, from TB perspective this looks okay. Not sure about graphics. Imre
do you see anything?

  reply	other threads:[~2025-11-03 11:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-02 15:39 TB 5 Dock DP-Out non-functional Frederik Schwan
2025-11-03  5:56 ` Mika Westerberg
2025-11-03  8:54   ` Frederik Schwan
2025-11-03 10:26     ` Mika Westerberg
2025-11-03 11:01       ` Frederik Schwan
2025-11-03 11:26         ` Mika Westerberg [this message]
2025-11-03 12:08           ` Imre Deak
2025-11-03 14:55             ` Frederik Schwan

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=20251103112648.GI2912318@black.igk.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=imre.deak@intel.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=michael.jamet@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).