From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Ivan Mikhaylov <fr0st61te@gmail.com>
Cc: Iwona Winiarska <iwona.winiarska@intel.com>,
Guenter Roeck <linux@roeck-us.net>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
openbmc@lists.ozlabs.org
Subject: Re: [PATCH 3/3] hwmon: (peci/cputemp) add Intel Emerald Rapids support
Date: Tue, 7 Oct 2025 10:31:59 +0200 [thread overview]
Message-ID: <277a2c83-de30-41a2-bfe4-d48efeceb6a1@molgen.mpg.de> (raw)
In-Reply-To: <20251006215321.5036-4-fr0st61te@gmail.com>
Dear Ivan,
Thank you for your patch.
Am 06.10.25 um 23:53 schrieb Ivan Mikhaylov:
> Add support to read DTS for reading Intel Emerald Rapids platform.
>
> Signed-off-by: Ivan Mikhaylov <fr0st61te@gmail.com>
> ---
> 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 c7112dbf008b..b350c9a76894 100644
> --- a/drivers/hwmon/peci/cputemp.c
> +++ b/drivers/hwmon/peci/cputemp.c
> @@ -364,6 +364,7 @@ static int init_core_mask(struct peci_cputemp *priv)
> case INTEL_ICELAKE_X:
> case INTEL_ICELAKE_D:
> case INTEL_SAPPHIRERAPIDS_X:
> + case INTEL_EMERALDRAPIDS_X:
> ret = peci_ep_pci_local_read(peci_dev, 0, reg->bus, reg->dev,
> reg->func, reg->offset + 4, &data);
> if (ret)
> @@ -539,6 +540,13 @@ static struct resolved_cores_reg resolved_cores_reg_spr = {
> .offset = 0x80,
> };
>
> +static struct resolved_cores_reg resolved_cores_reg_emr = {
> + .bus = 31,
> + .dev = 30,
> + .func = 6,
> + .offset = 0x80,
> +};
> +
> static const struct cpu_info cpu_hsx = {
> .reg = &resolved_cores_reg_hsx,
> .min_peci_revision = 0x33,
> @@ -563,6 +571,12 @@ static const struct cpu_info cpu_spr = {
> .thermal_margin_to_millidegree = &dts_ten_dot_six_to_millidegree,
> };
>
> +static const struct cpu_info cpu_emr = {
> + .reg = &resolved_cores_reg_emr,
Only use one space before the =.
> + .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",
> @@ -592,6 +606,10 @@ static const struct auxiliary_device_id peci_cputemp_ids[] = {
> .name = "peci_cpu.cputemp.spr",
> .driver_data = (kernel_ulong_t)&cpu_spr,
> },
> + {
> + .name = "peci_cpu.cputemp.emr",
> + .driver_data = (kernel_ulong_t)&cpu_emr,
> + },
> { }
> };
> MODULE_DEVICE_TABLE(auxiliary, peci_cputemp_ids);
Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>
Kind regards,
Paul
next prev parent reply other threads:[~2025-10-07 8:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 21:53 [PATCH 0/3] Add Emerald Rapids PECI support Ivan Mikhaylov
2025-10-06 21:53 ` [PATCH 1/3] peci: cpu: add Intel Emerald Rapids support Ivan Mikhaylov
2025-10-07 8:19 ` Paul Menzel
2025-10-12 18:11 ` Guenter Roeck
2025-10-06 21:53 ` [PATCH 2/3] hwmon: (peci/dimmtemp) add Intel Emerald Rapids platform support Ivan Mikhaylov
2025-10-07 8:26 ` Paul Menzel
2025-10-13 11:44 ` Ivan Mikhaylov
2025-10-13 14:47 ` Guenter Roeck
2025-10-12 18:12 ` Guenter Roeck
2025-10-06 21:53 ` [PATCH 3/3] hwmon: (peci/cputemp) add Intel Emerald Rapids support Ivan Mikhaylov
2025-10-07 8:31 ` Paul Menzel [this message]
2025-10-12 18:13 ` Guenter Roeck
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=277a2c83-de30-41a2-bfe4-d48efeceb6a1@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=fr0st61te@gmail.com \
--cc=iwona.winiarska@intel.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=openbmc@lists.ozlabs.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
all inboxes | Powered by JetHome®