public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <superm1@kernel.org>
To: Sumit Gupta <sumitg@nvidia.com>,
	rafael@kernel.org, viresh.kumar@linaro.org, lenb@kernel.org,
	pierre.gondois@arm.com, zhenglifeng1@huawei.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: Mon, 27 Apr 2026 10:37:04 -0500	[thread overview]
Message-ID: <703848b6-d56b-4c2e-b92c-0ba982477b33@kernel.org> (raw)
In-Reply-To: <20260427051823.280419-2-sumitg@nvidia.com>



On 4/27/26 00:18, 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>
Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>
> ---
>   drivers/acpi/cppc_acpi.c | 24 ++++++++++++++++++------
>   include/acpi/cppc_acpi.h |  8 ++++++--
>   2 files changed, 24 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/acpi/cppc_acpi.c b/drivers/acpi/cppc_acpi.c
> index 2e91c5a97761..a1c91ce20cc8 100644
> --- a/drivers/acpi/cppc_acpi.c
> +++ b/drivers/acpi/cppc_acpi.c
> @@ -134,7 +134,7 @@ static DEFINE_PER_CPU(struct cpc_desc *, cpc_desc_ptr);
>    * cpc_regs[] with the corresponding index. 0 means mandatory and 1
>    * means optional.
>    */
> -#define REG_OPTIONAL (0x1FC7D0)
> +#define REG_OPTIONAL (0x7FC7D0)
>   
>   /*
>    * Use the index of the register in per-cpu cpc_regs[] to check if
> @@ -751,18 +751,19 @@ int acpi_cppc_processor_probe(struct acpi_processor *pr)
>   	/*
>   	 * Disregard _CPC if the number of entries in the return package is not
>   	 * as expected, but support future revisions being proper supersets of
> -	 * the v3 and only causing more entries to be returned by _CPC.
> +	 * the v4 and only causing more entries to be returned by _CPC.
>   	 */
>   	if ((cpc_rev == CPPC_V2_REV && num_ent != CPPC_V2_NUM_ENT) ||
>   	    (cpc_rev == CPPC_V3_REV && num_ent != CPPC_V3_NUM_ENT) ||
> -	    (cpc_rev > CPPC_V3_REV && num_ent <= CPPC_V3_NUM_ENT)) {
> +	    (cpc_rev == CPPC_V4_REV && num_ent != CPPC_V4_NUM_ENT) ||
> +	    (cpc_rev > CPPC_V4_REV && num_ent <= CPPC_V4_NUM_ENT)) {
>   		pr_debug("Unexpected number of _CPC return package entries (%d) for CPU:%d\n",
>   			 num_ent, pr->id);
>   		goto out_free;
>   	}
> -	if (cpc_rev > CPPC_V3_REV) {
> -		num_ent = CPPC_V3_NUM_ENT;
> -		cpc_rev = CPPC_V3_REV;
> +	if (cpc_rev > CPPC_V4_REV) {
> +		num_ent = CPPC_V4_NUM_ENT;
> +		cpc_rev = CPPC_V4_REV;
>   	}
>   
>   	cpc_ptr->num_entries = num_ent;
> @@ -845,6 +846,17 @@ int acpi_cppc_processor_probe(struct acpi_processor *pr)
>   
>   			cpc_ptr->cpc_regs[i-2].type = ACPI_TYPE_BUFFER;
>   			memcpy(&cpc_ptr->cpc_regs[i-2].cpc_entry.reg, gas_t, sizeof(*gas_t));
> +		} else if (cpc_obj->type == ACPI_TYPE_PACKAGE) {
> +			/*
> +			 * ACPI 6.6, s8.4.6.1.2.7 defines Resource Priority
> +			 * as a Package of Resource Priority Register Descriptor
> +			 * sub-packages.  Parsing the full structure is not yet
> +			 * supported; mark the register as unsupported for now.
> +			 */
> +			pr_debug("CPU:%d entry %d: package type not supported\n",
> +				 pr->id, i);
> +			cpc_ptr->cpc_regs[i-2].type = ACPI_TYPE_INTEGER;
> +			cpc_ptr->cpc_regs[i-2].cpc_entry.int_value = 0;
>   		} else {
>   			pr_debug("Invalid entry type (%d) in _CPC for CPU:%d\n",
>   				 i, pr->id);
> diff --git a/include/acpi/cppc_acpi.h b/include/acpi/cppc_acpi.h
> index d1f02ceec4f9..8693890a7275 100644
> --- a/include/acpi/cppc_acpi.h
> +++ b/include/acpi/cppc_acpi.h
> @@ -17,16 +17,18 @@
>   #include <acpi/pcc.h>
>   #include <acpi/processor.h>
>   
> -/* CPPCv2 and CPPCv3 support */
> +/* CPPCv2, CPPCv3 and CPPCv4 support */
>   #define CPPC_V2_REV	2
>   #define CPPC_V3_REV	3
> +#define CPPC_V4_REV	4
>   #define CPPC_V2_NUM_ENT	21
>   #define CPPC_V3_NUM_ENT	23
> +#define CPPC_V4_NUM_ENT	25
>   
>   #define PCC_CMD_COMPLETE_MASK	(1 << 0)
>   #define PCC_ERROR_MASK		(1 << 2)
>   
> -#define MAX_CPC_REG_ENT 21
> +#define MAX_CPC_REG_ENT 23
>   
>   /* CPPC specific PCC commands. */
>   #define	CMD_READ 0
> @@ -109,6 +111,8 @@ enum cppc_regs {
>   	REFERENCE_PERF,
>   	LOWEST_FREQ,
>   	NOMINAL_FREQ,
> +	OSPM_NOMINAL_PERF,
> +	RESOURCE_PRIORITY,
>   };
>   
>   /*


  parent reply	other threads:[~2026-04-27 15:37 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
2026-04-27 15:37   ` Mario Limonciello [this message]
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=703848b6-d56b-4c2e-b92c-0ba982477b33@kernel.org \
    --to=superm1@kernel.org \
    --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=pierre.gondois@arm.com \
    --cc=rafael@kernel.org \
    --cc=saket.dumbre@intel.com \
    --cc=sanjayc@nvidia.com \
    --cc=sumitg@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