Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <ukleinek@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Luiz Angelo Daros de Luca <luizluca@gmail.com>,
	 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>,
	 linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,  linux-pwm@vger.kernel.org
Subject: Re: [hwmon-next PATCH v4 3/4] hwmon: (adt7470) Expose fan control via PWM framework
Date: Wed, 29 Jul 2026 13:49:38 +0200	[thread overview]
Message-ID: <amnoV4Vlxmc5QgVC@monoceros> (raw)
In-Reply-To: <12dfeaae-f806-4adc-95f1-97fe10ef748e@roeck-us.net>

[-- Attachment #1: Type: text/plain, Size: 1748 bytes --]

On Tue, Jul 28, 2026 at 10:56:04PM -0700, Guenter Roeck wrote:
> On 7/28/26 21:46, Luiz Angelo Daros de Luca wrote:
> > The ADT7470 features four PWM outputs designed to control fans.
> > Previously, these were only accessible through the legacy hwmon
> > sysfs interface.
> > 
> > Expose the ADT7470 fan control lines through the generic PWM framework.
> > This allows generic PWM consumers described in Device Tree, such as
> > "pwm-fan", to use the device through the "#pwm-cells" property.  This is
> > particularly necessary for boards where the ADT7470 external temperature
> > sensors are not populated and the chip is used strictly as a fan
> > controller (e.g., Edgecore ECS-2100-52T switches). In such setups,
> > delegating control to the generic PWM subsystem allows the kernel's
> > thermal framework to manage the fans based on unrelated temperature
> > zones, such as internal SoC sensors.
> > 
> > When a PWM consumer applies a new PWM state, the driver automatically
> > switches the corresponding PWM channel to manual mode so that the
> > requested duty cycle takes effect. The duty cycle specified by the PWM
> > framework is internally converted to the 0-255 scale expected by the
> > hardware registers.
> > 
> > The legacy sysfs interface remains unaffected and operates in parallel.
> 
> No, I won't accept this. It has to be either or. A pwm channel modeled as pwm
> subsystem channel must not be visible via hwmon attributes.

I didn't look in detail, but maybe my red line is a bit more lax. IMHO
it's not OK to be able to modify a setting that results from pushing
hwmon knobs using PWM operations or vice-versa. Switching between
exclusive use at runtime is IMHO ok.

Best regards
Uwe

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2026-07-29 11:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29  4:46 [hwmon-next PATCH v4 0/4] hwmon: (adt7470) Add PWM provider and thermal sensor support Luiz Angelo Daros de Luca
2026-07-29  4:46 ` [hwmon-next PATCH v4 1/4] dt-bindings: hwmon: add adi,adt7470 Luiz Angelo Daros de Luca
2026-07-29  4:49   ` sashiko-bot
2026-07-29  4:46 ` [hwmon-next PATCH v4 2/4] hwmon: (adt7470) Add ADT7470_PWM_MAX macro Luiz Angelo Daros de Luca
2026-07-29  4:51   ` sashiko-bot
2026-07-29  4:46 ` [hwmon-next PATCH v4 3/4] hwmon: (adt7470) Expose fan control via PWM framework Luiz Angelo Daros de Luca
2026-07-29  5:00   ` sashiko-bot
2026-07-29  5:56   ` Guenter Roeck
2026-07-29 11:49     ` Uwe Kleine-König [this message]
2026-07-29 14:22       ` Guenter Roeck
2026-07-29 19:05         ` Luiz Angelo Daros de Luca
2026-07-29 20:23           ` Guenter Roeck
2026-07-29 21:34           ` Uwe Kleine-König
2026-07-29 11:47   ` Uwe Kleine-König
2026-07-29  4:46 ` [hwmon-next PATCH v4 4/4] hwmon: (adt7470) Add thermal zone sensor support Luiz Angelo Daros de Luca
2026-07-29  5:03   ` sashiko-bot

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=amnoV4Vlxmc5QgVC@monoceros \
    --to=ukleinek@kernel.org \
    --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=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=luizluca@gmail.com \
    --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