From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: "Kurt Borja" <kuurtb@gmail.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Hans de Goede" <hansg@kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
"Mario Limonciello" <mario.limonciello@amd.com>
Cc: sre@kernel.org, bryan.odonoghue@linaro.org,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
stephan.gerhold@linaro.org
Subject: Re: [RFC PATCH] platform/arm64: lenovo-thinkpad-t14s: Adjust thermal trip with platform profile
Date: Thu, 15 Oct 2026 09:10:49 +0200 [thread overview]
Message-ID: <0ca8681e-8402-4540-8635-9a98140b8243@oss.qualcomm.com> (raw)
In-Reply-To: <DM55HM3TYCHT.1F7FX19ORJPG@gmail.com>
On 10/15/26 07:08, Kurt Borja wrote:
> On Wed Oct 14, 2026 at 10:03 AM -03, Daniel Lezcano wrote:
[ ... ]
>> Yes but I have a series I'm about to send decoupling the
>> platform_profile from ACPI
>
> The platform-profile already has a platform agnostic interface at
> /sys/class/platform-profile-N. Unless I'm missing something, I believe
> that interface should already cover your use case and its also the
> recommended way to expose interfaces to user-space.
>
> I was not around here when this functionality was exposed to
> /sys/firmware/acpi so I don't really know the context, but I personally
> don't see a reason to duplicate this at /sys/firmware/devicetree or
> something like that.
Yes, I agree, thanks for pointing this out.
The platform_profile is however tied with ACPI because if acpi_disabled
is set then platform profile is not usable. It uses also a acpi_kobj.
The aforementioned series [1] decouples both so it can be used on any
platform.
[1]
https://lore.kernel.org/all/20261014132500.3817549-1-daniel.lezcano@oss.qualcomm.com/
prev parent reply other threads:[~2026-10-15 7:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 18:19 Daniel Lezcano
2026-10-14 10:19 ` Ilpo Järvinen
2026-10-14 12:46 ` Hans de Goede
2026-10-14 13:03 ` Daniel Lezcano
2026-10-14 13:10 ` Hans de Goede
2026-10-15 5:08 ` Kurt Borja
2026-10-15 7:10 ` Daniel Lezcano [this message]
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=0ca8681e-8402-4540-8635-9a98140b8243@oss.qualcomm.com \
--to=daniel.lezcano@oss.qualcomm.com \
--cc=bryan.odonoghue@linaro.org \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kuurtb@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=sre@kernel.org \
--cc=stephan.gerhold@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®