From: Darrell Gum <d@rrell.co>
To: "Francisco Beltrán Millalén" <fbeltranmillalen@gmail.com>
Cc: rafael@kernel.org, bhelgaas@google.com,
linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
lenb@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI: PCI: take native PME control on Apple machines
Date: Thu, 8 Oct 2026 11:55:45 -0700 [thread overview]
Message-ID: <20261008185546.86200-1-d@rrell.co> (raw)
In-Reply-To: <20260924132859.24751-1-fbeltranmillalen@gmail.com>
On Thu, 24 Sep 2026 10:28:59 -0300, Francisco Beltrán Millalén wrote:
> Since commit 7bc5a2bad0b8 ("ACPI: Support _OSI("Darwin") correctly")
[...]
Tested on a second MacBookPro14,3 on 7.2.5 (Omarchy's linux-omarchy
7.2.5-3). Your PCI/PM v2 series and the Alpine Ridge quirk were
applied as well. The full report is in reply to the series:
https://lore.kernel.org/all/20260930141914.6678-1-fbeltranmillalen@gmail.com/
Stock 7.2.5: with both Thunderbolt xHCIs (8086:15d4 at 07:00.0 and
7d:00.0) runtime-suspended, plugging a USB 3 stick into any USB-C port
produced no kernel messages at all. With power/control=on, it
enumerated at SuperSpeed immediately.
With this patch, _OSC reads "OS assumes control of [PCIeHotplug
SHPCHotplug PME AER PCIeCapability LTR DPC]". With both controllers
left at power/control=auto, the same stick enumerated at SuperSpeed
within about 1 s, and 7d:00.0 runtime-resumed on its own. A later
run gave the same result: about 1 s when plugged in before a lid-close
S3, and about 3 s for a replug about 2 min after resume, still with
power/control=auto.
The patches were tested together, not bisected. This is the result
that maps most directly onto this one patch.
Tested-by: Darrell Gum <d@rrell.co>
next prev parent reply other threads:[~2026-10-08 18:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 13:28 [PATCH] ACPI: PCI: take native PME control on Apple machines Francisco Beltrán Millalén
2026-09-24 13:34 ` sashiko-bot
2026-10-08 18:55 ` Darrell Gum [this message]
2026-10-08 23:29 ` Bjorn Helgaas
2026-10-09 8:23 ` Matthew Garrett
2026-10-09 12:14 ` Francisco Beltrán Millalén
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=20261008185546.86200-1-d@rrell.co \
--to=d@rrell.co \
--cc=bhelgaas@google.com \
--cc=fbeltranmillalen@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rafael@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.