From: Daniel Baluta <daniel.baluta@gmail.com>
To: Frank Li <Frank.li@nxp.com>, Krzysztof Kozlowski <krzk+dt@kernel.org>
Cc: florin.leotescu@oss.nxp.com, Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Michael Shych <michaelsh@nvidia.com>,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, viorel.suman@nxp.com,
carlos.song@nxp.com, linux-arm-kernel@lists.infradead.org,
imx@lists.linux.dev, festevam@gmail.com,
Florin Leotescu <florin.leotescu@nxp.com>
Subject: Re: [PATCH v3 1/3] dt-bindings: hwmon: Add Microchip emc2305 yaml schema
Date: Wed, 5 Mar 2025 14:47:45 +0200 [thread overview]
Message-ID: <CAEnQRZCT4vfFBApv+C3Wp17Fk0-Rwx36h4eCTTygaXFYFipEGg@mail.gmail.com> (raw)
In-Reply-To: <Z8cp1xoIXT8lgD8T@lizhi-Precision-Tower-5810>
Hello Frank, Conor, Krzysztof,
Thanks a lot for your comments and help.
In this initial patchseries we only add minimal OF support and
introduce a minimal binding.
> How did you pickup the maintainer entry?
We got the author of the first commit for
See 0d8400c5a2ce ("hwmon: (emc2305) add support for EMC2301/2/3/5 RPM-based")
> If only one reg You can go through trivial-devices.yaml
This is not a trivial device as we will add some specific properties
with our next patches
(e.g polarity etc)
> Missing descriptions of the fans, no?
> missing $ref to fan-controller schema.
Do we need to add this now? As this is only the minimal binding
support. We want to add that
in a follow up patch when we go into specifics.
> The emc2301 label here can be dropped, it is not used.
Will fix.
> The nodename should be "fan-controller", not pwm here I guess.
Sure, will fix.
On Tue, Mar 4, 2025 at 6:56 PM Frank Li <Frank.li@nxp.com> wrote:
>
> On Tue, Mar 04, 2025 at 06:21:34PM +0200, florin.leotescu@oss.nxp.com wrote:
> > From: Florin Leotescu <florin.leotescu@nxp.com>
> >
> > Introduce yaml schema for Microchip emc2305 pwm fan controller.
> >
> > Signed-off-by: Florin Leotescu <florin.leotescu@nxp.com>
> > ---
> > .../bindings/hwmon/microchip,emc2305.yaml | 43 +++++++++++++++++++
> > 1 file changed, 43 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/hwmon/microchip,emc2305.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/hwmon/microchip,emc2305.yaml b/Documentation/devicetree/bindings/hwmon/microchip,emc2305.yaml
> > new file mode 100644
> > index 000000000000..cac0075a65bb
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/hwmon/microchip,emc2305.yaml
> > @@ -0,0 +1,43 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/hwmon/microchip,emc2305.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Microchip EMC2305 SMBus compliant PWM fan controller
> > +
> > +maintainers:
> > + - Michael Shych <michaelsh@nvidia.com>
>
> who is it? look like not Microchip and hwmon maintainer.
>
> > +
> > +description: |
>
> Needn't |
>
> > + Microchip EMC2301/2/3/5 pwm controller which supports up
> > + to five programmable fan control circuits
> > +
> > +properties:
> > + compatible:
> > + enum:
> > + - microchip,emc2301
> > + - microchip,emc2302
> > + - microchip,emc2303
> > + - microchip,emc2305
>
> According to your driver code look like all compatible with microchip,emc2301
>
> oneOf:
> - enum:
> - microchip,emc2301
> - items:
> - enum:
> - microchip,emc2302
> - microchip,emc2303
> - microchip,emc2305
> - const: microchip,emc2301
>
> So your driver just need one "microchip,emc2301" compatible string.
>
> > +
> > + reg:
> > + maxItems: 1
> > +
> > +required:
> > + - compatible
> > + - reg
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + i2c {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > +
> > + emc2301: pwm@2f {
> > + compatible = "microchip,emc2301";
> > + reg = <0x2f>;
>
> If only one reg:
> You can go through trivial-devices.yaml
>
> Frank
>
> > + };
> > + };
> > --
> > 2.34.1
> >
>
next prev parent reply other threads:[~2025-03-05 12:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 16:21 [PATCH v3 0/3] Add OF support for Microchip emc2305 fan controller florin.leotescu
2025-03-04 16:21 ` [PATCH v3 1/3] dt-bindings: hwmon: Add Microchip emc2305 yaml schema florin.leotescu
2025-03-04 16:27 ` Frank Li
2025-03-05 12:47 ` Daniel Baluta [this message]
2025-03-05 14:49 ` Florin Leotescu (OSS)
2025-03-04 16:29 ` Conor Dooley
2025-03-04 16:31 ` Krzysztof Kozlowski
2025-03-04 16:32 ` Krzysztof Kozlowski
2025-03-04 16:33 ` Krzysztof Kozlowski
2025-03-04 16:21 ` [PATCH v3 2/3] hwmon: emc2305: Add OF support florin.leotescu
2025-03-04 16:27 ` Frank Li
2025-03-04 16:21 ` [PATCH v3 3/3] hwmon: emc2305: Use devm_thermal_of_cooling_device_register florin.leotescu
2025-03-04 16:33 ` Frank Li
2025-03-05 16:54 ` 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=CAEnQRZCT4vfFBApv+C3Wp17Fk0-Rwx36h4eCTTygaXFYFipEGg@mail.gmail.com \
--to=daniel.baluta@gmail.com \
--cc=Frank.li@nxp.com \
--cc=carlos.song@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=florin.leotescu@nxp.com \
--cc=florin.leotescu@oss.nxp.com \
--cc=imx@lists.linux.dev \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=michaelsh@nvidia.com \
--cc=robh@kernel.org \
--cc=viorel.suman@nxp.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