From: sashiko-bot@kernel.org
To: "Gabriel Ford" <gabriel@gford.dev>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH] hwmon: (k10temp) Add per-CCD temperature monitoring for Zen5 Turin
Date: Wed, 12 Aug 2026 16:49:07 +0000 [thread overview]
Message-ID: <20260812164907.C3C991F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260812163812.2760-1-gabriel@gford.dev>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The patch adds support for 16 CCDs (Tccd13-Tccd16) on Zen 5 Turin, but fails to expose these new channels to the hwmon subsystem and read handler, rendering the new sensors completely inaccessible.
--
--- Patch [1]: [PATCH] hwmon: (k10temp) Add per-CCD temperature monitoring for Zen5 Turin ---
commit 91c5657242878293503804d18c7b5245b1066ddc
Author: Gabriel Ford <gabriel@gford.dev>
hwmon: (k10temp) Add per-CCD temperature monitoring for Zen5 Turin
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.
> diff --git a/drivers/hwmon/k10temp.c b/drivers/hwmon/k10temp.c
> index de0760dc597da..b882fe09ac1b6 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"
> };
[Severity: Medium]
Will these new sensors actually be exposed and read correctly by the hwmon
subsystem without corresponding updates to k10temp_info and
k10temp_read_temp()?
In k10temp_info, the hwmon_channel_info array dictates the maximum number of
attributes created, but it appears to be missing entries for Tccd13 through
Tccd16:
drivers/hwmon/k10temp.c:k10temp_info[] = {
HWMON_CHANNEL_INFO(temp,
...
HWMON_T_INPUT | HWMON_T_LABEL,
HWMON_T_INPUT | HWMON_T_LABEL),
NULL
};
Additionally, in k10temp_read_temp(), the switch statement handling raw CCD
reads is restricted to channels 2 through 13:
drivers/hwmon/k10temp.c:k10temp_read_temp() {
...
case 2 ... 13: /* Tccd{1-12} */
ret = read_ccd_temp_reg(data, channel - 2, ®val);
if (ret)
return ret;
*val = (regval & ZEN_CCD_TEMP_MASK) * 125 - 49000;
break;
default:
return ret;
...
}
Will reading channels 14-17 (Tccd13-16) fall through to the default case and
return -EOPNOTSUPP?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260812163812.2760-1-gabriel@gford.dev?part=1
next prev parent reply other threads:[~2026-08-12 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 16:37 [PATCH] hwmon: (k10temp) Add per-CCD temperature monitoring for Zen5 Turin Gabriel Ford
2026-08-12 16:49 ` sashiko-bot [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=20260812164907.C3C991F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=gabriel@gford.dev \
--cc=linux-hwmon@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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