mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sven Peter <sven@kernel.org>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Benson Leung <bleung@chromium.org>,
	Abhishek Pandit-Subedi <abhishekpandit@chromium.org>,
	Jameson Thies <jthies@google.com>,
	Andrei Kuchynski <akuchynski@chromium.org>,
	Tzung-Bi Shih <tzungbi@kernel.org>,
	Guenter Roeck <groeck@chromium.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: typec: tbt: Correct swapped TBT adapter type values
Date: Mon, 24 Aug 2026 13:31:54 +0200	[thread overview]
Message-ID: <20514e95-60ea-48de-979b-87b1dd7bcc12@kernel.org> (raw)
In-Reply-To: <aowm3TvXYnUv78FM@black.igk.intel.com>



On 8/24/26 13:11, Heikki Krogerus wrote:
> On Tue, Aug 18, 2026 at 06:20:03PM +0200, Sven Peter wrote:
>> Table F-10 of the USB Type-C Cable and Connector Specification R2.5 on
>> page 412 defines bit 16 of the TBT3 Device Discover Mode VDO as 0 = TBT3
>> Adapter and 1 = TBT2 Legacy Adapter. Linux has those two swapped since
>> their original introduction in commit ca469c292edc ("usb: typec: Add
>> definitions for Thunderbolt 3 Alternate Mode").
>>
>> ChromiumOS EC's include/usb_pd_tbt.h has them the correct way around
>> and references the USB Type-C ECN "Thunderbolt 3 Compatibility Updates"
>> as fixing an error where they were originally swapped which is presumably
>> where the wrong order originally came from.
>>
>> I've also confirmed the correct mapping with an Apple Thunderbolt 3
>> to Thunderbolt 2 adapter which does set bit 16 in that VDO.
>>
>> Swap the two values and update all users. Also rename the old defines
>> so that no user accidentally ends up with an inverted value.
>> No functional change.
>>
>> Link: https://usb.org/document-library/usb-type-cr-cable-and-connector-specification-release-25
>> Link: https://chromium.googlesource.com/chromiumos/platform/ec/+/db93814b6e73c8545d23714fe0674c10814d901a/include/usb_pd_tbt.h#90
>> Signed-off-by: Sven Peter <sven@kernel.org>
> Shouldn't this be marked as a fix?

I left it out deliberately together with Cc: stable because there's no 
functional change but I can just add it if you want to. The original 
commit is already in the message.
>
> Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>

Thanks!


Sven


      reply	other threads:[~2026-08-24 11:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-18 16:20 Sven Peter
2026-08-19 10:34 ` Konrad Dybcio
2026-08-24 11:11 ` Heikki Krogerus
2026-08-24 11:31   ` Sven Peter [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=20514e95-60ea-48de-979b-87b1dd7bcc12@kernel.org \
    --to=sven@kernel.org \
    --cc=abhishekpandit@chromium.org \
    --cc=akuchynski@chromium.org \
    --cc=andersson@kernel.org \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=groeck@chromium.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=jthies@google.com \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=tzungbi@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

all inboxes | Powered by JetHome®