devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: "Oleksij Rempel" <o.rempel@pengutronix.de>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Conor Dooley" <conor.dooley@microchip.com>,
	kernel@pengutronix.de, linux-kernel@vger.kernel.org,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	"Andy Shevchenko" <andy@kernel.org>,
	"Nuno Sá" <nuno.sa@analog.com>
Subject: Re: [PATCH v3 1/2] bindings: iio: adc: Add bindings for TI ADS131M0x ADCs
Date: Fri, 14 Nov 2025 17:13:16 +0000	[thread overview]
Message-ID: <20251114-scurvy-chewable-d68637504645@spud> (raw)
In-Reply-To: <ce727652-c00b-4779-97ea-0b9e4fc3477d@baylibre.com>

[-- Attachment #1: Type: text/plain, Size: 2166 bytes --]

On Fri, Nov 14, 2025 at 10:33:59AM -0600, David Lechner wrote:
> On 11/14/25 3:19 AM, Oleksij Rempel wrote:
> > Add device tree bindings documentation for the Texas Instruments
> > ADS131M0x analog-to-digital converters. This family includes the ADS131M02,
> > ADS131M03, ADS131M04, ADS131M06, and ADS131M08 variants.
> > 
> > These variants differ primarily in the number of supported channels
> > (2, 3, 4, 6, and 8, respectively), which requires separate compatible
> > strings to validate the channel nodes.
> > 
> > Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> > Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
> > ---
> > changes v3:
> > - Make channel@ regex patterns consistent
> > changes v2:
> > - Rename file to ti,ads131m02.yaml and update $id.
> > - Add supplies (avdd, dvdd, refin), interrupts, reset-gpios, and clock-names.
> > - Make avdd-supply, dvdd-supply, and clock-names required.
> > - Tighten channel validation logic for each device variant.
> > - Simplify channel description and reorder datasheet list.
> > - Update commit message to clarify device difference
> > ---
> 
> 
> ...
> 
> > +  - if:
> > +      # 32-pin devices: M06, M08
> > +      # These support both XTAL/CLKIN and optional REFIN.
> > +      properties:
> > +        compatible:
> > +          enum:
> > +            - ti,ads131m06
> > +            - ti,ads131m08
> > +    then:
> > +      properties:
> > +        clock-names:
> > +          description:
> > +            Indicates if a crystal oscillator (XTAL) or CMOS signal is connected
> > +            (CLKIN).
> > +          enum: [xtal, clkin]
> 
> 
> Usually, we want all possible properties declared at the top level and then
> only limit them by the conditional statements.
> 
> This makes it easier to see what all of the possibilities are. At first I
> thought clock-names had not been added.
> 
> 
> > +        refin-supply:
> > +          description: Optional external reference supply (REFIN).
> 
> refin-supply should be at the top level as well.

Oh ye, good shout. I didn't notice those inside the list of different
devices.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-11-14 17:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14  9:19 [PATCH v3 0/2] iio: adc: Add support for TI ADS131M0x ADCs Oleksij Rempel
2025-11-14  9:19 ` [PATCH v3 1/2] bindings: iio: adc: Add bindings " Oleksij Rempel
2025-11-14 16:33   ` David Lechner
2025-11-14 17:13     ` Conor Dooley [this message]
2025-11-14  9:20 ` [PATCH v3 2/2] iio: adc: Add TI ADS131M0x ADC driver Oleksij Rempel
2025-11-14 18:02   ` David Lechner
2025-11-14 18:24   ` Andy Shevchenko
2025-11-17 12:18     ` Oleksij Rempel
2025-11-15 18:04   ` 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=20251114-scurvy-chewable-d68637504645@spud \
    --to=conor@kernel.org \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=o.rempel@pengutronix.de \
    --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;
as well as URLs for NNTP newsgroup(s).