mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Winiarska, Iwona" <iwona.winiarska@intel.com>
To: "linux@roeck-us.net" <linux@roeck-us.net>,
	"linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Solanki, Naresh" <naresh.solanki@9elements.com>,
	"jdelvare@suse.com" <jdelvare@suse.com>
Cc: "Rudolph, Patrick" <patrick.rudolph@9elements.com>
Subject: Re: [PATCH v3 2/3] hwmon: (peci/cputemp) Add Intel Sapphire Rapids support
Date: Wed, 19 Jul 2023 20:01:01 +0000	[thread overview]
Message-ID: <f3e6303e867b7a335289bf2ea3aacec5a637fb8b.camel@intel.com> (raw)
In-Reply-To: <20230719184155.59375-2-Naresh.Solanki@9elements.com>

On Wed, 2023-07-19 at 20:41 +0200, Naresh Solanki wrote:
> From: Patrick Rudolph <patrick.rudolph@9elements.com>
> 
> Add support to read DTS for reading Intel Sapphire Rapids platform.
> 
> Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
> Signed-off-by: Naresh Solanki <Naresh.Solanki@9elements.com>
> Acked-by: Guenter Roeck <linux@roeck-us.net>

Reviewed-by: Iwona Winiarska <iwona.winiarska@intel.com>

Thanks
-Iwona

> ---
> Chagnes in V3:
> - Update Acked-by in commit message.
> Changes in V2:
> - Refactored from previous patchset as seperate patch based on subsystem.
> ---
>  drivers/hwmon/peci/cputemp.c | 18 ++++++++++++++++++
>  1 file changed, 18 insertions(+)
> 
> diff --git a/drivers/hwmon/peci/cputemp.c b/drivers/hwmon/peci/cputemp.c
> index e5b65a382772..a812c15948d9 100644
> --- a/drivers/hwmon/peci/cputemp.c
> +++ b/drivers/hwmon/peci/cputemp.c
> @@ -363,6 +363,7 @@ static int init_core_mask(struct peci_cputemp *priv)
>         switch (peci_dev->info.model) {
>         case INTEL_FAM6_ICELAKE_X:
>         case INTEL_FAM6_ICELAKE_D:
> +       case INTEL_FAM6_SAPPHIRERAPIDS_X:
>                 ret = peci_ep_pci_local_read(peci_dev, 0, reg->bus, reg->dev,
>                                              reg->func, reg->offset + 4,
> &data);
>                 if (ret)
> @@ -531,6 +532,13 @@ static struct resolved_cores_reg resolved_cores_reg_icx =
> {
>         .offset = 0xd0,
>  };
>  
> +static struct resolved_cores_reg resolved_cores_reg_spr = {
> +       .bus = 31,
> +       .dev = 30,
> +       .func = 6,
> +       .offset = 0x80,
> +};
> +
>  static const struct cpu_info cpu_hsx = {
>         .reg            = &resolved_cores_reg_hsx,
>         .min_peci_revision = 0x33,
> @@ -549,6 +557,12 @@ static const struct cpu_info cpu_icx = {
>         .thermal_margin_to_millidegree = &dts_ten_dot_six_to_millidegree,
>  };
>  
> +static const struct cpu_info cpu_spr = {
> +       .reg            = &resolved_cores_reg_spr,
> +       .min_peci_revision = 0x40,
> +       .thermal_margin_to_millidegree = &dts_ten_dot_six_to_millidegree,
> +};
> +
>  static const struct auxiliary_device_id peci_cputemp_ids[] = {
>         {
>                 .name = "peci_cpu.cputemp.hsx",
> @@ -574,6 +588,10 @@ static const struct auxiliary_device_id
> peci_cputemp_ids[] = {
>                 .name = "peci_cpu.cputemp.icxd",
>                 .driver_data = (kernel_ulong_t)&cpu_icx,
>         },
> +       {
> +               .name = "peci_cpu.cputemp.spr",
> +               .driver_data = (kernel_ulong_t)&cpu_spr,
> +       },
>         { }
>  };
>  MODULE_DEVICE_TABLE(auxiliary, peci_cputemp_ids);


  reply	other threads:[~2023-07-19 20:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-19 18:41 [PATCH v3 1/3] peci: cpu: " Naresh Solanki
2023-07-19 18:41 ` [PATCH v3 2/3] hwmon: (peci/cputemp) " Naresh Solanki
2023-07-19 20:01   ` Winiarska, Iwona [this message]
2023-07-19 18:41 ` [PATCH v3 3/3] hwmon: (peci/dimmtemp) Add " Naresh Solanki
2023-07-19 20:05   ` Winiarska, Iwona
2023-07-20  7:49     ` Naresh Solanki
2023-07-19 20:00 ` [PATCH v3 1/3] peci: cpu: Add Intel " Winiarska, Iwona

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=f3e6303e867b7a335289bf2ea3aacec5a637fb8b.camel@intel.com \
    --to=iwona.winiarska@intel.com \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=naresh.solanki@9elements.com \
    --cc=patrick.rudolph@9elements.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

Powered by JetHome