From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: diego.sure@gmail.com
Cc: "Imre Deak" <imre.deak@intel.com>,
dri-devel@lists.freedesktop.org,
"Uma Shankar" <uma.shankar@intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Mika Westerberg" <westeri@kernel.org>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] drm/dp_tunnel: Allow BWA when the DP IN adapter does not advertise it
Date: Mon, 2 Nov 2026 14:01:45 +0100 [thread overview]
Message-ID: <20261102130145.GU158991@black.igk.intel.com> (raw)
In-Reply-To: <20261031-dp-tunnel-bwa-flag-v1-1-f94ed3179349@gmail.com>
Hi,
On Sat, Oct 31, 2026 at 01:18:18AM +0100, Diego Noguês via B4 Relay wrote:
> From: Diego Noguês <diego.sure@gmail.com>
>
> On an Alder Lake host (i7-1265U) with a Thunderbolt 4 dock (Dell WD22TB4,
> Goshen Ridge) driving two 4K@60 monitors through two DP tunnels, the
> monitor whose tunnel is created second is limited to 4K@30. Which monitor
> is affected depends only on the order in which they are powered on.
>
> The thunderbolt driver enables the BW allocation mode (BWA) on both DP IN
> adapters: it sets the CM BWA support (DP_USB4_DRIVER_BW_CAPABILITY), a
> group ID and the estimated BW. The DP IN adapter, however, never sets
> DP_IN_BW_ALLOCATION_MODE_SUPPORT in DP_TUNNELING_CAPABILITIES (0xe000d
> reads 0x01), so tunnel_regs_are_valid() rejects the tunnel with:
Alder Lake firmware really does not support this and by forcing it to be
enabled you may end up in untested code paths and interesting behavior :)
BWA was only officially supported starting from Meteor Lake.
next prev parent reply other threads:[~2026-11-02 13:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 0:18 [PATCH RFC] drm/dp_tunnel: Allow BWA when the DP IN adapter does not advertise it Diego Noguês via B4 Relay
2026-10-31 0:18 ` Diego Noguês
2026-10-31 0:22 ` sashiko-bot
2026-11-02 13:01 ` Mika Westerberg [this message]
2026-11-04 9:00 ` Diego C N
2026-11-02 13:33 ` ✗ CI.checkpatch: warning for " Patchwork
2026-11-02 13:35 ` ✓ CI.KUnit: success " Patchwork
2026-11-02 14:09 ` ✓ Xe.CI.BAT: " Patchwork
2026-11-02 15:33 ` ✓ i915.CI.BAT: " Patchwork
2026-11-02 15:35 ` ✓ Xe.CI.FULL: " Patchwork
2026-11-02 16:06 ` ✓ i915.CI.Full: " Patchwork
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=20261102130145.GU158991@black.igk.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=airlied@gmail.com \
--cc=diego.sure@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=uma.shankar@intel.com \
--cc=ville.syrjala@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.