linux-kernel - [RESEND][PATCH v1 0/2] PCI: ACPI: PM: Rework root bus wakeup notification setup and wakeup source registration

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <6223429.lOV4Wx5bFT@rafael.j.wysocki>
Date: Mon, 15 Dec 2025 13:45:17 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Linux ACPI <linux-acpi@...r.kernel.org>
Cc: Linux PM <linux-pm@...r.kernel.org>,
 Linux PCI <linux-pci@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>,
 Bjorn Helgaas <helgaas@...nel.org>, Armin Wolf <w_armin@....de>
Subject:
 [RESEND][PATCH v1 0/2] PCI: ACPI: PM: Rework root bus wakeup notification
 setup and wakeup source registration

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!