From: Sumit Gupta <sumitg@nvidia.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux PM <linux-pm@vger.kernel.org>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
Lukasz Luba <lukasz.luba@arm.com>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Christian Loehle <christian.loehle@arm.com>,
Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
Ricardo Neri <ricardo.neri-calderon@linux.intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Pierre Gondois <Pierre.Gondois@arm.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Armin Wolf <W_Armin@gmx.de>
Subject: Re: [Pre-CfP] LPC2026: Power management and thermal control micro-conference
Date: Fri, 24 Apr 2026 01:41:47 +0530 [thread overview]
Message-ID: <d855d43a-2b07-4e3d-af61-7254ea08527e@nvidia.com> (raw)
In-Reply-To: <CAJZ5v0ge3q5JMm7fdySqLeD+TByhgqDFnp2NNF7ATSeHnBjPiw@mail.gmail.com>
Hi Rafael,
I would like to propose the following topic:
CPPC autonomous mode via a new cpufreq governor -
The ACPI CPPC driver currently enables autonomous performance
level selection via an auto_select sysfs interface, so scaling_governor
no longer reflects what is actually driving frequency.
The proposal is to model autonomous, performance-biased operation
as its own per-policy cpufreq governor, with autonomous state
exposed as read-only in sysfs.
Related upstream discussion:
https://lore.kernel.org/lkml/66f58f43-631b-40a0-8d42-4e90cd24b757@arm.com/
Best regards,
Sumit Gupta
On 23/04/26 01:18, Rafael J. Wysocki wrote:
> External email: Use caution opening links or attachments
>
>
> Hi Everyone,
>
> On Tue, Apr 21, 2026 at 3:47 PM Rafael J. Wysocki <rafael@kernel.org> wrote:
>> Hi Everyone,
>>
>> On Thu, Mar 26, 2026 at 3:35 PM Rafael J. Wysocki <rafael@kernel.org> wrote:
>>> Hi All,
>>>
>>> I'm looking for topic suggestions to be included in the power
>>> management and thermal control micro-conference submission for
>>> LPC2026. The deadline for submitting LPC u-conf proposals is April
>>> 23, so if there are any topics you'd like to be covered, please let me
>>> know within the next 2 weeks.
>> Just a reminder. The submission deadline is on Thursday, so I'm going
>> to send a proposal tomorrow.
>>
>> This is the last call for input.
> The proposal has been submitted, but it is still possible to update
> it, so if you have any additional topic suggestions, please let me
> know.
>
> Thanks, Rafael
>
next prev parent reply other threads:[~2026-04-23 20:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 14:35 [Pre-CfP] LPC2026: Power management and thermal control micro-conference Rafael J. Wysocki
2026-03-26 14:38 ` Rafael J. Wysocki
2026-04-17 15:02 ` Daniel Lezcano
2026-04-17 15:05 ` Daniel Lezcano
2026-04-20 10:22 ` Rafael J. Wysocki
2026-04-20 11:06 ` Daniel Lezcano
2026-04-21 13:47 ` Rafael J. Wysocki
2026-04-21 14:27 ` Lukasz Luba
2026-04-21 15:19 ` Rafael J. Wysocki
2026-04-22 19:48 ` Rafael J. Wysocki
2026-04-23 20:11 ` Sumit Gupta [this message]
2026-04-21 15:05 ` Daniel Lezcano
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=d855d43a-2b07-4e3d-af61-7254ea08527e@nvidia.com \
--to=sumitg@nvidia.com \
--cc=Pierre.Gondois@arm.com \
--cc=W_Armin@gmx.de \
--cc=artem.bityutskiy@linux.intel.com \
--cc=christian.loehle@arm.com \
--cc=daniel.lezcano@kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=morten.rasmussen@arm.com \
--cc=rafael@kernel.org \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=sudeep.holla@arm.com \
--cc=ulf.hansson@linaro.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