Linux USB
 help / color / mirror / Atom feed
From: James R Taylor <jrtaylor11@gmail.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: linux-usb@vger.kernel.org,
	Mario Limonciello <mario.limonciello@amd.com>,
	Sanath S <Sanath.S@amd.com>,
	Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Subject: Re: thunderbolt: AMD Phoenix USB4 host advertises Gen3 Support=0 in SB LINK_CONF with TB5 device, link stuck at Gen2
Date: Mon, 09 Nov 2026 07:53:21 -0800 (PST)	[thread overview]
Message-ID: <6af1ec71.fb59a2f3.1b24d6.5d62@mx.google.com> (raw)
In-Reply-To: <20261109155007.GV176724@black.igk.intel.com>

Hi Mika,

On Mon, Nov 09, 2026 at 04:50:07PM +0100, Mika Westerberg wrote:
> That's the host side retimer.

Thanks, that clears it up.

> Agree it looks like the AMD host only gets the link up Gen2 for some
> reason. It could be retimer/PD firmware issue. Anyways I'm adding the AMD
> experts if they have any ideas.

Thank you very much for looking at this and for adding them.

For Mario, Sanath and Basavaraj, a short summary of the setup and
what has been measured so far (the full logs and tbdump output are
earlier in this thread):

  - Host: Minisforum UM890 Pro (AMD Phoenix), BIOS 1.06
    (11/10/2025), AGESA PhoenixPI-FP8-FP7 1.2.0.0a, kernel 7.2.15.
  - Device: Minisforum DEG2 (TB5 eGPU dock, NVM 62.42), StarTech
    TBLT5MM50CM240W 0.5 m TB5 cable.
  - Host-side retimer 1-0:2.1, vendor 0x7fea device 0x1032.
  - Link comes up as TBT, 10.0 Gb/s x2. Host PORT_CS_18 reports
    Cable USB4 Version 0 and CG3=0; the DEG2 side reports Version 1
    and CG3=1.
  - Sideband LINK_CONFIGURATION (0x0c): host 03 d3 03 (Gen3 bit not
    set), DEG2 03 f3 1b (Gen3 bit set). Writing the Gen3 bit on the
    host side from Linux fails with -EIO.
  - Same result with thunderbolt.host_reset=0 and =1, and on a clean
    boot without host_reset/pcie_aspm=off.
  - The firmware exposes no UCSI device (no USBC000/PNP0CA0 in ACPI),
    so /sys/class/typec is absent and I can't see from Linux which
    mode the PD controller chose.

I'm happy to collect any other register reads or logs that would
help.

Thanks again,
James


      reply	other threads:[~2026-11-09 15:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-08 13:15 thunderbolt: AMD Phoenix USB4 host advertises Gen3 Support=0 in SB LINK_CONF with TB5 device, link stuck at Gen2 James Taylor
2026-11-09 11:18 ` Mika Westerberg
2026-11-09 11:25   ` James Taylor
2026-11-09 14:20     ` Mika Westerberg
2026-11-09 14:39       ` James R Taylor
2026-11-09 15:39         ` Mika Westerberg
2026-11-09 15:41           ` James R Taylor
2026-11-09 15:50             ` Mika Westerberg
2026-11-09 15:53               ` James R Taylor [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=6af1ec71.fb59a2f3.1b24d6.5d62@mx.google.com \
    --to=jrtaylor11@gmail.com \
    --cc=Basavaraj.Natikar@amd.com \
    --cc=Sanath.S@amd.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=mika.westerberg@linux.intel.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