Linux Power Management development
 help / color / mirror / Atom feed
From: Henry Tseng <henrytseng@qnap.com>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Len Brown <lenb@kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>
Cc: linux-pm@vger.kernel.org, SW Chen <swchen@qnap.com>,
	Kevin Ko <kevinko@qnap.com>, Henry Tseng <henrytseng@qnap.com>
Subject: [PATCH v2 0/2] cpufreq: intel_pstate: Add scaling factor for Bartlett Lake P-core only SKUs
Date: Fri,  8 May 2026 14:30:30 +0800	[thread overview]
Message-ID: <20260508063032.3248602-1-henrytseng@qnap.com> (raw)

On Bartlett Lake P-core only SKUs (e.g. Intel Core 9 273PE),
cpuinfo_max_freq is reported as 7.0/7.3 GHz, exceeding the datasheet
Max Turbo Frequency of 5.7 GHz.  Root cause: hwp_get_cpu_scaling()
returns 100000 (default core scaling) instead of the correct factor
78741.

Patch 1 fixes a framework regression introduced by 9b18d536b124,
where the registered hybrid_scaling_factor is bypassed for
table-registered models not reporting X86_FEATURE_HYBRID_CPU.
Patch 1 must apply before patch 2; the Bartlett Lake entry alone has
no effect on these SKUs without the framework fix.

Patch 2 adds Bartlett Lake to intel_hybrid_scaling_factor[] with
HYBRID_SCALING_FACTOR_ADL.

---
v2:
  - Reuse intel_hybrid_scaling_factor[] with HYBRID_SCALING_FACTOR_ADL
    instead of introducing a new intel_cppc_scaling_ids[] table and
    computing the scaling factor via CPPC at runtime.
  - Split into two patches: framework fix + Bartlett Lake entry.
v1:
  - https://lore.kernel.org/linux-pm/20260506095157.1591221-1-henrytseng@qnap.com/

Henry Tseng (2):
  cpufreq: intel_pstate: Fix scaling for hybrid-capable CPUs not
    reporting hybrid
  cpufreq: intel_pstate: Use HYBRID_SCALING_FACTOR_ADL for Bartlett Lake

 drivers/cpufreq/intel_pstate.c | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

-- 
2.43.0


             reply	other threads:[~2026-05-08  6:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-08  6:30 Henry Tseng [this message]
2026-05-08  6:30 ` [PATCH v2 1/2] cpufreq: intel_pstate: Fix scaling for hybrid-capable CPUs not reporting hybrid Henry Tseng
2026-05-10 14:34   ` srinivas pandruvada
2026-05-08  6:30 ` [PATCH v2 2/2] cpufreq: intel_pstate: Use HYBRID_SCALING_FACTOR_ADL for Bartlett Lake Henry Tseng

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=20260508063032.3248602-1-henrytseng@qnap.com \
    --to=henrytseng@qnap.com \
    --cc=kevinko@qnap.com \
    --cc=lenb@kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=srinivas.pandruvada@linux.intel.com \
    --cc=swchen@qnap.com \
    --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