devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@mailbox.org>
To: Conor Dooley <conor@kernel.org>
Cc: linux-pwm@vger.kernel.org,
	"Uwe Kleine-König" <ukleinek@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: trivial-devices: Document Argon40 Fan HAT
Date: Tue, 17 Jun 2025 02:30:02 +0200	[thread overview]
Message-ID: <2aa6a582-cd5b-4a82-8dc3-66163250f086@mailbox.org> (raw)
In-Reply-To: <20250612-progress-envelope-c332c4cdd26d@spud>

On 6/12/25 6:32 PM, Conor Dooley wrote:
> On Wed, Jun 11, 2025 at 12:07:26AM +0200, Marek Vasut wrote:
>> Document trivial PWM on Argon40 Fan HAT, which is a RaspberryPi
>> blower fan hat which can be controlled over I2C.
>>
>> Signed-off-by: Marek Vasut <marek.vasut+renesas@mailbox.org>
> 
> I don't see how a pwm controller, with a fan connected to it, is a
> trivial device, sorry.
> PWM fans have their own pwm consumer binding too, so it feels wrong on
> two levels.
Hopefully fixed in V2 series with dedicated bindings, thanks.

  reply	other threads:[~2025-06-17  0:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10 22:07 [PATCH 1/3] dt-bindings: vendor-prefixes: Document Argon40 Marek Vasut
2025-06-10 22:07 ` [PATCH 2/3] dt-bindings: trivial-devices: Document Argon40 Fan HAT Marek Vasut
2025-06-12 16:32   ` Conor Dooley
2025-06-17  0:30     ` Marek Vasut [this message]
2025-06-10 22:07 ` [PATCH 3/3] pwm: argon-fan-hat: Add Argon40 Fan HAT support Marek Vasut
2025-06-11  5:55   ` Uwe Kleine-König
2025-06-17  0:07     ` Marek Vasut
2025-06-12 16:29 ` [PATCH 1/3] dt-bindings: vendor-prefixes: Document Argon40 Conor Dooley

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=2aa6a582-cd5b-4a82-8dc3-66163250f086@mailbox.org \
    --to=marek.vasut@mailbox.org \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).