From: Vincent Jardin via B4 Relay <devnull+vjardin.free.fr@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
Vincent Jardin <vjardin@free.fr>
Subject: [PATCH] hwmon: (tmp401) register with thermal subsystem
Date: Mon, 13 Jul 2026 23:07:54 +0200 [thread overview]
Message-ID: <20260713-for-upstream-hwmon-tmp401-register-tz-v1-1-47315d8617bc@free.fr> (raw)
From: Vincent Jardin <vjardin@free.fr>
tmp401 is missing HWMON_C_REGISTER_TZ. So a devicetree thermal
zone referencing a such sensor ('thermal-sensors = <&tmp411 N>')
fails to register it. Then its cooling-maps is not set, which means
that the fans are not managed.
Same as lm90 or jc42, set HWMON_C_REGISTER_TZ.
Boards without the property into the DT keep the same behavior.
Signed-off-by: Vincent Jardin <vjardin@free.fr>
---
It was checked on a LX2160A board that uses a TMP411 for the chassis ambient
input of a fan thermal zone.
Without this patch the zone silently never registers.
With this patch, the zone registers and the cooling-map drives the EMC2305
fans.
---
drivers/hwmon/tmp401.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hwmon/tmp401.c b/drivers/hwmon/tmp401.c
index ca0ff525ea29..83aafe4bd3e7 100644
--- a/drivers/hwmon/tmp401.c
+++ b/drivers/hwmon/tmp401.c
@@ -695,7 +695,7 @@ static int tmp401_probe(struct i2c_client *client)
info->type = hwmon_chip;
info->config = data->chip_channel_config;
- data->chip_channel_config[0] = HWMON_C_UPDATE_INTERVAL;
+ data->chip_channel_config[0] = HWMON_C_REGISTER_TZ | HWMON_C_UPDATE_INTERVAL;
info = &data->temp_info;
info->type = hwmon_temp;
---
base-commit: ca078d004cf58137bcf8cb24a8b271397431ba58
change-id: 20260713-for-upstream-hwmon-tmp401-register-tz-d07130b9be30
Best regards,
--
Vincent Jardin <vjardin@free.fr>
reply other threads:[~2026-07-13 21:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260713-for-upstream-hwmon-tmp401-register-tz-v1-1-47315d8617bc@free.fr \
--to=devnull+vjardin.free.fr@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=vjardin@free.fr \
/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