Re: [PATCH v3 1/4] platform profile: Extract the core from ACPI
From: Daniel Lezcano
Date: Tue Nov 17 2026 - 11:03:39 EST
Hi Geert,
On 11/17/26 12:48, Geert Uytterhoeven wrote:
Hi Daniel,
On Sun, 25 Oct 2026 at 00:56, Daniel Lezcano
<daniel.lezcano@xxxxxxxxxxxxxxxx> wrote:
Platform profile providers already use device-based callbacks and do not
need ACPI types. The core is nevertheless confined to the ACPI build and
refuses to initialize when ACPI is disabled.
Move the implementation to drivers/platform/profile and introduce the
firmware-independent PLATFORM_PROFILE symbol. Update all provider
selectors. Keep provider-specific ACPI dependencies and the
platform_profile module name.
Isolate access to the legacy ACPI kobject in an optional compatibility
object linked into the same module. Retain the legacy ABI on active ACPI
systems, and initialize the class even when ACPI is absent or disabled.
Use subsys_initcall_sync so the class is ready before built-in thermal
and CPUFreq providers, but after ACPI has initialized its compatibility
kobject.
Signed-off-by: Daniel Lezcano <daniel.lezcano@xxxxxxxxxxxxxxxx>
Thanks for your patch, which is now commit 699041135f75b13a
("platform profile: Extract the core from ACPI") in pm/linux-next/
--- a/drivers/platform/Kconfig
+++ b/drivers/platform/Kconfig
@@ -1,4 +1,20 @@
# SPDX-License-Identifier: GPL-2.0-only
+config PLATFORM_PROFILE
+ tristate "Platform profile support"
I guess this can be invisible (perhaps "... if COMPILE_TEST"?), as
you have updated all provider selectors?
If not, I guess this needs a "depend on X86 || COMPILE_TEST", so people
configuring kernels for different architectures do not see this option?
The goal of this series is to make the platform profile firmware agnostic so it is available for all architectures