From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Linux ACPI <linux-acpi@vger.kernel.org>
Cc: Linux PM <linux-pm@vger.kernel.org>,
Linux PCI <linux-pci@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Bjorn Helgaas <helgaas@kernel.org>, Armin Wolf <w_armin@gmx.de>
Subject: [RESEND][PATCH v1 0/2] PCI: ACPI: PM: Rework root bus wakeup notification setup and wakeup source registration
Date: Mon, 15 Dec 2025 13:45:17 +0100 [thread overview]
Message-ID: <6223429.lOV4Wx5bFT@rafael.j.wysocki> (raw)
Hi All,
This is a resend of
https://lore.kernel.org/linux-acpi/2395536.ElGaqSPkdT@rafael.j.wysocki/
which was sent in the middle of the merge window.
I have added R-bys from Armin to both patches, but otherwise there are no
changes, so the version is still 1. I'd appreciate feedback, but if there's
none, I'll be queuing up these patches for 6.20.
The description below still applies.
Patch [1/2] updates the registration of PCI root bus wakeup notification setup
in order to simplify code in pci_acpi_wake_bus() and to prepare for the other
change. This is not expected to affect functionality.
Patch [2/2] modifies the ACPI PM notifier registration to add wakeup sources
under devices that are going to be affected by wakeup handling instead of
registering them under ACPI companions of those devices (rationale explained
in the patch changelog). This will change the sysfs layout (wakeup source
devices associated with PCI wakeup are now going to appear under PCI devices
and the host bridge device), but it is not expected to affect user space
adversely.
Thanks!
next reply other threads:[~2025-12-15 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 12:45 Rafael J. Wysocki [this message]
2025-12-15 12:48 ` [RESEND][PATCH v1 1/2] ACPI: PCI: PM: Rework root bus notification setup Rafael J. Wysocki
2025-12-15 12:49 ` [RESEND][PATCH v1 2/2] ACPI: PM: Register wakeup sources under physical devices Rafael J. Wysocki
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=6223429.lOV4Wx5bFT@rafael.j.wysocki \
--to=rafael@kernel.org \
--cc=helgaas@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=w_armin@gmx.de \
/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