From: Peter Zijlstra <peterz@infradead.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: andreas.noever@gmail.com, michael.jamet@intel.com,
westeri@kernel.org, YehezkelShB@gmail.com,
linux-usb@vger.kernel.org
Subject: Re: Thunderbolt display chaining
Date: Tue, 22 Apr 2025 11:12:22 +0200 [thread overview]
Message-ID: <20250422091222.GB14170@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20250422050501.GF88033@black.fi.intel.com>
On Tue, Apr 22, 2025 at 08:05:01AM +0300, Mika Westerberg wrote:
> You can remedy this by not daisy chaining if you have multiple ports:
>
> TGL <-> M
> ^
> |
> v
> M
>
> Let me know if you need more information.
Ah, thanks. I tried googling things but stuff like this just wasn't easy
to find.
Yes, this seems to work. I can even drive both panels at 120Hz this way.
Now I've got to go order a second long TB cable :-)
Thanks!
prev parent reply other threads:[~2025-04-22 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 16:35 Thunderbolt display chaining Peter Zijlstra
2025-04-22 5:05 ` Mika Westerberg
2025-04-22 9:12 ` Peter Zijlstra [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=20250422091222.GB14170@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox