mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Luiz Angelo Daros de Luca <luizluca@gmail.com>
Cc: "Krzysztof Kozlowski" <krzk@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Chris Packham" <chris.packham@alliedtelesis.co.nz>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Darrick J. Wong" <djwong@us.ibm.com>,
	"Uwe Kleine-König" <ukleinek@kernel.org>,
	linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org
Subject: Re: [hwmon-next PATCH v3 1/4] dt-bindings: hwmon: adi,adt7470
Date: Thu, 30 Jul 2026 14:37:01 -0700	[thread overview]
Message-ID: <a447e67e-ac2c-4b8c-bb96-b469d2a2d61a@roeck-us.net> (raw)
In-Reply-To: <CAJq09z5GL16qQ6smjEHsiYxpXn6MaBkibwsvSR66cJ4kEx1M6Q@mail.gmail.com>

On 7/30/26 14:11, Luiz Angelo Daros de Luca wrote:
the architecture, while I looked at the `emc2305` approach,
> delegating the actual fan management to the time-proven `pwm-fan`
> driver allows us to avoid reinventing the wheel (like cooling device
> registration and state management) inside the adt7470 driver. It also
> keeps the standard PWM consumer/provider relationship clear in the DT.
> It still feels strange that emc2305 declares #pwm-cells and its
> subdriver fans pwm properties and they do not work as a pwm
> controller. Other drivers, like aspeed-g6-pwm-tach (with similar

That is your opinion. #pwm-cells and pwms exists because it is mandated
by DT maintainers for configuring pwm properties. That does not have to
reflect the implementation: DT property guidance explicitly states
that properties must describe the hardware, not the implementation.
There is no mandate how to implement a specific driver (such as a fan
controller driver) because a specific binding exists. It is perfectly
valid to describe pwm properties of a fan controller using #pwm-cells
and pwms without modeling it as pwm controller (which actually mandates
support of the pwm subsystem or no good reason other than "because").

While you may consider the emc2305 approach inferior, I happen to
disagree. That is your personal opinion. For my part I consider it
inferior and overly complex having to involve another subsystem (pwm)
and another driver (pwm-fan) just to make the chip's pwm outputs
visible to the thermal subsystem as cooling devices.

Guenter


  reply	other threads:[~2026-07-30 21:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28  3:07 [hwmon-next PATCH v3 0/4] hwmon: (adt7470) Add PWM provider and thermal sensor support Luiz Angelo Daros de Luca
2026-07-28  3:07 ` [hwmon-next PATCH v3 1/4] dt-bindings: hwmon: adi,adt7470 Luiz Angelo Daros de Luca
2026-07-28  8:14   ` Krzysztof Kozlowski
2026-07-28  8:19     ` Krzysztof Kozlowski
2026-07-29  4:45     ` Luiz Angelo Daros de Luca
2026-07-30  6:17       ` Krzysztof Kozlowski
2026-07-30 15:38         ` Guenter Roeck
2026-07-30 21:11           ` Luiz Angelo Daros de Luca
2026-07-30 21:37             ` Guenter Roeck [this message]
2026-07-31  5:39               ` Uwe Kleine-König
2026-07-28  3:07 ` [hwmon-next PATCH v3 2/4] hwmon: (adt7470) Add ADT7470_PWM_MAX macro Luiz Angelo Daros de Luca
2026-07-28  3:07 ` [hwmon-next PATCH v3 3/4] hwmon: (adt7470) Expose fan control via PWM framework Luiz Angelo Daros de Luca
2026-07-28  3:07 ` [hwmon-next PATCH v3 4/4] hwmon: (adt7470) Add thermal zone sensor support Luiz Angelo Daros de Luca
2026-07-28  3:21 ` [hwmon-next PATCH v3 0/4] hwmon: (adt7470) Add PWM provider and thermal " Luiz Angelo Daros de Luca
2026-07-28  3:52   ` 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=a447e67e-ac2c-4b8c-bb96-b469d2a2d61a@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=akpm@linux-foundation.org \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=djwong@us.ibm.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=luizluca@gmail.com \
    --cc=robh@kernel.org \
    --cc=ukleinek@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

all inboxes | Powered by JetHome®