From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: Flaviu Nistor <flaviu.nistor@gmail.com>,
Andy Shevchenko <andy@kernel.org>, Nuno Sa <nuno.sa@analog.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Daniel Baluta <daniel.baluta@nxp.com>,
Antoniu Miclaus <antoniu.miclaus@analog.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: iio: adc: ti,ads1015: Add label property
Date: Sat, 5 Sep 2026 02:56:12 +0100 [thread overview]
Message-ID: <20260905025612.09363f51@jic23-huawei> (raw)
In-Reply-To: <61d64649-603d-4a55-a789-babe655a2de8@baylibre.com>
On Thu, 3 Sep 2026 10:30:01 -0500
David Lechner <dlechner@baylibre.com> wrote:
> On 9/3/26 10:19 AM, Flaviu Nistor wrote:
> > On Wed, Sep 2, 2026 at 9:31 PM, David Lechner wrote:
> >> On 9/2/26 12:22 PM, Flaviu Nistor wrote:
> >>> Add support for an optional label property per channel similar to other adc
> >>> chips. This allows assigning distinct names for each channel which can
> >>> match the schematic signal name.
> >>>
> >>> Signed-off-by: Flaviu Nistor <flaviu.nistor@gmail.com>
> >>> ---
> >>> Documentation/devicetree/bindings/iio/adc/ti,ads1015.yaml | 6 ++++++
> >>> 1 file changed, 6 insertions(+)
> >>>
> >>> diff --git a/Documentation/devicetree/bindings/iio/adc/ti,ads1015.yaml b/Documentation/devicetree/bindings/iio/adc/ti,ads1015.yaml
> >>> index 718f633c6e04..777a75c21d7f 100644
> >>> --- a/Documentation/devicetree/bindings/iio/adc/ti,ads1015.yaml
> >>> +++ b/Documentation/devicetree/bindings/iio/adc/ti,ads1015.yaml
> >>> @@ -66,6 +66,11 @@ patternProperties:
> >>> - minimum: 0
> >>> maximum: 7
> >>>
> >>> + label:
> >>> + $ref: /schemas/types.yaml#/definitions/string
> >>> + description:
> >>> + A descriptive name for this channel, like "vcc_ram" or "CH3".
> >>> +
> >>
> >> Apparently this chip has quite old dt-bindings. Normally, we would have
> >> included adc.yaml to get this and other channel properties.
Quite a lot of bindings predate that generalization work :(
> >>
> >> And we would have used diff-channels and single-channel from that to
> >> describe which pins are associated with which channel rather than having
> >> a magic number for reg. And the ti,datarate looks suspicious as sampling
> >> frequency is usually we control at runtime.
> >>
> >> Anyway, none of that is really relevant to this patch. We'll see what
> >> Jonathan says about using adc.yaml here vs. adding a label property.
Given it's only a single property and label is pretty universal
I'm fine with just adding it here without the reference to adc.yaml.
DT binding reviewers may disagree however!
J
> >>
> >
> > Thanks for your feedback. I can also use:
> >
> > $ref: adc.yaml
> > unevaluatedProperties: false
> >
> > and move additionalProperties: false at the end of patternProperties block.
>
> It can't have both unevaluatedProperties and additionalProperties (hopefully
> the dt_binding_check would catch that).
>
> > Any other idea?
> >
> > Best regards,
> > Flaviu Nistor
> >
> >>> ti,gain:
> >>> $ref: /schemas/types.yaml#/definitions/uint32
> >>> minimum: 0
> >>> @@ -125,6 +130,7 @@ examples:
> >>> reg = <4>;
> >>> ti,gain = <3>;
> >>> ti,datarate = <5>;
> >>> + label = "CH3";
> >>> };
> >>> };
> >>> };
>
next prev parent reply other threads:[~2026-09-05 1:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 17:22 [PATCH v2 1/2] dt-bindings: iio: adc: ti,ads1015: Add label property Flaviu Nistor
2026-09-02 17:22 ` [PATCH v2 2/2] iio: adc: ti-ads1015: Add support for label Flaviu Nistor
2026-09-02 18:37 ` David Lechner
2026-09-03 6:18 ` Andy Shevchenko
2026-09-03 15:16 ` Flaviu Nistor
2026-09-03 15:28 ` David Lechner
2026-09-03 19:03 ` Andy Shevchenko
2026-09-05 2:01 ` Jonathan Cameron
2026-09-02 18:31 ` [PATCH v2 1/2] dt-bindings: iio: adc: ti,ads1015: Add label property David Lechner
2026-09-03 15:19 ` Flaviu Nistor
2026-09-03 15:30 ` David Lechner
2026-09-05 1:56 ` Jonathan Cameron [this message]
2026-09-05 1:54 ` 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=20260905025612.09363f51@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=flaviu.nistor@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--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