From: Zhang Rui <rui.zhang@intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: Linux PM <linux-pm@vger.kernel.org>,
George D Sworo <george.d.sworo@intel.com>
Subject: Re: [PATCH] powercap: intel_rapl: Add support for RAPTORLAKE_P
Date: Fri, 10 Jun 2022 10:26:58 +0800 [thread overview]
Message-ID: <13a8ee34a67ec8a59e926c91894365e8d512d260.camel@intel.com> (raw)
In-Reply-To: <CAJZ5v0j8kahM+=VDg0Dj3mZjhw9W+cq6y-TU0M3QF4mNxYn-bQ@mail.gmail.com>
On Thu, 2022-06-09 at 20:55 +0200, Rafael J. Wysocki wrote:
> Rui, Srinivas, should I take this one?
Sorry that I missed this one.
George,
Have this patch been tested yet?
I have the same patch internally, it should work but I haven't got
chance to test it yet.
thanks,
rui
>
> On Wed, Jun 1, 2022 at 9:22 PM <george.d.sworo@intel.com> wrote:
> >
> > From: George D Sworo <george.d.sworo@intel.com>
> >
> > Add RAPTORLAKE_P to the list of supported processor model in the
> > Intel
> >
> > RAPL power capping driver.
> >
> > Signed-off-by: George D Sworo <george.d.sworo@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 a9c99d9e8b42..21d624f9f5fb 100644
> > --- a/drivers/powercap/intel_rapl_common.c
> > +++ b/drivers/powercap/intel_rapl_common.c
> > @@ -1109,6 +1109,7 @@ static const struct x86_cpu_id rapl_ids[]
> > __initconst = {
> > X86_MATCH_INTEL_FAM6_MODEL(ALDERLAKE_L, &rapl_defau
> > lts_core),
> > X86_MATCH_INTEL_FAM6_MODEL(ALDERLAKE_N, &rapl_defau
> > lts_core),
> > X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE, &rapl_defau
> > lts_core),
> > + X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE_P, &rapl_defau
> > lts_core),
> > X86_MATCH_INTEL_FAM6_MODEL(SAPPHIRERAPIDS_X, &rapl_defau
> > lts_spr_server),
> > X86_MATCH_INTEL_FAM6_MODEL(LAKEFIELD, &rapl_defau
> > lts_core),
> >
> > --
> > 2.17.1
> >
next prev parent reply other threads:[~2022-06-10 2:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 19:22 [PATCH] powercap: intel_rapl: Add support for RAPTORLAKE_P george.d.sworo
2022-06-09 18:55 ` Rafael J. Wysocki
2022-06-09 21:02 ` srinivas pandruvada
2022-06-09 21:47 ` Sworo, George D
2022-06-09 22:10 ` srinivas pandruvada
2022-06-10 2:26 ` Zhang Rui [this message]
2022-06-10 2:32 ` Zhang Rui
2022-06-10 3:31 ` Sworo, George D
2022-06-21 14:49 ` Pawnikar, Sumeet R
2022-06-21 19:22 ` Sworo, George D
2022-07-05 19:01 ` 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=13a8ee34a67ec8a59e926c91894365e8d512d260.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=george.d.sworo@intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=srinivas.pandruvada@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.