From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Andrew Hepp <andrew.hepp@ahepp.dev>,
devicetree@vger.kernel.org, linux-iio@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Jonathan Cameron <jic23@kernel.org>
Subject: Re: [PATCH v3 1/2] dt-bindings: iio: Add MCP9600 thermocouple EMF converter bindings
Date: Sat, 4 Mar 2023 12:20:58 +0100 [thread overview]
Message-ID: <73aa71ad-4cde-09d6-1af8-774701e330cd@linaro.org> (raw)
In-Reply-To: <20230304004109.78659-1-andrew.hepp@ahepp.dev>
On 04/03/2023 01:41, Andrew Hepp wrote:
> Add support for the MCP9600 thermocouple EMF converter.
>
> Datasheet: https://ww1.microchip.com/downloads/en/DeviceDoc/MCP960X-Data-Sheet-20005426.pdf
> Signed-off-by: Andrew Hepp <andrew.hepp@ahepp.dev>
Thank you for your patch. There is something to discuss/improve.
> +description: |
Drop '|'
> + https://ww1.microchip.com/downloads/en/DeviceDoc/MCP960X-Data-Sheet-20005426.pdf
> +
> +properties:
> + compatible:
> + const: microchip,mcp9600
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + minItems: 1
> + maxItems: 6
> +
> + interrupt-names:
> + minItems: 1
> + maxItems: 6
> + items:
> + enum:
The interrupts should be usually strictly ordered and you allow any
combinations. Why?
Why are they optional?
> + - open
> + - short
> + - alert1
> + - alert2
> + - alert3
> + - alert4
> +
> + thermocouple-type:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description:
> + Type of thermocouple (THERMOCOUPLE_TYPE_K if omitted).
> + Use defines in dt-bindings/iio/temperature/thermocouple.h.
> + Supported types are B, E, J, K, N, R, S, T.
> +
> + vdd-supply:
> + description: Regulator that provides power to the sensor.
> +
> +required:
> + - compatible
> + - reg
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/gpio/gpio.h>
No need for this header.
> + #include <dt-bindings/iio/temperature/thermocouple.h>
> + #include <dt-bindings/interrupt-controller/irq.h>
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + mcp9600@60 {
Node names should be generic, so temp-sensor, thermocouple or something
else matching the type.
https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
> + compatible = "microchip,mcp9600";
> + reg = <0x60>;
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-03-04 11:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 0:41 [PATCH v3 1/2] dt-bindings: iio: Add MCP9600 thermocouple EMF converter bindings Andrew Hepp
2023-03-04 0:41 ` [PATCH v3 2/2] iio: temperature: Add MCP9600 thermocouple EMF converter driver Andrew Hepp
2023-03-04 11:20 ` Krzysztof Kozlowski [this message]
2023-03-04 12:36 ` [PATCH v3 1/2] dt-bindings: iio: Add MCP9600 thermocouple EMF converter bindings Andrew Hepp
2023-03-04 13:06 ` Jonathan Cameron
2023-03-04 17:09 ` Jonathan Cameron
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=73aa71ad-4cde-09d6-1af8-774701e330cd@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andrew.hepp@ahepp.dev \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=robh+dt@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).