From: Henry Tseng <henrytseng@qnap.com>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
rafael@kernel.org, viresh.kumar@linaro.org
Cc: Henry Tseng <henrytseng@qnap.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] cpufreq: intel_pstate: Fix Raptor Lake-E cpufreq limits
Date: Tue, 12 May 2026 17:04:02 +0800 [thread overview]
Message-ID: <20260512090403.2708970-1-henrytseng@qnap.com> (raw)
In-Reply-To: <20260511235328.2018458-1-srinivas.pandruvada@linux.intel.com>
On Mon, 11 May 2026 16:53:28 -0700, Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> wrote:
> Raptor Lake-E processors are not correctly showing cpufreq frequency
> limits.
>
> These CPUs don't set X86_FEATURE_HYBRID_CPU and have no E-cores, but
> P-cores still use hybrid scaling factor.
> ...
Tested on Intel Core 9 273PE (Bartlett Lake P-core only):
cpuinfo_max_freq is now correctly reported as 5.5/5.7 GHz, matching
the datasheet, via the dynamic CPPC compute path.
On another Bartlett Lake P-core only SKU (Intel Core 7 253PE), the
CPPC-computed factor (80645) overshoots the datasheet Max Turbo
Frequency (5.5 GHz) by 100 MHz, matching the CPPC rounding error
described in the commit message.
I'll send a standalone patch adding Bartlett Lake to
intel_hybrid_scaling_factor[] with HYBRID_SCALING_FACTOR_ADL to
address the 253PE residual.
Tested-by: Henry Tseng <henrytseng@qnap.com>
Thanks,
Henry
next prev parent reply other threads:[~2026-05-12 9:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 23:53 [PATCH] cpufreq: intel_pstate: Fix Raptor Lake-E cpufreq limits Srinivas Pandruvada
2026-05-12 9:04 ` Henry Tseng [this message]
2026-05-12 10:20 ` Rafael J. Wysocki
2026-05-12 11:15 ` srinivas pandruvada
2026-05-12 12:37 ` Rafael J. Wysocki
2026-05-12 18:45 ` srinivas pandruvada
2026-05-12 18:54 ` Rafael J. Wysocki
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=20260512090403.2708970-1-henrytseng@qnap.com \
--to=henrytseng@qnap.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=stable@vger.kernel.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