From: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
To: Ming Yu <a0282524688@gmail.com>
Cc: tmyu0@nuvoton.com, lee@kernel.org, linus.walleij@linaro.org,
brgl@bgdev.pl, andi.shyti@kernel.org, mkl@pengutronix.de,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, wim@linux-watchdog.org,
linux@roeck-us.net, jdelvare@suse.com,
alexandre.belloni@bootlin.com, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
linux-watchdog@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-rtc@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH v6 6/7] hwmon: Add Nuvoton NCT6694 HWMON support
Date: Sun, 26 Jan 2025 16:42:50 +0900 [thread overview]
Message-ID: <c1cbb337-9ca5-4071-b05a-a97ab451f358@wanadoo.fr> (raw)
In-Reply-To: <20250123091115.2079802-7-a0282524688@gmail.com>
On 23/01/2025 at 18:11, Ming Yu wrote:
> This driver supports Hardware monitor functionality for NCT6694 MFD
> device based on USB interface.
>
> Signed-off-by: Ming Yu <a0282524688@gmail.com>
> ---
(...)
> +static int nct6694_temp_write(struct device *dev, u32 attr, int channel,
> + long val)
> +{
> + struct nct6694_hwmon_data *data = dev_get_drvdata(dev);
> + struct nct6694_cmd_header cmd_hd;
> + unsigned char temp_hyst;
> + signed char temp_max;
> + int ret;
> +
> + guard(mutex)(&data->lock);
> +
> + switch (attr) {
> + case hwmon_temp_enable:
> + if (val == 0)
> + data->hwmon_en.tin_en[channel / 8] &= ~BIT(channel % 8);
> + else if (val == 1)
> + data->hwmon_en.tin_en[channel / 8] |= BIT(channel % 8);
> + else
> + return -EINVAL;
> +
> + cmd_hd = (struct nct6694_cmd_header) {
> + .mod = NCT6694_HWMON_MOD,
> + .cmd = NCT6694_HWMON_CONTROL,
> + .sel = NCT6694_HWMON_CONTROL_SEL,
> + .len = cpu_to_le16(sizeof(data->hwmon_en))
> + };
> +
> + return nct6694_write_msg(data->nct6694, &cmd_hd,
> + &data->hwmon_en);
> + case hwmon_temp_max:
> + cmd_hd = (struct nct6694_cmd_header) {
> + .mod = NCT6694_HWMON_MOD,
> + .cmd = NCT6694_HWMON_ALARM,
> + .sel = NCT6694_HWMON_ALARM_SEL,
> + .len = cpu_to_le16(sizeof(data->msg->hwmon_alarm))
> + };
> + ret = nct6694_read_msg(data->nct6694, &cmd_hd,
> + &data->msg->hwmon_alarm);
> + if (ret)
> + return ret;
> +
> + val = clamp_val(val, -127000, 127000);
> + data->msg->hwmon_alarm.tin_cfg[channel].hl = temp_to_reg(val);
> +
> + return nct6694_write_msg(data->nct6694, &cmd_hd,
> + &data->msg->hwmon_alarm);
> + case hwmon_temp_max_hyst:
> + cmd_hd = (struct nct6694_cmd_header) {
> + .mod = NCT6694_HWMON_MOD,
> + .cmd = NCT6694_HWMON_ALARM,
> + .sel = NCT6694_HWMON_ALARM_SEL,
> + .len = cpu_to_le16(sizeof(data->msg->hwmon_alarm))
> + };
> + ret = nct6694_read_msg(data->nct6694, &cmd_hd,
> + &data->msg->hwmon_alarm);
> +
> + val = clamp_val(val, -127000, 127000);
> + temp_max = data->msg->hwmon_alarm.tin_cfg[channel].hl;
> + temp_hyst = temp_max - temp_to_reg(val);
> + temp_hyst = clamp_val(temp_hyst, 0, 7);
temp_hyst is unsigned. It can not be smaller than zero. No need for
clamp(), using min here is sufficient.
> + data->msg->hwmon_alarm.tin_cfg[channel].hyst =
> + (data->msg->hwmon_alarm.tin_cfg[channel].hyst & ~NCT6694_TIN_HYST_MASK) |
> + FIELD_PREP(NCT6694_TIN_HYST_MASK, temp_hyst);
> +
> + return nct6694_write_msg(data->nct6694, &cmd_hd,
> + &data->msg->hwmon_alarm);
> + default:
> + return -EOPNOTSUPP;
> + }
> +}
(...)
Yours sincerely,
Vincent Mailhol
next prev parent reply other threads:[~2025-01-26 7:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 9:11 [PATCH v6 0/7] Add Nuvoton NCT6694 MFD drivers Ming Yu
2025-01-23 9:11 ` [PATCH v6 1/7] mfd: Add core driver for Nuvoton NCT6694 Ming Yu
2025-01-23 9:11 ` [PATCH v6 2/7] gpio: Add Nuvoton NCT6694 GPIO support Ming Yu
2025-01-23 9:11 ` [PATCH v6 3/7] i2c: Add Nuvoton NCT6694 I2C support Ming Yu
2025-01-23 9:11 ` [PATCH v6 4/7] can: Add Nuvoton NCT6694 CANFD support Ming Yu
2025-01-23 11:09 ` Simon Horman
2025-02-04 2:55 ` Ming Yu
2025-01-26 8:47 ` Vincent Mailhol
2025-02-04 3:24 ` Ming Yu
2025-02-06 11:05 ` Vincent Mailhol
2025-01-23 9:11 ` [PATCH v6 5/7] watchdog: Add Nuvoton NCT6694 WDT support Ming Yu
2025-01-26 10:13 ` Vincent Mailhol
2025-02-04 2:44 ` Ming Yu
2025-01-23 9:11 ` [PATCH v6 6/7] hwmon: Add Nuvoton NCT6694 HWMON support Ming Yu
2025-01-26 7:42 ` Vincent Mailhol [this message]
2025-01-26 13:18 ` Guenter Roeck
2025-02-04 2:52 ` Ming Yu
2025-01-23 9:11 ` [PATCH v6 7/7] rtc: Add Nuvoton NCT6694 RTC support Ming Yu
2025-02-05 10:23 ` Alexandre Belloni
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=c1cbb337-9ca5-4071-b05a-a97ab451f358@wanadoo.fr \
--to=mailhol.vincent@wanadoo.fr \
--cc=a0282524688@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andi.shyti@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=brgl@bgdev.pl \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jdelvare@suse.com \
--cc=kuba@kernel.org \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tmyu0@nuvoton.com \
--cc=wim@linux-watchdog.org \
/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;
as well as URLs for NNTP newsgroup(s).