From: Rob Herring <robh@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Naresh Solanki <naresh.solanki@9elements.com>,
devicetree@vger.kernel.org, Jean Delvare <jdelvare@suse.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org,
Patrick Rudolph <patrick.rudolph@9elements.com>
Subject: Re: [PATCH v2 1/3] dt-bindings: hwmon: fan: Add fan binding to schema
Date: Tue, 11 Oct 2022 14:37:44 -0500 [thread overview]
Message-ID: <20221011193744.GA4051000-robh@kernel.org> (raw)
In-Reply-To: <8d2e905b-8669-b7ec-c7c0-1b0d78fded92@roeck-us.net>
On Tue, Oct 11, 2022 at 09:46:08AM -0700, Guenter Roeck wrote:
> On 10/11/22 09:12, Naresh Solanki wrote:
> > Hi Guenter,
> >
> > fan-common is intended for fan properties. i.e., those derived from
> > fan datasheets.
> > For min-rpm, some fans have minimum non zero rpm like 1900rpm below which
> > the fan cannot run.
> >
>
> I would argue the properties are for fan controllers, not for fans.
> Fans don't have or depend on specific pwm frequencies. Fan controllers
> do.
Presumably fan controllers can produce a range of frequencies. If they
need a specific frequency, then why are they programmable? Something
outside the fan controller must have the constraint.
> Fans don't have a configurable pwm polarity. Fan controllers do,
> to match the hardware on a board.
We don't model an inverter, so it's got to go somewhere.
> Fans don't have or rely on
> a target rpm. That is a system property, configured into the
> fan controller. And so on.
Yes, but it is per fan. per fan properties/settings should go in the fan
node IMO.
> If this is for fans, we'll need another set of properties for
> fan controllers. The driver for max6639, being a fan controller,
> would need to implement those properties.
>
> Also, as implemented in the MAX6639, max-rpm is the fan's
> rpm range, not the actual rpm. Your implementation is just
> confusing, including the example in the bindings. Valid values
> should be what the chip accepts, not some random value.
A fan would have some design maximum RPM depending on its mechanical
design and lifetime requirements. A controller would have some maximum
in terms of electrical pulse frequency or register bit sizes (depending
how RPM or pulse counts are exposed to s/w. That should all be implied
from the controller part and not in DT. It's the mechanical limits of
the fan we should be defining here.
> Really, I don't understand where you are going with this.
Certainly it needs more thought for different cases.
Rob
next prev parent reply other threads:[~2022-10-11 19:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 10:47 [PATCH v2 0/3] Add devicetree support for max6639 Naresh Solanki
2022-10-11 10:47 ` [PATCH v2 1/3] dt-bindings: hwmon: fan: Add fan binding to schema Naresh Solanki
2022-10-11 15:00 ` Guenter Roeck
2022-10-11 16:12 ` Naresh Solanki
2022-10-11 16:46 ` Guenter Roeck
2022-10-11 19:37 ` Rob Herring [this message]
2022-10-11 16:24 ` Krzysztof Kozlowski
2022-10-11 19:05 ` Rob Herring
2022-10-11 19:47 ` Naresh Solanki
2022-10-11 10:47 ` [PATCH v2 2/3] dt-bindings: hwmon: Add binding for max6639 Naresh Solanki
2022-10-11 16:28 ` Krzysztof Kozlowski
2022-10-11 16:54 ` Guenter Roeck
2022-10-11 10:47 ` [PATCH v2 3/3] hwmon: (max6639) Change from pdata to dt configuration Naresh Solanki
2022-10-11 16:57 ` 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=20221011193744.GA4051000-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=naresh.solanki@9elements.com \
--cc=patrick.rudolph@9elements.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;
as well as URLs for NNTP newsgroup(s).