The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Sumit Gupta <sumitg@nvidia.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: viresh.kumar@linaro.org, pierre.gondois@arm.com,
	zhenglifeng1@huawei.com, ionela.voinescu@arm.com,
	lenb@kernel.org, robert.moore@intel.com, corbet@lwn.net,
	rdunlap@infradead.org, ray.huang@amd.com, gautham.shenoy@amd.com,
	mario.limonciello@amd.com, perry.yuan@amd.com,
	zhanjie9@hisilicon.com, yumpusamongus@gmail.com,
	dedekind1@gmail.com, linux-pm@vger.kernel.org,
	linux-acpi@vger.kernel.org, linux-doc@vger.kernel.org,
	acpica-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-tegra@vger.kernel.org, treding@nvidia.com,
	jonathanh@nvidia.com, vsethi@nvidia.com, ksitaraman@nvidia.com,
	sanjayc@nvidia.com, nhartman@nvidia.com, mochs@nvidia.com,
	bbasu@nvidia.com, sumitg@nvidia.com
Subject: Re: [PATCH v8 0/7] Enhanced autonomous selection and improvements
Date: Tue, 3 Mar 2026 23:02:30 +0530	[thread overview]
Message-ID: <48bdf87e-39f1-402f-a7dc-1a0e1e7a819d@nvidia.com> (raw)
In-Reply-To: <CAJZ5v0iOsqoZx0EZ3AqEk_8mrGxSj6wj-m8phRJ0cT71NTuBWA@mail.gmail.com>


On 28/02/26 02:06, Rafael J. Wysocki wrote:
> External email: Use caution opening links or attachments
>
>
> On Thu, Feb 26, 2026 at 2:59 PM Sumit Gupta <sumitg@nvidia.com> wrote:
>>
>>> This patch series improves the CPPC cpufreq driver with new ACPI APIs
>>> and enhancements for Autonomous Selection (auto_select).
>>>
>>> CPPC auto_select enables hardware-driven CPU performance scaling using
>>> Energy Performance Preference (EPP) hints. Currently, there's limited
>>> runtime control and visibility into CPPC performance registers.
>>>
>>> The series adds cppc_get_perf() API to read performance controls, updates
>>> MIN_PERF/MAX_PERF in target callbacks using existing scaling_min/max_freq
>>> interface similar to intel_cpufreq HWP handling, and exposes perf_limited
>>> register via sysfs to detect throttling events.
>>>
>>> The patches are grouped as below:
>>> - Patch 1: Add cppc_get_perf() API (independent).
>>> - Patch 2: Warn on missing mandatory DESIRED_PERF (independent).
>>> - Patch 3: Extend cppc_set_epp_perf for FFH/SystemMemory (independent).
>>> - Patch 4: Update cached perf_ctrls on sysfs write (independent).
>>> - Patch 5: Update MIN_PERF/MAX_PERF in target callbacks (depends on 4).
>>> - Patch 6-7: APIs, sysfs and doc for perf_limited (independent).
>> Gentle ping.
>>
>> If there are no further comments, could this be considered for merging.
> Applied as 7.1 material, thanks!

Thank you for applying the series.

>
> That said, wouldn't it be prudent to check cpc_read() return values 
> everywhere? They are handled quite inconsistently and this series 
> doesn't improve that. 

I will send a follow-up patch to address this.

Thank you
Sumit Gupta



      reply	other threads:[~2026-03-03 17:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-06 14:26 [PATCH v8 0/7] Enhanced autonomous selection and improvements Sumit Gupta
2026-02-06 14:26 ` [PATCH v8 1/7] ACPI: CPPC: Add cppc_get_perf() API to read performance controls Sumit Gupta
2026-02-06 14:26 ` [PATCH v8 2/7] ACPI: CPPC: Warn on missing mandatory DESIRED_PERF register Sumit Gupta
2026-02-06 14:26 ` [PATCH v8 3/7] ACPI: CPPC: Extend cppc_set_epp_perf() for FFH/SystemMemory Sumit Gupta
2026-02-06 14:26 ` [PATCH v8 4/7] cpufreq: CPPC: Update cached perf_ctrls on sysfs write Sumit Gupta
2026-02-06 14:26 ` [PATCH v8 5/7] cpufreq: cppc: Update MIN_PERF/MAX_PERF in target callbacks Sumit Gupta
2026-02-06 14:26 ` [PATCH v8 6/7] ACPI: CPPC: add APIs and sysfs interface for perf_limited Sumit Gupta
2026-02-06 14:26 ` [PATCH v8 7/7] cpufreq: CPPC: Add sysfs documentation " Sumit Gupta
2026-02-26 13:59 ` [PATCH v8 0/7] Enhanced autonomous selection and improvements Sumit Gupta
2026-02-27 20:36   ` Rafael J. Wysocki
2026-03-03 17:32     ` Sumit Gupta [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=48bdf87e-39f1-402f-a7dc-1a0e1e7a819d@nvidia.com \
    --to=sumitg@nvidia.com \
    --cc=acpica-devel@lists.linux.dev \
    --cc=bbasu@nvidia.com \
    --cc=corbet@lwn.net \
    --cc=dedekind1@gmail.com \
    --cc=gautham.shenoy@amd.com \
    --cc=ionela.voinescu@arm.com \
    --cc=jonathanh@nvidia.com \
    --cc=ksitaraman@nvidia.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=linux-tegra@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=mochs@nvidia.com \
    --cc=nhartman@nvidia.com \
    --cc=perry.yuan@amd.com \
    --cc=pierre.gondois@arm.com \
    --cc=rafael@kernel.org \
    --cc=ray.huang@amd.com \
    --cc=rdunlap@infradead.org \
    --cc=robert.moore@intel.com \
    --cc=sanjayc@nvidia.com \
    --cc=treding@nvidia.com \
    --cc=viresh.kumar@linaro.org \
    --cc=vsethi@nvidia.com \
    --cc=yumpusamongus@gmail.com \
    --cc=zhanjie9@hisilicon.com \
    --cc=zhenglifeng1@huawei.com \
    /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