X86 platform drivers
 help / color / mirror / Atom feed
From: "David E. Box" <david.e.box@linux.intel.com>
To: george.d.sworo@intel.com, david.e.box@intel.com
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] platform/x86/intel: pmc: Support Intel Raptorlake P
Date: Wed, 01 Jun 2022 18:36:43 -0700	[thread overview]
Message-ID: <e66d266554132a94d2290edba52039ad257b7add.camel@linux.intel.com> (raw)
In-Reply-To: <20220602012617.20100-1-george.d.sworo@intel.com>

On Wed, 2022-06-01 at 18:26 -0700, george.d.sworo@intel.com wrote:
> From: George D Sworo <george.d.sworo@intel.com>
> 
> Add Raptorlake P to the list of the platforms that intel_pmc_core driver
> supports for pmc_core device. Raptorlake P PCH is based on Alderlake P
> PCH.
> 
> Signed-off-by: George D Sworo <george.d.sworo@intel.com>
> ---
>  drivers/platform/x86/intel/pmc/core.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/platform/x86/intel/pmc/core.c
> b/drivers/platform/x86/intel/pmc/core.c
> index edaf22e5ae98..40183bda7894 100644
> --- a/drivers/platform/x86/intel/pmc/core.c
> +++ b/drivers/platform/x86/intel/pmc/core.c
> @@ -1912,6 +1912,7 @@ static const struct x86_cpu_id intel_pmc_core_ids[] = {
>  	X86_MATCH_INTEL_FAM6_MODEL(ROCKETLAKE,		&tgl_reg_map),
>  	X86_MATCH_INTEL_FAM6_MODEL(ALDERLAKE_L,		&tgl_reg_map),
>  	X86_MATCH_INTEL_FAM6_MODEL(ALDERLAKE,		&adl_reg_map),
> +	X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE_P,        &tgl_reg_map),
>  	{}
>  };
>  

Reviewed-by: David E. Box <david.e.box@linux.intel.com>

Thanks


  reply	other threads:[~2022-06-02  1:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02  1:26 [PATCH] platform/x86/intel: pmc: Support Intel Raptorlake P george.d.sworo
2022-06-02  1:36 ` David E. Box [this message]
2022-06-10 19:13 ` Hans de Goede
  -- strict thread matches above, loose matches on Subject: below --
2022-06-01 23:17 George D Sworo

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=e66d266554132a94d2290edba52039ad257b7add.camel@linux.intel.com \
    --to=david.e.box@linux.intel.com \
    --cc=david.e.box@intel.com \
    --cc=george.d.sworo@intel.com \
    --cc=platform-driver-x86@vger.kernel.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