linux-kernel - [PATCH v1 0/4] ACPI: scan: Handle generic system devices directly

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: <7888874.EvYhyI6sBW@rafael.j.wysocki>
Date: Mon, 15 Dec 2025 14:31:53 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Linux ACPI <linux-acpi@...r.kernel.org>
Cc: LKML <linux-kernel@...r.kernel.org>, Bjorn Helgaas <helgaas@...nel.org>,
 Zhang Rui <rui.zhang@...el.com>, Chen Yu <yu.c.chen@...el.com>,
 Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
 Mika Westerberg <mika.westerberg@...ux.intel.com>,
 Linux PCI <linux-pci@...r.kernel.org>, Alex Hung <alexhung@...il.com>,
 Hans de Goede <hansg@...nel.org>,
 Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>,
 platform-driver-x86@...r.kernel.org, AceLan Kao <acelan.kao@...onical.com>
Subject: [PATCH v1 0/4] ACPI: scan: Handle generic system devices directly

Hi All,

As per the changelog of patch [1/4], there is a long-standing problem with ACPI
device enumeration that if the given device has a compatible ID which is one of
the generic system resource device IDs (PNP0C01 and PNP0C02), it will be claimed
by the PNP scan handler and it will not be represented as a platform device, so
it cannot be handled by a platform driver.

Obviously, PNP0C01 and PNP0C02 need to be removed from acpi_pnp_device_ids[] to
address this problem, but it cannot be done without making any other changes
due to the way the legacy PNP system driver works (see the changelog of patch
[1/4] for details) and the approach used in patch [1/4] is to reserve the
"motherboard resources" directly in the ACPI core without creating platform
devices for "system" devices (whose _HID is either PNP0C01 or PNP0C02).  The
new code doing works along the lines of the PNP system driver to avoid
regressions.

The remaining patches in the series are simplifications that can be done on
top of the first one.

Patches [2-3/4] remove platform device creation code from Intel HID and VBTN
drivers that don't need to worry about _CID including PNP0C02 any more.

Patch [4/4] drops acpi_nonpnp_device_ids[] that was added as a workaround for
the issue at hand in the first place.

Thanks!