From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Duff O'Melia <duff@omelia.org>
Cc: westeri@kernel.org, andreas.noever@gmail.com,
YehezkelShB@gmail.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, imre.deak@intel.com
Subject: Re: [RFC PATCH] thunderbolt: Tunnel only the first DP OUT of Apple Studio Displays
Date: Fri, 13 Nov 2026 08:50:50 +0100 [thread overview]
Message-ID: <20261113075050.GN259790@black.igk.intel.com> (raw)
In-Reply-To: <82a62e13-928a-4973-b88f-ea2642132fc1@app.fastmail.com>
Hi,
On Thu, Nov 12, 2026 at 05:38:46PM -0500, Duff O'Melia wrote:
> Hi Mika,
>
> On Mon, Nov 09, 2026 at 11:30:39AM +0100, Mika Westerberg wrote:
> > Can you provide full dmesg with thunderbolt.dyndbg=+p and drm.debug=0x10e
> > in the kernel command line when you have everything connected and the issue
> > reproduces?
>
> Sure, it's attached, xz-compressed. It's from a reboot with everything
> connected, on Omarchy's 7.2.15 kernel with its stock Thunderbolt driver
> (my patch not applied). I added log_buf_len=64M so the start of the boot
> isn't lost. I removed MAC addresses, USB serial numbers and some
> firewall log lines, and changed nothing else.
>
> In short:
>
> - 0-3 is the 2026 model (0x8025). Both of its DP OUT adapters got
> tunneled: 0:5 <-> 3:11 and 0:10 <-> 3:12.
> - 1-1 is a 2022 model (0x801f) on the second host router. It got
> 0:6 <-> 1:10.
> - 0-1 is the other 2022 model. It came up last, found no free DP IN
> adapter ("no suitable DP IN adapter available, not tunneling") and
> stays dark.
> - In xe, DP-1 (DPTUN 0:1:5) is the 2026 model's first tile, DP-3
> (DPTUN 0:1:10) its second tile, and DP-2 (DPTUN 1:1:6) the 2022
> model. DP-1 and DP-2 run at 5120x2880.
>
> One correction to my patch description: on this boot DP-3 isn't
> disabled. Pipe D is active on it at 2560x2880 with no framebuffer on its
> primary plane, and the compositor doesn't list it as a monitor. So the
> second tile's stream does come up, but it shows nothing.
Thanks! Confirmed:
[ 1.099566] thunderbolt 0000:00:0d.2: 0:5: DP IN resource available
[ 1.101235] thunderbolt 0000:00:0d.2: 0:10: DP IN resource available
Both DP INs of domain0
[ 2.417970] thunderbolt 0000:00:0d.2: 0:5 <-> 3:11 (DP): activating
First DP tunnel
[ 2.428951] thunderbolt 0000:00:0d.3: acking hot unplug event on 0:10
[ 2.429566] thunderbolt 0000:00:0d.2: 0: allocated DP resource for port 10
[ 2.433756] thunderbolt 0000:00:0d.2: 0:10 <-> 3:12 (DP): activating
Secodn DP tunnel. However, the DP resource in 0:10 is shared with domain1
0:10 as well so that leaves only one DP IN for domain1 (0:6).
[ 1.169534] thunderbolt 0000:00:0d.3: 0:6: DP IN resource available
[ 1.170368] thunderbolt 0000:00:0d.3: 0:10: DP IN resource available
[ 2.699961] thunderbolt 0000:00:0d.3: 0:6 <-> 1:10 (DP): activating
And this is that tunnel. Then you run out of DP INs.
It would be good if Imre could take a look from DP perspective if that
second tile in the 2026 model can be used.
I do have an internal patch series where userspace can affect what DP
IN/OUT pairs should be selected via a BPF hook but that's still work in
progress. That would help here.
prev parent reply other threads:[~2026-11-13 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 15:44 Duff OMelia
2026-11-09 10:30 ` Mika Westerberg
2026-11-12 22:38 ` Duff O'Melia
2026-11-13 7:50 ` Mika Westerberg [this message]
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=20261113075050.GN259790@black.igk.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=duff@omelia.org \
--cc=imre.deak@intel.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®