platform-driver-x86.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>, markgross@kernel.org
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: intel-uncore-freq: Add client processors
Date: Thu, 06 Apr 2023 11:12:12 -0700	[thread overview]
Message-ID: <3a5a04091462fc33d4c61da2889fe7ce9bd55d97.camel@linux.intel.com> (raw)
In-Reply-To: <efcdc3fe-de74-0f0d-d9d5-3249fc1d5d53@redhat.com>

Hi Hans,

On Thu, 2023-04-06 at 12:58 +0200, Hans de Goede wrote:
> Hi Srinivas,
> 
> On 3/30/23 16:59, Srinivas Pandruvada wrote:
> > Make Intel uncore frequency driver support to client processor
> > starting
> > from Alder Lake.
> > 
> > Signed-off-by: Srinivas Pandruvada
> > <srinivas.pandruvada@linux.intel.com>
> 
> I assume that this is independent from the
> "[PATCH] platform/x86/intel-uncore-freq: Uncore frequency control via
> TPMI"
> changes ?
> 
Yes this is independent and there is no TPMI dependency.


Thanks,
Srinivas

> (just double checking before I merge this).
> 
> Regards,
> 
> Hans
> 
> 
> 
> > ---
> >  .../platform/x86/intel/uncore-frequency/uncore-frequency.c | 7
> > +++++++
> >  1 file changed, 7 insertions(+)
> > 
> > diff --git a/drivers/platform/x86/intel/uncore-frequency/uncore-
> > frequency.c b/drivers/platform/x86/intel/uncore-frequency/uncore-
> > frequency.c
> > index 00ac7e381441..32e2515ee366 100644
> > --- a/drivers/platform/x86/intel/uncore-frequency/uncore-
> > frequency.c
> > +++ b/drivers/platform/x86/intel/uncore-frequency/uncore-
> > frequency.c
> > @@ -204,6 +204,13 @@ static const struct x86_cpu_id
> > intel_uncore_cpu_ids[] = {
> >         X86_MATCH_INTEL_FAM6_MODEL(ICELAKE_D,   NULL),
> >         X86_MATCH_INTEL_FAM6_MODEL(SAPPHIRERAPIDS_X, NULL),
> >         X86_MATCH_INTEL_FAM6_MODEL(EMERALDRAPIDS_X, NULL),
> > +       X86_MATCH_INTEL_FAM6_MODEL(ALDERLAKE, NULL),
> > +       X86_MATCH_INTEL_FAM6_MODEL(ALDERLAKE_L, NULL),
> > +       X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE, NULL),
> > +       X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE_P, NULL),
> > +       X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE_S, NULL),
> > +       X86_MATCH_INTEL_FAM6_MODEL(METEORLAKE, NULL),
> > +       X86_MATCH_INTEL_FAM6_MODEL(METEORLAKE_L, NULL),
> >         {}
> >  };
> >  MODULE_DEVICE_TABLE(x86cpu, intel_uncore_cpu_ids);
> 


  reply	other threads:[~2023-04-06 18:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 14:59 [PATCH] platform/x86: intel-uncore-freq: Add client processors Srinivas Pandruvada
2023-04-06 10:58 ` Hans de Goede
2023-04-06 18:12   ` srinivas pandruvada [this message]
2023-04-07 13:28 ` Hans de Goede

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=3a5a04091462fc33d4c61da2889fe7ce9bd55d97.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markgross@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).