From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: rafael@kernel.org, "Len Brown" <lenb@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Maximilian Luz" <luzmaximilian@gmail.com>,
"Shyam Sundar S K" <Shyam-sundar.S-k@amd.com>,
"Mark Pearson" <mpearson-lenovo@squebb.ca>,
"Derek J. Clark" <derekjohn.clark@gmail.com>,
"Daniel Lezcano" <daniel.lezcano@kernel.org>,
"Zhang Rui" <rui.zhang@intel.com>,
"Lukasz Luba" <lukasz.luba@arm.com>,
"Armin Wolf" <W_Armin@gmx.de>,
"Jai Luthra" <jai.luthra@ideasonboard.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jack Wu" <jackbb_wu@compal.com>,
"Mario Limonciello (AMD)" <superm1@kernel.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-pm@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v3 1/4] platform profile: Extract the core from ACPI
Date: Tue, 17 Nov 2026 17:03:05 +0100 [thread overview]
Message-ID: <0de1444a-a0ba-4e16-a480-74a39c865ab6@oss.qualcomm.com> (raw)
In-Reply-To: <CAMuHMdXJOpcC3a6wMXF_m=uNjuqSO1Z3kyM7Az1uP_2GBurOvA@mail.gmail.com>
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@oss.qualcomm.com> 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@oss.qualcomm.com>
>
> 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
next prev parent reply other threads:[~2026-11-17 16:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-24 22:34 [PATCH v3 0/4] Make platform profiles firmware independent Daniel Lezcano
2026-10-24 22:34 ` [PATCH v3 1/4] platform profile: Extract the core from ACPI Daniel Lezcano
2026-11-17 11:48 ` Geert Uytterhoeven
2026-11-17 16:03 ` Daniel Lezcano [this message]
2026-11-17 16:38 ` Geert Uytterhoeven
2026-10-24 22:34 ` [PATCH v3 2/4] platform profile: Complete class notifications and registration cleanup Daniel Lezcano
2026-10-24 22:34 ` [PATCH v3 3/4] platform profile: Document firmware-independent profile selection Daniel Lezcano
2026-10-24 22:34 ` [PATCH v3 4/4] platform profile: Make legacy ACPI aggregate interface optional Daniel Lezcano
2026-11-09 16:36 ` [PATCH v3 0/4] Make platform profiles firmware independent Daniel Lezcano
2026-11-09 16:46 ` Rafael J. Wysocki (Intel)
2026-11-09 17:39 ` Mario Limonciello
2026-11-09 19:37 ` Rafael J. Wysocki (Intel)
2026-11-10 0:51 ` Mark Pearson
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=0de1444a-a0ba-4e16-a480-74a39c865ab6@oss.qualcomm.com \
--to=daniel.lezcano@oss.qualcomm.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=W_Armin@gmx.de \
--cc=corbet@lwn.net \
--cc=daniel.lezcano@kernel.org \
--cc=derekjohn.clark@gmail.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jackbb_wu@compal.com \
--cc=jai.luthra@ideasonboard.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=luzmaximilian@gmail.com \
--cc=mpearson-lenovo@squebb.ca \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rui.zhang@intel.com \
--cc=skhan@linuxfoundation.org \
--cc=superm1@kernel.org \
--cc=viresh.kumar@linaro.org \
/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
all inboxes | Powered by JetHome®