Re: [PATCH v3 1/4] platform profile: Extract the core from ACPI

From: Rafael J. Wysocki (Intel)

Date: Tue Nov 17 2026 - 15:22:56 EST


On Tue, Nov 17, 2026 at 7:27 PM Daniel Lezcano
<daniel.lezcano@xxxxxxxxxxxxxxxx> wrote:
>
>
>
> Le mar. 17 nov. 2026, 17:39, Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> a écrit :
>>
>> Hi Daniel,
>>
>> On Tue, 17 Nov 2026 at 17:03, Daniel Lezcano
>> <daniel.lezcano@xxxxxxxxxxxxxxxx> wrote:
>> > On 11/17/26 12:48, Geert Uytterhoeven wrote:
>> > > 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
>>
>> Sure... Are there any users of it on these architectures?
>
>
> ARM64 is about to (patches are cooked)

Geert has a point though. There are arches that don't need to see this at all.

You can add ARM64 to the list while adding support for this to it.

> Others IDK

Well, exactly.