From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Stefan Hoffmeister <stefan.hoffmeister@gmail.com>
Cc: "Tomasz Moń" <desowin@gmail.com>,
"Heikki Krogerus" <heikki.krogerus@linux.intel.com>,
linux-usb@vger.kernel.org
Subject: Re: Thunderbolt: One missing DisplayPort?
Date: Tue, 31 May 2022 12:36:03 +0300 [thread overview]
Message-ID: <YpXhg6wPtotRk6c2@lahna> (raw)
In-Reply-To: <CALhB_QNh3vMn2+6H41MC_O0sKPfjiVrPeqmvpnLk=tuHUPQGdg@mail.gmail.com>
Hi,
On Mon, May 30, 2022 at 08:57:34PM +0200, Stefan Hoffmeister wrote:
> ********** $ cat /sys/kernel/debug/thunderbolt/0-0/port5/regs
> ********************
> # offset relative_offset cap_id vs_cap_id value
> 0x0000 0 0x00 0x00 0x9a1f8086
> 0x0001 1 0x00 0x00 0x05080239
> 0x0002 2 0x00 0x00 0x010e0101
> 0x0003 3 0x00 0x00 0x80500010
> 0x0004 4 0x00 0x00 0x4100000d
> 0x0005 5 0x00 0x00 0x00004809
> 0x0006 6 0x00 0x00 0x00000000
> 0x0007 7 0x00 0x00 0x00000000
> 0x0008 8 0x00 0x00 0x00000000
> 0x0039 0 0x04 0x00 0xc009048f
The bits 31:30 tell that this tunnel is active.
> ********** $ cat /sys/kernel/debug/thunderbolt/0-0/port6/regs
> ********************
> # offset relative_offset cap_id vs_cap_id value
> 0x0000 0 0x00 0x00 0x9a1f8086
> 0x0001 1 0x00 0x00 0x05080239
> 0x0002 2 0x00 0x00 0x010e0101
> 0x0003 3 0x00 0x00 0x80600010
> 0x0004 4 0x00 0x00 0x0100000d
> 0x0005 5 0x00 0x00 0x00004809
> 0x0006 6 0x00 0x00 0x00000000
> 0x0007 7 0x00 0x00 0x00000000
> 0x0008 8 0x00 0x00 0x00000000
> 0x0039 0 0x04 0x00 0x0009048f
This one is not.
> ********** $ cat /sys/kernel/debug/thunderbolt/0-1/port11/regs
> ********************
> # offset relative_offset cap_id vs_cap_id value
> 0x0000 0 0x00 0x00 0x15ef8086
> 0x0001 1 0x00 0x00 0x0608020a
> 0x0002 2 0x00 0x00 0x010e0102
> 0x0003 3 0x00 0x00 0x80b00008
> 0x0004 4 0x00 0x00 0x00800000
> 0x0005 5 0x00 0x00 0x00004809
> 0x0006 6 0x00 0x00 0x00000000
> 0x0007 7 0x00 0x00 0x00000000
> 0x0008 8 0x00 0x00 0x00000000
> 0x000a 0 0x03 0x00 0x00000339
> 0x000b 1 0x03 0x00 0x40110005
> 0x000c 2 0x03 0x00 0x00000000
> 0x000d 3 0x03 0x00 0x00000000
> 0x000e 4 0x03 0x00 0xffffffff
> 0x000f 5 0x03 0x00 0x00000000
> 0x0010 6 0x03 0x00 0x000009c4
> 0x0011 7 0x03 0x00 0x00c80002
> 0x0039 0 0x04 0x00 0x0009044f
> 0x003a 1 0x04 0x00 0x00004008
> 0x003b 2 0x04 0x00 0x000fff40
> 0x003c 3 0x04 0x00 0x00400005
> 0x003d 4 0x04 0x00 0x00c0a234
This is the "local" capability and it tells that this one supports MST
(bit 15).
I wonder if this dock has the two DP outputs behind a MST "hub" or so?
I've seen such devices out there. This would explain why there is only
single DP tunnel active.
I don't remember if you already mentioned but have you tried to connect
the second monitor to the USB-C downstream ports on that dock? At least
for some docks this is where the second DP OUT adapter is routed.
If the second DP tunnel gets activated you should also see bits 31:30 of
the port6/regs to be set by the connection manager firmware.
next prev parent reply other threads:[~2022-05-31 9:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 10:22 Thunderbolt: One missing DisplayPort? Stefan Hoffmeister
2022-05-24 10:55 ` Heikki Krogerus
2022-05-24 11:04 ` Mika Westerberg
2022-05-27 6:24 ` Stefan Hoffmeister
2022-05-27 9:10 ` Mika Westerberg
2022-05-28 14:29 ` Stefan Hoffmeister
2022-05-29 19:51 ` Stefan Hoffmeister
2022-05-30 8:33 ` Tomasz Moń
2022-05-30 9:54 ` Mika Westerberg
2022-05-30 18:57 ` Stefan Hoffmeister
2022-05-31 9:36 ` Mika Westerberg [this message]
2022-05-31 19:45 ` Stefan Hoffmeister
2022-06-01 10:51 ` Mika Westerberg
2022-06-02 19:34 ` Tomasz Moń
2022-06-03 5:04 ` Mika Westerberg
2022-06-08 14:27 ` Tomasz Moń
2022-06-11 16:29 ` Tomasz Moń
2022-06-07 17:28 ` Stefan Hoffmeister
2022-05-30 18:02 ` Stefan Hoffmeister
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=YpXhg6wPtotRk6c2@lahna \
--to=mika.westerberg@linux.intel.com \
--cc=desowin@gmail.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-usb@vger.kernel.org \
--cc=stefan.hoffmeister@gmail.com \
/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