Linux USB
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Mykola Dimura <mykola.dimura@gmail.com>
Cc: westeri@kernel.org, linux-usb@vger.kernel.org
Subject: Re: thunderbolt: second DP tunnel starved at boot while first tunnel's DPRX read is pending
Date: Mon, 9 Nov 2026 12:00:04 +0100	[thread overview]
Message-ID: <20261109110004.GO176724@black.igk.intel.com> (raw)
In-Reply-To: <CAGYMYpgLU20vVmwnWyQkYgvjL=fo+Rb8TxYJUu31FSPnhJ9DpQ@mail.gmail.com>

Hi,

On Sat, Nov 07, 2026 at 04:11:22PM +0100, Mykola Dimura wrote:
> Hi,
> 
> With two monitors on a Thunderbolt 4 dock, one of them comes up limited
> to 4K@30 after every boot (or dock re-plug). Which one gets 60 Hz is
> effectively random. Plugging the monitors in one at a time, in the right
> order, gives 4K@60 on both until the next boot. The cause is
> the order-dependent DP tunnel bandwidth reservation in tb_tunnel_one_dp().

Yes, this is by design. It's now called the "legacy" mode because it works
exactly like the firmware CM: first monitor gets all, second gets what is
left. So plugging them one by one is the correct workaround. The solution
to this is the bandwidth allocation mode but unfortunately it's not
supported until Meteor Lake.

We don't really want to add any new command line parameters. I have an
internal patch series that makes it possible from userspace to affect the
monitor selection via eBPF but that's not yet ready to be upstreamed. It
would help in your case though.

  reply	other threads:[~2026-11-09 11:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-07 15:11 thunderbolt: second DP tunnel starved at boot while first tunnel's DPRX read is pending Mykola Dimura
2026-11-09 11:00 ` Mika Westerberg [this message]
2026-11-09 19:54   ` Mykola Dimura

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=20261109110004.GO176724@black.igk.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=mykola.dimura@gmail.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