linux-kernel - Re: [PATCH 0/5] hwmon: (cros_ec): fan target, fan pwm control and temperature thresholds

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <536e51a1-5968-4493-96ce-287167b89288@roeck-us.net>
Date: Mon, 10 Jun 2024 18:18:05 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Thomas Weißschuh <linux@...ssschuh.net>,
 Benson Leung <bleung@...omium.org>, Tzung-Bi Shih <tzungbi@...nel.org>,
 Guenter Roeck <groeck@...omium.org>, Thomas Weißschuh
 <thomas@...ssschuh.net>, Jean Delvare <jdelvare@...e.com>
Cc: Dustin Howett <dustin@...ett.net>,
 Mario Limonciello <mario.limonciello@....com>,
 Stephen Horvath <s.horvath@...look.com.au>, chrome-platform@...ts.linux.dev,
 linux-kernel@...r.kernel.org, linux-hwmon@...r.kernel.org
Subject: Re: [PATCH 0/5] hwmon: (cros_ec): fan target, fan pwm control and
 temperature thresholds

On 6/8/24 01:12, Thomas Weißschuh wrote:
> Add support to cros_ec_hwmon for
> * fan target speed for fan 1
> * fan pwm control for all fans
> * fan temperature thresholds (RW) for all temp sensors
> 
> The EC also supports tempY_auto_pointZ_{pwm,temp} but that does not yet
> seem to be usable from "struct hwmon_channel_info".
> Guenter, is this intentional, do you want me to add support for it?
> 

When I wrote the _info API, I figured it was too chip specific to make
it generic. It is also at least somewhat questionable if it makes sense
to have all that configurable through sysfs in the first place; normally
the ranges are device specific and should be configured through the
thermal subsystem using devicetree properties and not be touched by
the user. There might even be warranty implications by playing with
thermal parameters if someone manages to overheat the system as result.
I really don't want to help enabling that.

Which leads to the next question - we are going way beyond just reporting
system operational parameters with your patches. What is the actual use
case ?

Thanks,
Guenter