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: Sat, 11 Jun 2022 18:29:28 +0200 [thread overview]
Message-ID: <494c3280c58455b2439559f1b48858caf22b8c8f.camel@gmail.com> (raw)
In-Reply-To: <cf0dbecff8e70d15c7121bfdee16d945ba52b55c.camel@gmail.com>
On Wed, 2022-06-08 at 16:27 +0200, Tomasz Moń wrote:
> 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 managed to get an active 3 meters long USB Type-C cable. It is both a
directional cable (meaning the host end has to be plugged into laptop
and sink into dock) and appear to have working display port only when
connected with correct plug orientation. That is, rotating USB-C plug
180 degrees switches between working DP altmode and non-working.
The active cable I have features retimer in the middle of the cable.
The retimer is definitely noticeable (it is bulky) and does get warm
when in use.
This cable indeed does inhibit Thunderbolt operation and dock status in
boltctl is disconnected.
The EMCA information for the active cable is below. Even though the
cable is 3 meters long it claims to be 2 meters.
Type Active Cable
Vendor Unknown (0x0bda)
Specs [ <20ns (~2m) ] [ 20V ] [ 3A ] [ USB3 10Gbps ]
VER HW:0001 FW:0002 VDO:0 v:2
Vdo object hex
IdHeader 0x24000bda
CertStat 0x00000000
Product 0x00000209
Cable 0x120851b2
SVISD 0x0bdaff01
TBT3/4 0x00000000
next prev parent reply other threads:[~2022-06-11 16:29 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ń
2022-06-11 16:29 ` Tomasz Moń [this message]
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=494c3280c58455b2439559f1b48858caf22b8c8f.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