[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e7577165-436d-4335-943b-2187f7b95946@kernel.org>
Date: Wed, 13 Aug 2025 18:15:37 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Ben Collins <bcollins@...ter.com>, Jonathan Cameron <jic23@...nel.org>,
David Lechner <dlechner@...libre.com>, Nuno Sá
<nuno.sa@...log.com>, Andy Shevchenko <andy@...nel.org>,
Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Andrew Hepp <andrew.hepp@...pp.dev>
Cc: linux-iio@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/5] dt-bindings: iio: mcp9600: Add compatible for
microchip,mcp9601
On 13/08/2025 17:15, Ben Collins wrote:
> MCP9601 is a superset of MCP9600 and is supported by the driver.
There is no driver patch, so I cannot verify last part - about driver -
and I don't understand it. If it is already supported, doesn't it make
this patch redundant? Or did you wanted to say you are documenting
compatible being already used?
>
> Signed-off-by: Ben Collins <bcollins@...ter.com>
Where is the changelog? That's a v2.
No cover letter either...
> ---
> .../bindings/iio/temperature/microchip,mcp9600.yaml | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/iio/temperature/microchip,mcp9600.yaml b/Documentation/devicetree/bindings/iio/temperature/microchip,mcp9600.yaml
> index d2cafa38a5442..d8af0912ce886 100644
> --- a/Documentation/devicetree/bindings/iio/temperature/microchip,mcp9600.yaml
> +++ b/Documentation/devicetree/bindings/iio/temperature/microchip,mcp9600.yaml
> @@ -4,7 +4,7 @@
> $id: http://devicetree.org/schemas/iio/temperature/microchip,mcp9600.yaml#
> $schema: http://devicetree.org/meta-schemas/core.yaml#
>
> -title: Microchip MCP9600 thermocouple EMF converter
> +title: Microchip MCP9600 and similar thermocouple EMF converters
>
> maintainers:
> - Andrew Hepp <andrew.hepp@...pp.dev>
> @@ -14,7 +14,9 @@ description:
>
> properties:
> compatible:
> - const: microchip,mcp9600
> + enum:
> + - microchip,mcp9600
> + - microchip,mcp9601
If it is superset, why isn't this expressed with compatibility and fallback?
>
> reg:
> maxItems: 1
Best regards,
Krzysztof
Powered by blists - more mailing lists