public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: whitequark <whitequark@whitequark.org>,
	Mario Limonciello <mario.limonciello@dell.com>,
	linux-kernel@vger.kernel.org
Subject: Re: USB type-C altmode support for UCSI
Date: Wed, 5 Sep 2018 16:34:50 +0300	[thread overview]
Message-ID: <20180905133450.GM2283@lahna.fi.intel.com> (raw)
In-Reply-To: <20180905132429.GB25121@kuha.fi.intel.com>

On Wed, Sep 05, 2018 at 04:24:29PM +0300, Heikki Krogerus wrote:
> +Mika, Mario, LKML
> 
> On Mon, Sep 03, 2018 at 02:17:46PM +0000, whitequark wrote:
> > After looking through LKML, I've seen that people refer to you when
> > discussing issues with USB-C device compatibility. Do you think you
> > could help me with an Apple Thunderbolt 2 to 3 adapter? I've spent
> > quite a while studying USB-C, reverse engineering platform and
> > adapter firmware and so on, and I'm quite stumped.
> > 
> > I have a Dell XPS13 laptop. UCSI advertises port altmodes
> > 8087:00000001, ff01:00001c46, 413c:00000001, in that order.
> > When I plug in the adapter, UCSI advertises partner altmode
> > 8087:00000001. A billboard class device enumerates. Nothing else
> > happens; the Thunderbolt NHI device doesn't appear, and if I force
> > it to appear via the WMI hook, there are no Thunderbolt events,
> > and the only device on the Thunderbolt bus is the root switch.

Some Dell XPS systems do not support that TBT2<->TBT3 adapter. I think I
tried this on XPS 15 9550 and XPS 13 9365 and in both cases it is
rejected. I think it has something to do with the PD controller
firmware. Same goes if you Plug TB16 dock and to that dock then connect
the adapter + device.

Mario probably has more input about this one.

  reply	other threads:[~2018-09-05 13:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1e8398f2c1790890f40b69f12e2934e3@whitequark.org>
     [not found] ` <20180903140623.GD15112@kuha.fi.intel.com>
     [not found]   ` <28522bb57c5d8f49416b9174b19b1625@whitequark.org>
2018-09-05 13:24     ` USB type-C altmode support for UCSI Heikki Krogerus
2018-09-05 13:34       ` Mika Westerberg [this message]
2018-09-05 13:50       ` Mario.Limonciello
2018-09-05 14:13         ` whitequark
2018-09-07 11:04           ` whitequark
2018-09-10 21:25             ` Mario.Limonciello
2018-09-11  9:32               ` Mika Westerberg
2018-09-11 13:02                 ` Mario.Limonciello
2018-10-06  6:01                   ` A different PD controller firmware problem? Theodore Y. Ts'o
2018-11-08 18:00                     ` Mario.Limonciello
2018-11-08 21:15                       ` Theodore Y. Ts'o
2018-11-10 20:13                         ` Theodore Y. Ts'o

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=20180905133450.GM2283@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@dell.com \
    --cc=whitequark@whitequark.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