All of lore.kernel.org
 help / color / mirror / Atom feed
From: sylv <sylv@sylv.io>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-hwmon@vger.kernel.org,
	Patrick Rudolph <patrick.rudolph@9elements.com>,
	Jean Delvare <jdelvare@suse.com>,
	Rob Herring <robh+dt@kernel.org>,
	Roland Stigge <stigge@antcom.de>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v3 3/4] dt-bindings: hwmon: Add binding for max6639
Date: Thu, 27 Jan 2022 15:49:08 +0100	[thread overview]
Message-ID: <9f1f48ac68f0afed92d7fa114fb8af74c81aa581.camel@sylv.io> (raw)
In-Reply-To: <20220125050804.GA361944@roeck-us.net>

On Mon, 2022-01-24 at 21:08 -0800, Guenter Roeck wrote:
> On Wed, Jan 19, 2022 at 10:53:54AM +0100, Marcello Sylvester Bauer
> wrote:
> > Add Devicetree binding documentation for Maxim MAX6639 temperature
> > monitor with PWM fan-speed controller.
> > 
> > The devicetree documentation for the SD3078 device tree.
> > 
> > Signed-off-by: Marcello Sylvester Bauer <sylv@sylv.io>
> > ---
> >  .../bindings/hwmon/maxim,max6639.yaml         | 112
> > ++++++++++++++++++
> >  1 file changed, 112 insertions(+)
> >  create mode 100644
> > Documentation/devicetree/bindings/hwmon/maxim,max6639.yaml
> > 
> > diff --git
> > a/Documentation/devicetree/bindings/hwmon/maxim,max6639.yaml
> > b/Documentation/devicetree/bindings/hwmon/maxim,max6639.yaml
> > new file mode 100644
> > index 000000000000..7093cbeba44b
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/hwmon/maxim,max6639.yaml
> > @@ -0,0 +1,112 @@
> > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +
> > +$id: http://devicetree.org/schemas/hwmon/maxim,max6639.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Maxim max6639
> > +
> > +maintainers:
> > +  - Roland Stigge <stigge@antcom.de>
> > +
> > +description: |
> > +  The MAX6639 is a 2-channel temperature monitor with dual,
> > automatic, PWM
> > +  fan-speed controller.  It monitors its own temperature and one
> > external
> > +  diode-connected transistor or the temperatures of two external
> > diode-connected
> > +  transistors, typically available in CPUs, FPGAs, or GPUs.
> > +
> > +  Datasheets:
> > +   
> > https://datasheets.maximintegrated.com/en/ds/MAX6639-MAX6639F.pdf
> > +
> > +properties:
> > +  compatible:
> > +    enum:
> > +      - maxim,max6639
> > +
> > +  reg:
> > +    maxItems: 1
> > +
> > +  '#address-cells':
> > +    const: 1
> > +
> > +  '#size-cells':
> > +    const: 0
> > +
> > +required:
> > +  - compatible
> > +  - reg
> > +  - "channel@0"
> > +  - "channel@1"
> > +
> > +additionalProperties: false
> > +
> > +patternProperties:
> > +  "^channel@[0-1]$":
> > +    type: object
> > +    description: |
> > +      Represents the two fans and their specific configuration.
> > +
> > +    properties:
> > +      reg:
> > +        description: |
> > +          The fan number.
> > +        items:
> > +          minimum: 0
> > +          maximum: 1
> > +
> > +      pwm-polarity:
> > +        $ref: /schemas/types.yaml#/definitions/uint32
> > +        enum: [0, 1]
> > +        description:
> > +          PWM output is low at 100% duty cycle when this bit is
> > set to zero. PWM
> > +          output is high at 100% duty cycle when this bit is set
> > to 1.
> > +
> > +      pulses-per-revolution:
> > +        $ref: /schemas/types.yaml#/definitions/uint32
> > +        enum: [1, 2, 3, 4]
> > +        description:
> > +          Value specifying the number of pulses per revolution of
> > the controlled
> > +          FAN.
> > +
> 
> I think the above two properties should be optional.
> pulses-per-revolution is 2 for almost all fans out there,
> and pwm polarity is positive almost all the time.

makes sense. I guess I'll keep the default values like before and
also set rpm-range (resp. rpm-max) to 4000.

> 
> > +      rpm-range:
> > +        $ref: /schemas/types.yaml#/definitions/uint32
> > +        enum: [2000, 4000, 8000, 16000]
> > +        description:
> > +          Scales the tachometer counter by setting the maximum
> > (full-scale) value
> > +          of the RPM range.
> > +
> Isn't this the maximum rpm ? Using the term "range" seems to be
> a bit misleading.

Yeah, the data sheet explicitly calls this register "rpm fan range".
But since this is not a vendor specific property and the purpose is
to set a maximum rpm value, it should rather be called "rpm-max".

Thanks!

Marcello

> 
> > +    required:
> > +      - reg
> > +      - pwm-polarity
> > +      - pulses-per-revolution
> > +      - rpm-range
> > +
> > +examples:
> > +  - |
> > +    i2c {
> > +      #address-cells = <1>;
> > +      #size-cells = <0>;
> > +
> > +      max6639@10 {
> > +        compatible = "maxim,max6639";
> > +        reg = <0x10>;
> > +        #address-cells = <1>;
> > +        #size-cells = <0>;
> > +
> > +        channel@0 {
> > +          reg = <0x0>;
> > +          pwm-polarity = <1>;
> > +          pulses-per-revolution = <2>;
> > +          rpm-range = <4000>;
> > +        };
> > +
> > +        channel@1 {
> > +          reg = <0x1>;
> > +          pwm-polarity = <1>;
> > +          pulses-per-revolution = <2>;
> > +          rpm-range = <4000>;
> > +        };
> > +      };
> > +    };
> > +...


  reply	other threads:[~2022-01-27 14:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19  9:53 [PATCH v3 0/4] Add max6639 regulator and devicetree support Marcello Sylvester Bauer
2022-01-19  9:53 ` [PATCH v3 1/4] hwmon: (max6639) Update Datasheet URL Marcello Sylvester Bauer
2022-01-19  9:53 ` [PATCH v3 2/4] hwmon: (max6639) Add regulator support Marcello Sylvester Bauer
2022-01-19  9:53 ` [PATCH v3 3/4] dt-bindings: hwmon: Add binding for max6639 Marcello Sylvester Bauer
2022-01-25  5:08   ` Guenter Roeck
2022-01-27 14:49     ` sylv [this message]
2022-01-19  9:53 ` [PATCH v3 4/4] hwmon: (max6639) Change from pdata to dt configuration Marcello Sylvester Bauer

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=9f1f48ac68f0afed92d7fa114fb8af74c81aa581.camel@sylv.io \
    --to=sylv@sylv.io \
    --cc=devicetree@vger.kernel.org \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=patrick.rudolph@9elements.com \
    --cc=robh+dt@kernel.org \
    --cc=stigge@antcom.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.