From: "Tomasz Moń" <desowin@gmail.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Stefan Hoffmeister <stefan.hoffmeister@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
linux-usb@vger.kernel.org
Subject: Re: Thunderbolt: One missing DisplayPort?
Date: Wed, 08 Jun 2022 16:27:24 +0200 [thread overview]
Message-ID: <cf0dbecff8e70d15c7121bfdee16d945ba52b55c.camel@gmail.com> (raw)
In-Reply-To: <YpmWXl5Y/VToYFvJ@lahna>
On Fri, 2022-06-03 at 08:04 +0300, Mika Westerberg wrote:
> On Thu, Jun 02, 2022 at 09:34:27PM +0200, Tomasz Moń wrote:
> > How do I determine that the cable is non-Thunderbolt Type-C?
>
> It does not have that "lightning" logo on the connector.
I got two more (to a total of 4) cables without lightning logo and all
seem to enter Thunderbolt mode.
> > I have tried with two different brands 1m USB Type-C cables that are
> > not advertised as Thunderbolt. Both cables are electronically marked
> > and 5A capable. When the docking station is connected using these
> > cables, it operates in Thunderbolt mode.
>
> Oh, yeah it is possible actually that with a passive type-C cable that
> it still enters TBT/USB4 mode (20G). I think.
Yes, with all the cables boltctl shows 20 Gb/s = 2 lanes * 10 Gb/s
With the 0.7m cable that came with dock (without e-Marker), boltctl
shows 40 Gb/s = 2 lanes * 20 Gb/s
> > If the device was operating in USB (+DP altmode), I assume that boltctl
> > would show that the docking station status as disconnected?
>
> Correct.
>
> > Can I read the cable EMCA details in Linux?
>
> This I don't know.
My USB-C Power Meter shows basic EMCA details. I presume the
information is not complete (it only shows it on small display, I
didn't find option to export/dump EMCA).
Below is the EMCA for all 4 cables. None support Thunderbolt, but all,
even the 3m one, manage to enter Thunderbolt mode.
Type Passive Cable
Vendor CE-LINK (0x2095)
Specs [ <10ns (~1m) ] [ 20V ] [ 5A ] [ USB3 10Gbps ]
VER HW:0009 FW:0001 VDO:0 v:3
Vdo object hex
IdHeader 0x18002095
CertStat 0x00000974
Product 0x00050310
Cable 0x91082042
SVISD 0x00000000
TBT3/4 0x00000000
Type Passive Cable
Vendor Unknown (0x0000)
Specs [ <10ns (~1m) ] [ 20V ] [ 5A ] [ USB3 10Gbps ]
VER HW:0000 FW:0000 VDO:0 v:3
Vdo object hex
IdHeader 0x18000000
CertStat 0x00000000
Product 0x00000000
Cable 0x00082042
SVISD 0x00000000
TBT3/4 0x00000000
Type Passive Cable
Vendor VIA Labs (0x2109)
Specs [ <20ns (~2m) ] [ 20V ] [ 5A ] [ USB3 10Gbps ]
VER HW:0000 FW:0000 VDO:0 v:3
Vdo object hex
IdHeader 0x18002109
CertStat 0x00000000
Product 0x00000000
Cable 0x00004042
SVISD 0x00000000
TBT3/4 0x00000000
Type Passive Cable
Vendor Yichong (0x315c)
Specs [ <30ns (~3m) ] [ 20V ] [ 5A ] [ USB3 10Gbps ]
VER HW:0001 FW:0001 VDO:0 v:3
Vdo object hex
IdHeader 0x1800315c
CertStat 0x00004244
Product 0x00020002
Cable 0x11086042
SVISD 0x00000000
TBT3/4 0x00000000
next prev parent reply other threads:[~2022-06-08 14:27 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
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ń [this message]
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=cf0dbecff8e70d15c7121bfdee16d945ba52b55c.camel@gmail.com \
--to=desowin@gmail.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-usb@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--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