From: sashiko-bot@kernel.org
To: "Thomas Richard (congatec GmbH)" <thomas.richard@bootlin.com>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH 2/2] hwmon: (cgbc-hwmon): Add some temperature sensors
Date: Thu, 10 Sep 2026 13:45:38 +0000 [thread overview]
Message-ID: <20260910134538.76E6F1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260910-cgbc-hwmon-fix-and-new-sensors-v1-2-ef13ae2fa147@bootlin.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The patch adds a 15th voltage sensor ('12V Standby Voltage', mapping to `in14_input`) to the driver's string labels and documentation, but fails to add its corresponding configuration entry to the `cgbc_hwmon_info` array. As a result, the hardware monitoring core will silently ignore the 15th channel and fail to expose it to sysfs.
--
commit 0d30ff3c376bb1134975af10205e094badb07304
Author: Thomas Richard (congatec GmbH) <thomas.richard@bootlin.com>
hwmon: (cgbc-hwmon): Add some temperature sensors
This commit adds several new temperature sensors, updating documentation and
string labels to match the Congatec board controller documentation. It also
modifies existing labels.
> diff --git a/drivers/hwmon/cgbc-hwmon.c b/drivers/hwmon/cgbc-hwmon.c
> index 2effa0b562862..098896ec8c6f6 100644
> --- a/drivers/hwmon/cgbc-hwmon.c
> +++ b/drivers/hwmon/cgbc-hwmon.c
> @@ -41,32 +41,42 @@ enum cgbc_sensor_types {
[ ... ]
> static const char * const cgbc_hwmon_labels_in[] = {
> - "CPU Voltage",
> + "CPU Core Voltage",
> "DC Runtime Voltage",
> "DC Standby Voltage",
> "CMOS Battery Voltage",
> - "Battery Voltage",
> + "Battery Supply Voltage",
> "AC Voltage",
> "Other Voltage",
> - "5V Voltage",
> + "5V Runtime Voltage",
> "5V Standby Voltage",
> - "3V3 Voltage",
> + "3V3 Runtime Voltage",
> "3V3 Standby Voltage",
> "VCore A Voltage",
> "VCore B Voltage",
> - "12V Voltage",
> + "12V Runtime Voltage",
> + "12V Standby Voltage",
> };
[ ... ]
> @@ -255,7 +265,12 @@ static const struct hwmon_channel_info * const cgbc_hwmon_info[] = {
> HWMON_T_INPUT | HWMON_T_LABEL, HWMON_T_INPUT | HWMON_T_LABEL,
> HWMON_T_INPUT | HWMON_T_LABEL, HWMON_T_INPUT | HWMON_T_LABEL,
> HWMON_T_INPUT | HWMON_T_LABEL, HWMON_T_INPUT | HWMON_T_LABEL,
> - HWMON_T_INPUT | HWMON_T_LABEL, HWMON_T_INPUT | HWMON_T_LABEL),
> + HWMON_T_INPUT | HWMON_T_LABEL, HWMON_T_INPUT | HWMON_T_LABEL,
> + HWMON_T_INPUT | HWMON_T_LABEL, HWMON_T_INPUT | HWMON_T_LABEL,
> + HWMON_T_INPUT | HWMON_T_LABEL, HWMON_T_INPUT | HWMON_T_LABEL,
> + HWMON_T_INPUT | HWMON_T_LABEL, HWMON_T_INPUT | HWMON_T_LABEL,
> + HWMON_T_INPUT | HWMON_T_LABEL, HWMON_T_INPUT | HWMON_T_LABEL,
> + HWMON_T_INPUT | HWMON_T_LABEL),
> HWMON_CHANNEL_INFO(in,
> HWMON_I_INPUT | HWMON_I_LABEL, HWMON_I_INPUT | HWMON_I_LABEL,
> HWMON_I_INPUT | HWMON_I_LABEL, HWMON_I_INPUT | HWMON_I_LABEL,
[Severity: Medium]
This patch adds a 15th voltage label ("12V Standby Voltage"), but is the
corresponding configuration entry missing from the cgbc_hwmon_info array?
Looking at the 'in' channel info array here, it only has 14 configuration
elements.
Since the hardware monitoring core iterates over the cgbc_hwmon_info
array and stops after 14 entries for 'in', will it silently ignore the 15th
channel and fail to expose it to sysfs?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260910-cgbc-hwmon-fix-and-new-sensors-v1-0-ef13ae2fa147@bootlin.com?part=2
next prev parent reply other threads:[~2026-09-10 13:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 13:28 [PATCH 0/2] Congatec Board Controller: Fix current sensor lookup and add new sensors Thomas Richard (congatec GmbH)
2026-09-10 13:28 ` [PATCH 1/2] hwmon: (cgbc-hwmon): Fix current sensors ID lookup Thomas Richard (congatec GmbH)
2026-09-10 13:45 ` sashiko-bot
2026-09-11 0:58 ` Guenter Roeck
2026-09-11 7:23 ` Thomas Richard
2026-09-11 13:57 ` Guenter Roeck
2026-09-11 17:33 ` Thomas Richard
2026-09-10 13:28 ` [PATCH 2/2] hwmon: (cgbc-hwmon): Add some temperature sensors Thomas Richard (congatec GmbH)
2026-09-10 13:45 ` sashiko-bot [this message]
2026-09-10 14:56 ` Guenter Roeck
2026-09-11 0:59 ` 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=20260910134538.76E6F1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=thomas.richard@bootlin.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