From: Gabriel Ford <gabriel@gford.dev>
To: Clemens Ladisch <clemens@ladisch.de>,
Guenter Roeck <linux@roeck-us.net>,
linux-hwmon@vger.kernel.org (open list:K10TEMP HARDWARE
MONITORING DRIVER), linux-kernel@vger.kernel.org (open list)
Cc: Gabriel Ford <gabriel@gford.dev>
Subject: [PATCH] hwmon: (k10temp) Add per-CCD temperature monitoring for Zen5 Turin
Date: Wed, 12 Aug 2026 16:37:58 +0000 [thread overview]
Message-ID: <20260812163812.2760-1-gabriel@gford.dev> (raw)
Add support for per-CCD temperature monitoring on Zen 5 Turin (EPYC 9005)
CPUs, as they fall in a different model range with a larger number of
maximum CCDs compared to their desktop counterparts. Tested and working
on an EPYC 9555P.
Signed-off-by: Gabriel Ford <gabriel@gford.dev>
---
drivers/hwmon/k10temp.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/drivers/hwmon/k10temp.c b/drivers/hwmon/k10temp.c
index de0760dc597d..b882fe09ac1b 100644
--- a/drivers/hwmon/k10temp.c
+++ b/drivers/hwmon/k10temp.c
@@ -207,6 +207,10 @@ static const char *k10temp_temp_label[] = {
"Tccd10",
"Tccd11",
"Tccd12",
+ "Tccd13",
+ "Tccd14",
+ "Tccd15",
+ "Tccd16"
};
static int k10temp_read_labels(struct device *dev,
@@ -515,6 +519,10 @@ static int k10temp_probe(struct pci_dev *pdev, const struct pci_device_id *id)
}
} else if (boot_cpu_data.x86 == 0x1a) {
switch (boot_cpu_data.x86_model) {
+ case 0x00 ... 0x2f: /* Zen5 Turin */
+ data->ccd_offset = 0x1F0;
+ k10temp_get_ccd_support(data, 16);
+ break;
case 0x40 ... 0x4f: /* Zen5 Ryzen Desktop */
data->ccd_offset = 0x308;
k10temp_get_ccd_support(data, 8);
--
2.43.0
next reply other threads:[~2026-08-12 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 16:37 Gabriel Ford [this message]
2026-08-12 18:59 ` Guenter Roeck
[not found] <20260811050523.5688-1-gabriel@gford.dev>
2026-08-11 16:19 ` 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=20260812163812.2760-1-gabriel@gford.dev \
--to=gabriel@gford.dev \
--cc=clemens@ladisch.de \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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®