From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Marek Vasut <marek.vasut+renesas@mailbox.org>
Cc: linux-hwmon@vger.kernel.org,
Akinobu Mita <akinobu.mita@gmail.com>,
Conor Dooley <conor+dt@kernel.org>,
Guenter Roeck <linux@roeck-us.net>,
Jean Delvare <jdelvare@suse.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [RESEND PATCH 2/2] hwmon: (pwm-fan) Implement after shutdown fan settings
Date: Fri, 5 Sep 2025 14:42:28 +0200 [thread overview]
Message-ID: <aLratMZ69w_sF2hO@shikoro> (raw)
In-Reply-To: <20250904202157.170600-2-marek.vasut+renesas@mailbox.org>
[-- Attachment #1: Type: text/plain, Size: 753 bytes --]
On Thu, Sep 04, 2025 at 10:21:10PM +0200, Marek Vasut wrote:
> Add fan-shutdown-percent property, used to describe fan RPM in percent set
> during shutdown. This is used to keep the fan running at fixed RPM after
> the kernel shut down, which is useful on hardware that does keep heating
> itself even after the kernel did shut down, for example from some sort of
> management core. The current behavior of pwm-fan is to unconditionally
> stop the fan on shutdown, which is not always the safe and correct thing
> to do, so let the hardware description include the expected behavior.
>
> Signed-off-by: Marek Vasut <marek.vasut+renesas@mailbox.org>
Works for me as promised!
Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-09-05 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 20:21 [RESEND PATCH 1/2] dt-bindings: hwmon: pwm-fan: Document after shutdown fan settings Marek Vasut
2025-09-04 20:21 ` [RESEND PATCH 2/2] hwmon: (pwm-fan) Implement " Marek Vasut
2025-09-05 12:42 ` Wolfram Sang [this message]
2025-09-05 21:13 ` Guenter Roeck
2025-09-05 18:40 ` [RESEND PATCH 1/2] dt-bindings: hwmon: pwm-fan: Document " Conor Dooley
2025-09-05 21:07 ` Guenter Roeck
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=aLratMZ69w_sF2hO@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=akinobu.mita@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=marek.vasut+renesas@mailbox.org \
--cc=robh@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.