From: Krzysztof Kozlowski <krzk@kernel.org>
To: Bruno Thomsen <bruno.thomsen@gmail.com>
Cc: devicetree@vger.kernel.org, linux-hwmon@vger.kernel.org,
Guenter Roeck <linux@roeck-us.net>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: hwmon: ti,tmp401: Add label property
Date: Tue, 4 Aug 2026 09:59:34 +0200 [thread overview]
Message-ID: <20260804-rapid-heavenly-tench-4fbbbb@quoll> (raw)
In-Reply-To: <20260730133058.14731-1-bruno.thomsen@gmail.com>
On Thu, Jul 30, 2026 at 03:30:57PM +0200, Bruno Thomsen wrote:
> Add support for an optional channel label property similar to other
> hwmon devices.
No, you need to provide reasons. Other bindings need properties per
channel, but yours do not, so you do not have a valid case.
>
> Signed-off-by: Bruno Thomsen <bruno.thomsen@gmail.com>
> ---
> .../devicetree/bindings/hwmon/ti,tmp401.yaml | 58 +++++++++++++++++++
> 1 file changed, 58 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/hwmon/ti,tmp401.yaml b/Documentation/devicetree/bindings/hwmon/ti,tmp401.yaml
> index 0e8ddf0ad789..345ab6203a54 100644
> --- a/Documentation/devicetree/bindings/hwmon/ti,tmp401.yaml
> +++ b/Documentation/devicetree/bindings/hwmon/ti,tmp401.yaml
> @@ -30,6 +30,12 @@ properties:
> reg:
> maxItems: 1
>
> + '#address-cells':
> + const: 1
> +
> + '#size-cells':
Use consistent quotes.
> + const: 0
> +
> ti,extended-range-enable:
> description:
> When set, this sensor measures over extended temperature range.
> @@ -50,6 +56,26 @@ properties:
> minimum: 0
> maximum: 15
>
> +patternProperties:
> + "^channel@([0-2])$":
> + type: object
> + description: Represents channels of the device and their specific configuration.
> +
> + properties:
> + reg:
> + description: The channel number. 0 is local channel, 1-2 are remote channels.
> + items:
> + minimum: 0
> + maximum: 2
> +
> + label:
> + description: A descriptive name for this channel, like "ambient" or "psu".
> +
> + required:
> + - reg
> +
> + additionalProperties: false
> +
> allOf:
> - if:
> properties:
> @@ -72,6 +98,16 @@ allOf:
> properties:
> ti,beta-compensation: false
>
> + - if:
> + not:
> + properties:
> + compatible:
> + contains:
> + const: ti,tmp432
> + then:
> + properties:
> + channel@2: false
> +
> required:
> - compatible
> - reg
> @@ -102,3 +138,25 @@ examples:
> ti,beta-compensation = <0x7>;
> };
> };
> + - |
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
No need for new example, just grow existing.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-08-04 7:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 13:30 [PATCH 1/2] dt-bindings: hwmon: ti,tmp401: Add label property Bruno Thomsen
2026-07-30 13:30 ` [PATCH 2/2] hwmon: (tmp401) add channel label support Bruno Thomsen
2026-07-30 13:46 ` sashiko-bot
2026-07-30 13:42 ` [PATCH 1/2] dt-bindings: hwmon: ti,tmp401: Add label property sashiko-bot
2026-08-04 7:59 ` Krzysztof Kozlowski [this message]
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=20260804-rapid-heavenly-tench-4fbbbb@quoll \
--to=krzk@kernel.org \
--cc=bruno.thomsen@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh@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