From: Guenter Roeck <linux@roeck-us.net>
To: Ali Ahmet Memis <ali@iusegentoo.com>
Cc: Ming Yu <tmyu0@nuvoton.com>, Ming Yu <a0282524688@gmail.com>,
Jean Delvare <jdelvare@suse.com>, Lee Jones <lee@kernel.org>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: (nct6694) do not expose enable on DTIN temperature channels
Date: Wed, 9 Sep 2026 13:37:42 -0700 [thread overview]
Message-ID: <a9885f92-e54a-42d6-bf96-db2ee819b473@roeck-us.net> (raw)
In-Reply-To: <20260803102148.14196-1-ali@iusegentoo.com>
On Mon, Aug 03, 2026 at 10:21:48AM +0000, Ali Ahmet Memis wrote:
> The driver registers 26 temperature channels, all advertising
> HWMON_T_ENABLE, and indexes the enable bitmap with the raw channel:
>
> data->hwmon_en.tin_en[channel / 8] |= BIT(channel % 8);
>
> tin_en is two bytes and only covers the 5 THR and 5 TDP channels
> (index 0-9). The 16 DTIN channels (index 10-25) are enabled by the
> firmware and were never meant to carry an enable bit. Because the
> control structure is packed, writing temp17_enable and above indexes
> past tin_en into the fin_en bytes that follow it, so it toggles fan
> enable state instead; nct6694_hwmon_init() then sends the whole
> structure back to the device, and reads report fan state as temperature
> state. It stays within the structure, so this is not a memory safety
> problem, but on a board that uses the fan channels it is not harmless.
>
> Give the DTIN channels a temperature config without HWMON_T_ENABLE so
> the core never creates their enable attribute. The enable path is then
> reachable only for the first 10 channels, which stay within tin_en, and
> fin_en is left alone. The DTIN input and limit attributes are unchanged.
>
> Fixes: 197e779d29d8 ("hwmon: Add Nuvoton NCT6694 HWMON support")
> Suggested-by: Ming Yu <tmyu0@nuvoton.com>
> Link: https://lore.kernel.org/all/20260802124730.20387-1-ali@iusegentoo.com/
> Signed-off-by: Ali Ahmet Memis <ali@iusegentoo.com>
Applied.
Thanks,
Guenter
prev parent reply other threads:[~2026-09-09 20:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 10:21 Ali Ahmet Memis
2026-09-09 20:37 ` Guenter Roeck [this message]
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=a9885f92-e54a-42d6-bf96-db2ee819b473@roeck-us.net \
--to=linux@roeck-us.net \
--cc=a0282524688@gmail.com \
--cc=ali@iusegentoo.com \
--cc=jdelvare@suse.com \
--cc=lee@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tmyu0@nuvoton.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
all inboxes | Powered by JetHome®