From: "Winiarska, Iwona" <iwona.winiarska@intel.com>
To: "linux@roeck-us.net" <linux@roeck-us.net>,
"changhuang.liang@starfivetech.com"
<changhuang.liang@starfivetech.com>
Cc: "linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: [PATCH v3 4/6] peci: cpu: Add Intel Granite Rapids support
Date: Fri, 16 Oct 2026 20:09:49 +0000 [thread overview]
Message-ID: <b90b7be3a63f85347e0e230f0f4e1df6725f82c0.camel@intel.com> (raw)
In-Reply-To: <20261008100623.7085-5-changhuang.liang@starfivetech.com>
On Thu, 2026-10-08 at 03:06 -0700, Changhuang Liang wrote:
> Add support for detection of Intel Granite Rapids processor based on
> CPU model.
>
> Granite Rapids processors with the model set to INTEL_GRANITERAPIDS_X.
> The data field for this entry is "gnr".
>
> Tested on JHB100 BMC with Intel Granite Rapids processors.
>
> Signed-off-by: Changhuang Liang <changhuang.liang@starfivetech.com>
Reviewed-by: Iwona Winiarska <iwona.winiarska@intel.com>
Thanks
-Iwona
> ---
> drivers/peci/cpu.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/peci/cpu.c b/drivers/peci/cpu.c
> index c9fc06c9ff53..abf004637949 100644
> --- a/drivers/peci/cpu.c
> +++ b/drivers/peci/cpu.c
> @@ -325,6 +325,10 @@ static const struct peci_device_id peci_cpu_device_ids[]
> = {
> .x86_vfm = INTEL_EMERALDRAPIDS_X,
> .data = "emr",
> },
> + { /* Granite Rapids */
> + .x86_vfm = INTEL_GRANITERAPIDS_X,
> + .data = "gnr",
> + },
> { }
> };
> MODULE_DEVICE_TABLE(peci, peci_cpu_device_ids);
next prev parent reply other threads:[~2026-10-16 20:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 10:06 [PATCH v3 0/6] Add StarFive JHB100 PECI support Changhuang Liang
2026-10-08 10:06 ` [PATCH v3 1/6] dt-bindings: peci: Add StarFive JHB100 PECI controller Changhuang Liang
2026-10-08 11:45 ` sashiko-bot
2026-10-16 20:08 ` Winiarska, Iwona
2026-10-08 10:06 ` [PATCH v3 2/6] peci: controller: Add StarFive JHB100 PECI driver Changhuang Liang
2026-10-08 11:52 ` sashiko-bot
2026-10-16 20:09 ` Winiarska, Iwona
2026-10-08 10:06 ` [PATCH v3 3/6] peci: Add support for PECI CC 0x83 retry condition Changhuang Liang
2026-10-08 11:51 ` sashiko-bot
2026-10-16 20:09 ` Winiarska, Iwona
2026-10-08 10:06 ` [PATCH v3 4/6] peci: cpu: Add Intel Granite Rapids support Changhuang Liang
2026-10-08 11:49 ` sashiko-bot
2026-10-16 20:09 ` Winiarska, Iwona [this message]
2026-10-08 10:06 ` [PATCH v3 5/6] hwmon: (peci/cputemp) Add support for Granite Rapids (GNR) Changhuang Liang
2026-10-08 11:48 ` sashiko-bot
2026-10-16 20:10 ` Winiarska, Iwona
2026-10-08 10:06 ` [PATCH v3 6/6] hwmon: (peci/dimmtemp) " Changhuang Liang
2026-10-08 11:48 ` sashiko-bot
2026-10-16 20:10 ` 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=b90b7be3a63f85347e0e230f0f4e1df6725f82c0.camel@intel.com \
--to=iwona.winiarska@intel.com \
--cc=changhuang.liang@starfivetech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=openbmc@lists.ozlabs.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@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