From: Guenter Roeck <linux@roeck-us.net>
To: Sung-Chi Li <lschyi@google.com>
Cc: "Benson Leung" <bleung@chromium.org>,
"Guenter Roeck" <groeck@chromium.org>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Jonathan Corbet" <corbet@lwn.net>,
chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-hwmon@vger.kernel.org, linux-doc@vger.kernel.org,
"Sung-Chi Li" <lschyi@chromium.org>
Subject: Re: [PATCH v6 3/3] hwmon: (cros_ec) register fans into thermal framework cooling devices
Date: Wed, 24 Sep 2025 12:31:29 -0700 [thread overview]
Message-ID: <c2dc1970-386f-4e4f-b1cd-ca849d002aa6@roeck-us.net> (raw)
In-Reply-To: <20250911-cros_ec_fan-v6-3-a1446cc098af@google.com>
On Thu, Sep 11, 2025 at 06:56:36AM +0000, Sung-Chi Li wrote:
> From: Sung-Chi Li <lschyi@chromium.org>
>
> Register fans connected under EC as thermal cooling devices as well, so
> these fans can then work with the thermal framework.
>
> During the driver probing phase, we will also try to register each fan
> as a thermal cooling device based on previous probe result (whether the
> there are fans connected on that channel, and whether EC supports fan
> control). The basic get max state, get current state, and set current
> state methods are then implemented as well.
>
> Signed-off-by: Sung-Chi Li <lschyi@chromium.org>
> Acked-by: Thomas Weißschuh <linux@weissschuh.net>
Applied.
Guenter
prev parent reply other threads:[~2025-09-24 19:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 6:56 [PATCH v6 0/3] Export fan control and register fans as " Sung-Chi Li via B4 Relay
2025-09-11 6:56 ` [PATCH v6 1/3] platform/chrome: update pwm fan control host commands Sung-Chi Li via B4 Relay
2025-09-24 19:30 ` Guenter Roeck
2025-09-11 6:56 ` [PATCH v6 2/3] hwmon: (cros_ec) add PWM control over fans Sung-Chi Li via B4 Relay
2025-09-24 19:31 ` Guenter Roeck
2025-09-11 6:56 ` [PATCH v6 3/3] hwmon: (cros_ec) register fans into thermal framework cooling devices Sung-Chi Li via B4 Relay
2025-09-24 19:31 ` 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=c2dc1970-386f-4e4f-b1cd-ca849d002aa6@roeck-us.net \
--to=linux@roeck-us.net \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=corbet@lwn.net \
--cc=groeck@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=lschyi@chromium.org \
--cc=lschyi@google.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®