From: Zhang Rui <rui.zhang@intel.com>
To: rjw@rjwysocki.net
Cc: linux-pm@vger.kernel.org
Subject: Re: [PATCH] powercap: intel_rapl: Add support for RAPTORLAKE_S
Date: Tue, 30 Aug 2022 11:00:48 +0800 [thread overview]
Message-ID: <efe3eb3d0ad53d58ebd1a54cb5b3a27fdaec3487.camel@intel.com> (raw)
In-Reply-To: <20220830030134.8111-1-rui.zhang@intel.com>
Note that this patch depends on commit
ea902bcc1943 ("x86/cpu: Add new Raptor Lake CPU model number") which
was merged in 6.0-rc3.
thanks,
rui
On Tue, 2022-08-30 at 11:01 +0800, Zhang Rui wrote:
> Add intel_rapl support for RAPTORLAKE_S platform, which behaves the
> same
> as RAPTORLAKE and RAPTORLAKE_P platforms.
>
> Signed-off-by: Zhang Rui <rui.zhang@intel.com>
> ---
> drivers/powercap/intel_rapl_common.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/powercap/intel_rapl_common.c
> b/drivers/powercap/intel_rapl_common.c
> index 21d624f9f5fb..6812c1ca3100 100644
> --- a/drivers/powercap/intel_rapl_common.c
> +++ b/drivers/powercap/intel_rapl_common.c
> @@ -1110,6 +1110,7 @@ static const struct x86_cpu_id rapl_ids[]
> __initconst = {
> X86_MATCH_INTEL_FAM6_MODEL(ALDERLAKE_N, &rapl_default
> s_core),
> X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE, &rapl_default
> s_core),
> X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE_P, &rapl_defaults_
> core),
> + X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE_S, &rapl_defaults_core),
> X86_MATCH_INTEL_FAM6_MODEL(SAPPHIRERAPIDS_X, &rapl_default
> s_spr_server),
> X86_MATCH_INTEL_FAM6_MODEL(LAKEFIELD, &rapl_default
> s_core),
>
next prev parent reply other threads:[~2022-08-30 3:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 3:01 [PATCH] powercap: intel_rapl: Add support for RAPTORLAKE_S Zhang Rui
2022-08-30 3:00 ` Zhang Rui [this message]
2022-09-03 18:22 ` 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=efe3eb3d0ad53d58ebd1a54cb5b3a27fdaec3487.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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