From: Marek Vasut <marek.vasut@mailbox.org>
To: Rob Herring <robh@kernel.org>
Cc: linux-hwmon@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
Guenter Roeck <linux@roeck-us.net>,
Jean Delvare <jdelvare@suse.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: hwmon: pwm-fan: Document after shutdown fan settings
Date: Sun, 31 Aug 2025 21:13:45 +0200 [thread overview]
Message-ID: <4aa7dcb5-fada-43dc-b9e1-b51bb328fc02@mailbox.org> (raw)
In-Reply-To: <9ba974d7-456d-4255-bb74-cfd1998a43ae@mailbox.org>
On 7/20/25 10:07 PM, Marek Vasut wrote:
> On 7/8/25 5:50 PM, Rob Herring wrote:
>> On Mon, Jun 30, 2025 at 12:02:08AM +0200, Marek Vasut wrote:
>>> Document 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.
>>
>> This sounds more like "don't ever let the fan go below this RPM" or
>> "don't ever turn off the fan". IOW, it is more than just shutdown.
>
> This property is literally only used during/after shutdown , this does
> not limit or affect fan RPM during runtime in any way.
How can we proceed here ?
prev parent reply other threads:[~2025-08-31 19:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-29 22:02 [PATCH 1/2] dt-bindings: hwmon: pwm-fan: Document after shutdown fan settings Marek Vasut
2025-06-29 22:02 ` [PATCH 2/2] hwmon: (pwm-fan) Implement " Marek Vasut
2025-07-08 15:50 ` [PATCH 1/2] dt-bindings: hwmon: pwm-fan: Document " Rob Herring
2025-07-20 20:07 ` Marek Vasut
2025-08-31 19:13 ` Marek Vasut [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=4aa7dcb5-fada-43dc-b9e1-b51bb328fc02@mailbox.org \
--to=marek.vasut@mailbox.org \
--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=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 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).