From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: hans@kilurion.com
Cc: Mika Westerberg <westeri@kernel.org>,
Andreas Noever <andreas.noever@gmail.com>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] thunderbolt: Keep Meteor Lake host routers powered in DP redrive mode
Date: Tue, 6 Oct 2026 13:01:12 +0200 [thread overview]
Message-ID: <20261006110112.GP176164@black.igk.intel.com> (raw)
In-Reply-To: <20261006-tb-mtl-redrive-v1-1-5ec921114c37@kilurion.com>
Hi,
On Tue, Oct 06, 2026 at 10:06:43AM +0200, Hans van Essen via B4 Relay wrote:
> From: Hans van Essen <hans@kilurion.com>
>
> When a DisplayPort Alt Mode (non-Thunderbolt) dock is connected to the
> USB4 port of an Arrow Lake-H system with the integrated Meteor Lake-P
> host router (8086:7ec2), the USB functions of the dock work but the DP
> AUX transfers time out and no monitor is detected. It only works if the
> port was used with a Thunderbolt dock before and the system was not
> powered off in between; suspend and warm reboot keep it working.
>
> The Barlow Ridge host routers already have QUIRK_KEEP_POWER_IN_DP_REDRIVE
> so that the host router does not enter runtime suspend while the USB4
> port is in DP redrive mode. Apply the same quirk to the integrated
> Meteor Lake host routers. With this the driver logs "enter redrive mode,
> keeping powered" when the dock is plugged in and the monitors come up
> after a cold boot.
Yes, Barlow Ridge needs it but it's a special case. ARL should not need
this - its all routed internally so something else is wrong here.
Can you share full dmesg when this issue happens? Please add
thunderbolt.dydnbg=+p too although this really has nothing to do with TB if
the port is in redrive mode.
prev parent reply other threads:[~2026-10-06 11:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 8:06 Hans van Essen via B4 Relay
2026-10-06 11:01 ` 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=20261006110112.GP176164@black.igk.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=hans@kilurion.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®