From: James R Taylor <jrtaylor11@gmail.com>
To: linux-usb@vger.kernel.org
Subject: Re: thunderbolt: AMD Phoenix USB4 host advertises Gen3 Support=0 in SB LINK_CONF with TB5 device, link stuck at Gen2
Date: Sun, 15 Nov 2026 14:43:16 +0000 [thread overview]
Message-ID: <1794753796.37750.resend.hermes@gmail.com> (raw)
In-Reply-To: <dcc400cf-809e-4b7e-a14c-e4b2f469909d@amd.com>
(Resending to the list in plain text: my first copy was rejected for
containing HTML. Sorry for the noise.)
Hi Mario,
On Sun, Nov 15, 2026 at 02:13:37PM +0000, Mario Limonciello wrote:
> I'd lean on more likely a PD controller issue. Did you already look for
> a BIOS update? Most vendors distribute PD updates with BIOS/EC.
Thank you for looking at this. I'm on BIOS 1.06. Minisforum have a 1.07
image for the UM890 Pro with no release notes; its AGESA (PhoenixPI
1.2.0.0a) is the same as 1.06, and I couldn't tell from the image
whether it carries a PD or EC update, so I haven't flashed it yet.
> If there is no update available; can you start with reporting to your
> vendor and let them reproduce and get some PD traces to confirm?
I reported it to Minisforum on 8 November and it is with their firmware
team now. I'll pass on your PD controller suggestion and ask whether
1.07 or a separate EC/PD update changes anything.
Andrei, thank you for testing your SER8 and for laying the values out
side by side. The host-side values are identical on both machines,
including the retimer ID, PORT_CS_18 and the SB LINK_CONFIGURATION
03 d3 03, and your MacBook result rules out the cable and the DEG2. One
difference from Framework #56: the StarTech TBLT5MM50CM240W I have been
using is an active cable and it still trains TBT3, 2 x 10 Gb/s; the
DEG2's bundled cable gives the same result. Like your SER8, the UM890
Pro exposes no UCSI device, so I can't see the PD side from Linux
either.
Thanks,
James
prev parent reply other threads:[~2026-11-15 14:44 UTC|newest]
Thread overview: 12+ 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
2026-11-14 20:41 ` Re[2]: " Andrei Schapov
2026-11-15 14:13 ` Mario Limonciello
2026-11-15 14:43 ` 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=1794753796.37750.resend.hermes@gmail.com \
--to=jrtaylor11@gmail.com \
--cc=linux-usb@vger.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