From: Armin Wolf <W_Armin@gmx.de>
To: "Thomas Weißschuh" <linux@weissschuh.net>,
"Guenter Roeck" <linux@roeck-us.net>,
"Benson Leung" <bleung@chromium.org>,
"Shuah Khan" <skhan@linuxfoundation.org>
Cc: Guenter Roeck <groeck@chromium.org>,
chrome-platform@lists.linux.dev, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] hwmon: (cros_ec) Allow modification of fan curves
Date: Sat, 30 May 2026 18:37:32 +0200 [thread overview]
Message-ID: <87825203-0bbb-46a4-8939-a904f5a546ab@gmx.de> (raw)
In-Reply-To: <20260529-cros_ec-hwmon-fan-curve-v1-5-da6792b3830f@weissschuh.net>
Am 29.05.26 um 22:31 schrieb Thomas Weißschuh:
> The fan curves used by the embedded controller can be configured.
>
> Expose this through the standard hwmon sysfs ABI.
>
> Only allow the curves to be made more aggressive than the current ones.
>
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> ---
> Documentation/hwmon/cros_ec_hwmon.rst | 2 +-
> drivers/hwmon/cros_ec_hwmon.c | 68 +++++++++++++++++++++++++++++++++--
> 2 files changed, 67 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/hwmon/cros_ec_hwmon.rst b/Documentation/hwmon/cros_ec_hwmon.rst
> index 7a8683227252..a3d0e43c8833 100644
> --- a/Documentation/hwmon/cros_ec_hwmon.rst
> +++ b/Documentation/hwmon/cros_ec_hwmon.rst
> @@ -48,4 +48,4 @@ PWM fan control
> in the thermal framework as well.
>
> Fan curves:
> - If supported by the EC. Reading only.
> + If supported by the EC. Reading and writing.
> diff --git a/drivers/hwmon/cros_ec_hwmon.c b/drivers/hwmon/cros_ec_hwmon.c
> index 731143f8c6b2..fb73a00ebeeb 100644
> --- a/drivers/hwmon/cros_ec_hwmon.c
> +++ b/drivers/hwmon/cros_ec_hwmon.c
> @@ -8,9 +8,11 @@
> #include <linux/device.h>
> #include <linux/hwmon.h>
> #include <linux/hwmon-sysfs.h>
> +#include <linux/kstrtox.h>
> #include <linux/math.h>
> #include <linux/mod_devicetable.h>
> #include <linux/module.h>
> +#include <linux/overflow.h>
> #include <linux/platform_device.h>
> #include <linux/platform_data/cros_ec_commands.h>
> #include <linux/platform_data/cros_ec_proto.h>
> @@ -135,6 +137,22 @@ static int cros_ec_hwmon_get_thermal_config(struct cros_ec_device *cros_ec, u8 i
> return 0;
> }
>
> +static int cros_ec_hwmon_set_thermal_config(struct cros_ec_device *cros_ec, u8 index,
> + const struct ec_thermal_config *config)
> +{
> + struct ec_params_thermal_set_threshold_v1 req = {};
> + int ret;
> +
> + req.sensor_num = index;
> + req.cfg = *config;
> + ret = cros_ec_cmd(cros_ec, 1, EC_CMD_THERMAL_SET_THRESHOLD,
> + &req, sizeof(req), NULL, 0);
> + if (ret < 0)
> + return ret;
> +
> + return 0;
> +}
> +
> static int cros_ec_hwmon_read_temp_threshold(struct cros_ec_device *cros_ec, u8 index,
> enum ec_temp_thresholds threshold, u32 *temp)
> {
> @@ -417,14 +435,60 @@ static ssize_t temp_auto_point_temp_show(struct device *dev, struct device_attri
> return sysfs_emit(buf, "%ld\n", cros_ec_hwmon_kelvin_to_millicelsius(temp));
> }
>
> +static ssize_t temp_auto_point_temp_store(struct device *dev, struct device_attribute *attr,
> + const char *buf, size_t size)
> +{
> + struct sensor_device_attribute_2 *sattr = to_sensor_dev_attr_2(attr);
> + struct cros_ec_hwmon_priv *priv = dev_get_drvdata(dev);
> + struct ec_thermal_config config;
> + u32 *temp_field;
> + s64 temp;
> + int ret;
> +
> + ret = kstrtos64(buf, 10, &temp);
> + if (ret)
> + return ret;
> +
> + temp = cros_ec_hwmon_millicelsius_to_kelvin(temp);
> +
> + if (overflows_type(temp, config.temp_fan_off))
> + return -ERANGE;
> +
> + guard(hwmon_lock)(dev);
> +
> + ret = cros_ec_hwmon_get_thermal_config(priv->cros_ec, sattr->index, &config);
> + if (ret)
> + return ret;
> +
> + if (cros_ec_hwmon_attr_is_temp_fan_off(sattr))
> + temp_field = &config.temp_fan_off;
> + else /* temp_fan_max */
> + temp_field = &config.temp_fan_max;
> +
> + /* Only allow values which are more aggressive than the current ones */
> + if (temp > *temp_field)
> + return -EINVAL;
Hi,
i think it would be more practical for users to increase and later decrease the fan curve values.
Could the driver copy the original fan curve configuration and use that instead? This would also
require to restore the original fan curve during shutdown and removal.
Thanks,
Armin Wolf
> +
> + *temp_field = temp;
> +
> + if (config.temp_fan_off > config.temp_fan_max)
> + return -EINVAL;
> +
> + ret = cros_ec_hwmon_set_thermal_config(priv->cros_ec, sattr->index, &config);
> + if (ret)
> + return ret;
> +
> + return size;
> +}
> +
> #define CROS_EC_HWMON_TEMP_AUTO_POINT_ATTRS(_idx) \
> static SENSOR_DEVICE_ATTR_2_RO(temp ## _idx ## _auto_point1_pwm, \
> temp_auto_point_pwm, 0, (_idx) - 1); \
> static SENSOR_DEVICE_ATTR_2_RO(temp ## _idx ## _auto_point2_pwm, \
> temp_auto_point_pwm, 1, (_idx) - 1); \
> - static SENSOR_DEVICE_ATTR_2_RO(temp ## _idx ## _auto_point1_temp, \
> + static SENSOR_DEVICE_ATTR_2_RW(temp ## _idx ## _auto_point1_temp, \
> temp_auto_point_temp, 0, (_idx) - 1); \
> - static SENSOR_DEVICE_ATTR_2_RO(temp ## _idx ## _auto_point2_temp, \
> + static SENSOR_DEVICE_ATTR_2_RW(temp ## _idx ## _auto_point2_temp, \
> temp_auto_point_temp, 1, (_idx) - 1) \
>
> #define CROS_EC_HWMON_TEMP_AUTO_POINT_ATTRS_PTRS(_idx) \
>
next prev parent reply other threads:[~2026-05-30 16:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 20:31 [PATCH 0/5] hwmon: (cros_ec) Add support for " Thomas Weißschuh
2026-05-29 20:31 ` [PATCH 1/5] hwmon: (cros_ec) Implement custom kelvin to celsius conversions Thomas Weißschuh
2026-06-09 20:50 ` Guenter Roeck
2026-05-29 20:31 ` [PATCH 2/5] hwmon: (cros_ec) Prepare the addition of custom groups Thomas Weißschuh
2026-06-09 20:51 ` Guenter Roeck
2026-05-29 20:31 ` [PATCH 3/5] hwmon: (cros_ec) Split out cros_ec_hwmon_get_thermal_config() Thomas Weißschuh
2026-06-09 20:52 ` Guenter Roeck
2026-05-29 20:31 ` [PATCH 4/5] hwmon: (cros_ec) Add support for displaying fan curves Thomas Weißschuh
2026-06-09 20:53 ` Guenter Roeck
2026-05-29 20:31 ` [PATCH 5/5] hwmon: (cros_ec) Allow modification of " Thomas Weißschuh
2026-05-30 16:37 ` Armin Wolf [this message]
2026-06-04 9:04 ` Thomas Weißschuh
2026-06-04 10:33 ` Armin Wolf
2026-06-08 13:34 ` Guenter Roeck
2026-06-08 15:53 ` Thomas Weißschuh
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=87825203-0bbb-46a4-8939-a904f5a546ab@gmx.de \
--to=w_armin@gmx.de \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linux@weissschuh.net \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®