From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Grant Morphett <grant@gmorph.com>
Cc: Andreas Noever <andreas.noever@gmail.com>,
Mika Westerberg <westeri@kernel.org>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
linux-usb@vger.kernel.org
Subject: Re: [PATCH] thunderbolt: Enable hidden DP OUT adapter on Dell TB16 dock
Date: Wed, 4 Nov 2026 13:00:38 +0100 [thread overview]
Message-ID: <20261104120038.GC176724@black.igk.intel.com> (raw)
In-Reply-To: <20261101212311.10946-1-grant@gmorph.com>
Hi,
On Mon, Nov 02, 2026 at 08:23:11AM +1100, Grant Morphett wrote:
> The Dell TB16 Thunderbolt 3 dock consists of two Alpine Ridge 4C routers
> in a chain: one in the captive cable module (DROM 00d4:b051 "Dell
> Thunderbolt Cable") and one in the dock itself (DROM 00d4:b054 "Dell
> Thunderbolt Dock"). The dock has four video connectors: mini DisplayPort,
> HDMI, full size DisplayPort and VGA.
>
> Mini DisplayPort and HDMI sit behind an MST hub on DP OUT adapter 8 of
> the dock router and work fine. Full size DisplayPort and VGA are wired
> to DP OUT adapter 8 of the cable router, but the cable router's DROM
> marks that adapter as disabled. The software connection manager
> therefore never initializes it, never tunnels DisplayPort to it, and a
> monitor on the full size DisplayPort or VGA connector stays dark. Only
> two external displays can be used with the dock, while all of them work
> with the firmware connection manager (and under Windows).
>
> The adapter is real: its adapter config space reports type DP/HDMI OUT
> (0xe0102), it raises hot plug events when a monitor is attached to the
> DisplayPort or VGA connector, and once it is enabled the DP tunnel to it
> is established and the display comes up. The same DROM also fails its
> CRC32 check (expected 0xaf438340, got 0xaf4383c0), so the port
> disabled bit is likely just wrong rather than intentional:
>
> 1: DROM data CRC32 mismatch (expected: 0xaf438340, got: 0xaf4383c0), continuing
> 1:8: disabled by eeprom
> acking hot plug event on 1:8
>
> Add a quirk for the cable router that re-enables adapter 8 if its
> config space confirms it is a DP OUT adapter, and initializes it the
> same way tb_switch_add() does for the other ports. tb_init_port() is
> made non-static for this.
>
> With the quirk applied, both DP tunnels come up at boot and all three
> external monitors work:
>
> 1:8: enabling DP OUT adapter disabled in DROM
> 1:8: DP OUT available
> 0:5 <-> 1:8 (DP): activating
> 301:8: DP OUT available
> 0:6 <-> 301:8 (DP): activating
>
> Tested on a Lenovo ThinkPad X1 Yoga Gen 8 (Raptor Lake, USB4 host
> 8087:a76d) with a TB16 at dock NVM 27.0 / cable NVM 16.0, driving three
> 1920x1080 monitors on mini DisplayPort, HDMI and full size DisplayPort.
Yeah, the firmware connection manager ignored the DROM entries so that's
why it worked with the TB3 hosts but fails with the USB4 software
connection manager.
> Assisted-by: LLM
> Signed-off-by: Grant Morphett <grant@gmorph.com>
> ---
> drivers/thunderbolt/quirks.c | 35 +++++++++++++++++++++++++++++++++++
> drivers/thunderbolt/switch.c | 7 ++++---
> drivers/thunderbolt/tb.h | 1 +
> 3 files changed, 40 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/thunderbolt/quirks.c b/drivers/thunderbolt/quirks.c
> index 2722918..4529fa4 100644
> --- a/drivers/thunderbolt/quirks.c
> +++ b/drivers/thunderbolt/quirks.c
> @@ -65,6 +65,38 @@ static void quirk_stuck_pending(struct tb_switch *sw)
> }
> }
>
> +/*
> + * The DROM of the Dell TB16 cable module marks adapter 8 as disabled
> + * even though it is the DP OUT adapter wired to the dock's full size
> + * DisplayPort and VGA connectors. Enable it so that the software
> + * connection manager can tunnel DisplayPort to it.
> + */
> +static void quirk_dell_tb16_dp_out(struct tb_switch *sw)
> +{
> + struct tb_port *port;
> + u32 type;
> +
> + if (sw->config.max_port_number < 8)
> + return;
> +
> + port = &sw->ports[8];
> + if (!port->disabled)
> + return;
> +
> + if (tb_port_read(port, &type, TB_CFG_PORT, 2, 1))
> + return;
> + if ((type & 0xffffff) != TB_TYPE_DP_HDMI_OUT)
> + return;
> +
> + port->disabled = false;
> + if (tb_init_port(port)) {
> + port->disabled = true;
> + return;
> + }
> +
> + tb_port_info(port, "enabling DP OUT adapter disabled in DROM\n");
> +}
> +
> struct tb_quirk {
> u16 hw_vendor_id;
> u16 hw_device_id;
> @@ -77,6 +109,9 @@ static const struct tb_quirk tb_quirks[] = {
> /* Dell WD19TB supports self-authentication on unplug */
> { 0x0000, 0x0000, 0x00d4, 0xb070, quirk_force_power_link },
> { 0x0000, 0x0000, 0x00d4, 0xb071, quirk_force_power_link },
> + /* Dell TB16 cable module DROM hides the second DP OUT adapter */
> + { 0x8086, PCI_DEVICE_ID_INTEL_ALPINE_RIDGE_4C_BRIDGE, 0x00d4, 0xb051,
> + quirk_dell_tb16_dp_out },
>
> /* Intel Titan Ridge CLx is unstable on early firmware versions */
> { 0x8086, PCI_DEVICE_ID_INTEL_TITAN_RIDGE_DD_BRIDGE, 0x0000, 0x0000,
> diff --git a/drivers/thunderbolt/switch.c b/drivers/thunderbolt/switch.c
> index d22d8db..e4629ed 100644
> --- a/drivers/thunderbolt/switch.c
> +++ b/drivers/thunderbolt/switch.c
> @@ -701,15 +701,16 @@ int tb_port_reset(struct tb_port *port)
> return tb_lc_reset_port(port);
> }
>
> -/*
> +/**
> * tb_init_port() - initialize a port
> + * @port: Port to initialize
> *
> - * This is a helper method for tb_switch_alloc. Does not check or initialize
> + * This is a helper method for tb_switch_add(). Does not check or initialize
> * any downstream switches.
> *
> * Return: %0 on success, negative errno otherwise.
> */
> -static int tb_init_port(struct tb_port *port)
> +int tb_init_port(struct tb_port *port)
I'm not too happy to expose this. Instead let's add tb_check_drom_quirks()
right after DROM has been parsed and then that one can "correct" the wrong
DROM entries.
> {
> int res;
> int cap;
> diff --git a/drivers/thunderbolt/tb.h b/drivers/thunderbolt/tb.h
> index e868457..cb84182 100644
> --- a/drivers/thunderbolt/tb.h
> +++ b/drivers/thunderbolt/tb.h
> @@ -1099,6 +1099,7 @@ int tb_switch_pcie_l1_enable(struct tb_switch *sw);
> int tb_switch_xhci_connect(struct tb_switch *sw);
> void tb_switch_xhci_disconnect(struct tb_switch *sw);
>
> +int tb_init_port(struct tb_port *port);
> int tb_port_state(struct tb_port *port);
> int tb_wait_for_port(struct tb_port *port, bool wait_if_unplugged);
> int tb_port_add_nfc_credits(struct tb_port *port, int credits);
> --
> 2.53.0
next prev parent reply other threads:[~2026-11-04 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 21:23 [PATCH] thunderbolt: Enable hidden DP OUT adapter on Dell TB16 dock Grant Morphett
2026-11-01 21:29 ` sashiko-bot
2026-11-04 12:00 ` Mika Westerberg [this message]
2026-11-06 6:26 ` [PATCH v2] " Grant Morphett
2026-11-06 6:33 ` sashiko-bot
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=20261104120038.GC176724@black.igk.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=grant@gmorph.com \
--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