From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Zhenguo Yao <yaozhenguo1@gmail.com>
Cc: lenb@kernel.org, viresh.kumar@linaro.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
yaozhenguo@jd.com
Subject: Re: [PATCH] cpufreq: intel_pstate: Add Emerald Rapids support in no-HWP mode
Date: Tue, 19 Dec 2023 15:33:32 -0500 [thread overview]
Message-ID: <9adc18c94f160cad550e762571a952baa7f8df36.camel@linux.intel.com> (raw)
In-Reply-To: <CAJZ5v0i4DAtzoJUyN0H-4rL=HR=cNntqrrJaDj12suF=7JiyeQ@mail.gmail.com>
On Tue, 2023-12-19 at 21:22 +0100, Rafael J. Wysocki wrote:
> On Wed, Dec 13, 2023 at 11:28 AM Zhenguo Yao <yaozhenguo1@gmail.com>
> wrote:
> >
> > Users may disable HWP in firmware, in which case intel_pstate
> > wouldn't load
> > unless the CPU model is explicitly supported.
> >
> > See also the following past commits:
> >
> > commit df51f287b5de ("cpufreq: intel_pstate: Add Sapphire Rapids
> > support
> > in no-HWP mode")
> > commit d8de7a44e11f ("cpufreq: intel_pstate: Add Skylake servers
> > support")
> > commit 706c5328851d ("cpufreq: intel_pstate: Add Cometlake support
> > in
> > no-HWP mode")
> > commit fbdc21e9b038 ("cpufreq: intel_pstate: Add Icelake servers
> > support in
> > no-HWP mode")
> > commit 71bb5c82aaae ("cpufreq: intel_pstate: Add Tigerlake support
> > in
> > no-HWP mode")
> >
> > Signed-off-by: Zhenguo Yao <yaozhenguo1@gmail.com>
>
> Srinivas, any objections?
No.
Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
>
> > ---
> > drivers/cpufreq/intel_pstate.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/cpufreq/intel_pstate.c
> > b/drivers/cpufreq/intel_pstate.c
> > index a534a1f7f1ee..39e0a2cf7236 100644
> > --- a/drivers/cpufreq/intel_pstate.c
> > +++ b/drivers/cpufreq/intel_pstate.c
> > @@ -2406,6 +2406,7 @@ static const struct x86_cpu_id
> > intel_pstate_cpu_ids[] = {
> > X86_MATCH(ICELAKE_X, core_funcs),
> > X86_MATCH(TIGERLAKE, core_funcs),
> > X86_MATCH(SAPPHIRERAPIDS_X, core_funcs),
> > + X86_MATCH(EMERALDRAPIDS_X, core_funcs),
> > {}
> > };
> > MODULE_DEVICE_TABLE(x86cpu, intel_pstate_cpu_ids);
> > --
> > 2.39.3
> >
next prev parent reply other threads:[~2023-12-19 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 10:28 Zhenguo Yao
2023-12-19 20:22 ` Rafael J. Wysocki
2023-12-19 20:33 ` srinivas pandruvada [this message]
2023-12-19 20:39 ` 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=9adc18c94f160cad550e762571a952baa7f8df36.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=yaozhenguo1@gmail.com \
--cc=yaozhenguo@jd.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
all inboxes | Powered by JetHome®