From: sashiko-bot@kernel.org
To: "Francisco Beltrán Millalén" <fbeltranmillalen@gmail.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: Extend Apple Thunderbolt power quirk to Alpine Ridge
Date: Thu, 24 Sep 2026 13:34:37 +0000 [thread overview]
Message-ID: <20260924133438.44FBF1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260924132815.24430-1-fbeltranmillalen@gmail.com>
> On Macs with an Alpine Ridge Thunderbolt 3 controller, suspending to RAM
> with anything plugged into a USB-C port leaves the PCIe link between the
> root port and the controller's upstream bridge permanently untrained on
> resume. The link does not merely fall back to a lower speed: it never
> starts. On a MacBookPro14,3 the root port reports
>
> LnkSta: Speed 2.5GT/s, Width x0
> LnkSta2: EqualizationComplete- EqualizationPhase1- Phase2- Phase3-
>
> with no correctable, non-fatal or fatal errors logged, and the link
> training state machine stuck at its first state. Both Thunderbolt
> controllers, both integrated xHCIs and all four USB-C ports are lost
> until reboot. Measured 15 failures out of 15 with a device attached,
> against 5 successes out of 5 with the ports empty; it follows the device,
> not the port, and affects either controller.
> [ ... ]
> and leaving it out is the conservative choice.
>
> Tested on 6.18.49 on a MacBookPro14,3.
>
> Signed-off-by: Francisco Beltrán Millalén <fbeltranmillalen@gmail.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260924132815.24430-1-fbeltranmillalen@gmail.com?part=1
next prev parent reply other threads:[~2026-09-24 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 13:28 [PATCH] PCI: Extend Apple Thunderbolt power quirk to Alpine Ridge Francisco Beltrán Millalén
2026-09-24 13:34 ` sashiko-bot [this message]
2026-10-08 18:55 ` Darrell Gum
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=20260924133438.44FBF1F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=fbeltranmillalen@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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