From: Sumit Gupta <sumitg@nvidia.com>
To: Mario Limonciello <mario.limonciello@amd.com>,
"zhenglifeng (A)" <zhenglifeng1@huawei.com>,
rafael@kernel.org, viresh.kumar@linaro.org, lenb@kernel.org,
pierre.gondois@arm.com, zhanjie9@hisilicon.com,
saket.dumbre@intel.com, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
acpica-devel@lists.linux.dev
Cc: treding@nvidia.com, jonathanh@nvidia.com, vsethi@nvidia.com,
ksitaraman@nvidia.com, sanjayc@nvidia.com, bbasu@nvidia.com
Subject: Re: [PATCH 1/2] ACPI: CPPC: Add support for CPPC v4
Date: Tue, 28 Apr 2026 18:23:45 +0530 [thread overview]
Message-ID: <826bd942-4e6b-4e4d-9292-04b5614aa91a@nvidia.com> (raw)
In-Reply-To: <d76e7f9d-f418-457a-b08f-90f929bfe71b@amd.com>
On 27/04/26 21:03, Mario Limonciello wrote:
> External email: Use caution opening links or attachments
>
>
> On 4/27/26 03:04, Sumit Gupta wrote:
>>
>> On 27/04/26 12:36, zhenglifeng (A) wrote:
>>> External email: Use caution opening links or attachments
>>>
>>>
>>> It seems that mario has sent a similar patch:
>>>
>>> https://lore.kernel.org/all/20260427035520.1427080-3-superm1@kernel.org/
>>>
>>
>>
>> Thank you for sharing.
>> Yes, both look similar with below two change.
>> 1. REG_OPTIONAL needs the 0x1FC7D0 -> 0x7FC7D0 update to mark
>> the two new registers optional. This is present in my [PATCH 1/2].
>> 2. For Resource Priority, pkg_data added to cpc_entry.
>> This is present in Mario's [PATCH 2/6].
>>
>>
>> Hi Mario,
>> How would you like to proceed? A few options:
>> (a) Let both CPPCv4 patches from this series go separately.
>> (b) Fold the REG_OPTIONAL update from my patch 1/2 into your
>> patch, and pull my patch 2/2 into your series.
>> (c) Anything else you'd prefer.
>> Either way works for me.
>>
>> Thank you,
>> Sumit Gupta
>>
>
>
> Reviewing yours points out that I totally missed updating REG_OPTIONAL
> with the two new ACPI 6.7 fields being optional too.
>
> In my series I only add in CPPv4 so I can build on top of the changes
> for CPPCv5.
>
> So - I would say we should let your patches merge for v4 and I'll drop
> the relevant ones from my series and rebase mine on top of your work.
>
Thanks Mario.
I will proceed with this series and add your Reviewed-by to this patch
in v2.
Thank you,
Sumit Gupta
>
>>
>>>
>>> On 4/27/2026 1:18 PM, Sumit Gupta wrote:
>>>> CPPC v4 (ACPI 6.6, Section 8.4.6) adds two optional entries to the
>>>> _CPC package:
>>>>
>>>> 1. OSPM Nominal Performance (8.4.6.1.2.6): A write-only register that
>>>> lets OSPM inform the platform what it considers nominal
>>>> performance.
>>>> The platform classifies performance above this level as boost and
>>>> below as throttle for its power/thermal decisions.
>>>>
>>>> 2. Resource Priority (8.4.6.1.2.7): A Package of Resource Priority
>>>> Register Descriptor sub-packages that allow OSPM to set relative
>>>> priority among processors for shared resources (boost, throttle,
>>>> L2/L3 cache, memory bandwidth). Parsing the full structure is not
>>>> yet supported; such entries are marked as unsupported.
>>>>
>>>> Add v4 _CPC table parsing (25 entries) and update REG_OPTIONAL to
>>>> mark the two new registers as optional.
>>>>
>>>> Signed-off-by: Sumit Gupta <sumitg@nvidia.com>
>>>> ---
....
next prev parent reply other threads:[~2026-04-28 12:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 5:18 [PATCH 0/2] ACPI: CPPC: Add CPPC v4 support (ACPI 6.6) Sumit Gupta
2026-04-27 5:18 ` [PATCH 1/2] ACPI: CPPC: Add support for CPPC v4 Sumit Gupta
2026-04-27 7:06 ` zhenglifeng (A)
2026-04-27 8:04 ` Sumit Gupta
2026-04-27 15:33 ` Mario Limonciello
2026-04-28 12:53 ` Sumit Gupta [this message]
2026-04-27 15:37 ` Mario Limonciello
2026-04-27 5:18 ` [PATCH 2/2] ACPI: CPPC: Add ospm_nominal_perf support Sumit Gupta
2026-04-27 15:36 ` Mario Limonciello
2026-04-28 12:55 ` Sumit Gupta
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=826bd942-4e6b-4e4d-9292-04b5614aa91a@nvidia.com \
--to=sumitg@nvidia.com \
--cc=acpica-devel@lists.linux.dev \
--cc=bbasu@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=ksitaraman@nvidia.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=pierre.gondois@arm.com \
--cc=rafael@kernel.org \
--cc=saket.dumbre@intel.com \
--cc=sanjayc@nvidia.com \
--cc=treding@nvidia.com \
--cc=viresh.kumar@linaro.org \
--cc=vsethi@nvidia.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