All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Mario Limonciello <superm1@kernel.org>
Cc: Sebastian Loscher <krang@krang.de>,
	linux-usb@vger.kernel.org, andreas.noever@gmail.com
Subject: Re: [BUG] thunderbolt: USB4 v2 TBGAA tunnel creation crash in TMU enhanced uni-directional mode
Date: Fri, 29 May 2026 08:35:25 +0200	[thread overview]
Message-ID: <20260529063525.GK3102@black.igk.intel.com> (raw)
In-Reply-To: <09372c24-0812-4f14-8d23-7d44028fb499@kernel.org>

On Thu, May 28, 2026 at 10:13:28PM +0100, Mario Limonciello wrote:
> 
> > The other thing I noticed is that the host is USB4v2 as well (well
> > according to the TMU configuration). @Mario is that right? I was not sure
> > if AMD is v2.
> 
> AMD's integrated one is not USB4v2, but I believe this specific design
> actually has both AMD integrated USB4 as well as a discrete Intel USB4v2
> soldered down on the MB.

Ah okay.

> That's why I was suggesting to try some of the ports to rule out if it's a
> USB4v2 unique issue. I think he said the front ports are USB4 and rear ports
> are USB4v2.

Agree, doing this makes sense.

      reply	other threads:[~2026-05-29  6:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-23 16:43 [BUG] thunderbolt: USB4 v2 TBGAA tunnel creation crash in TMU enhanced uni-directional mode Sebastian Loscher
2026-05-25  4:44 ` Mika Westerberg
2026-05-25 22:22   ` Mario Limonciello
2026-05-26  4:07     ` Mika Westerberg
2026-05-26 16:03       ` Sebastian Loscher
2026-05-27 12:26         ` Mika Westerberg
2026-05-27 19:19           ` Sebastian Loscher
2026-05-29  6:34             ` Mika Westerberg
2026-05-29 20:05               ` Sebastian Loscher
2026-05-31 13:15                 ` Mario Limonciello
2026-06-01  4:40                 ` Mika Westerberg
2026-05-28 21:13           ` Mario Limonciello
2026-05-29  6:35             ` Mika Westerberg [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=20260529063525.GK3102@black.igk.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=andreas.noever@gmail.com \
    --cc=krang@krang.de \
    --cc=linux-usb@vger.kernel.org \
    --cc=superm1@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.