Devicetree
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Kyle Hsieh" <kylehsieh1995@gmail.com>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	"Mark Brown" <broonie@kernel.org>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] dt-bindings: iio: adc: ti,ads112c04: Add binding for ADS112C04
Date: Wed, 12 Aug 2026 17:03:49 +0100	[thread overview]
Message-ID: <20260812-kindness-compactly-2c3f5bb1f0a2@spud> (raw)
In-Reply-To: <20260812051107.204ae084@jic23-huawei>

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

On Wed, Aug 12, 2026 at 05:11:35AM +0100, Jonathan Cameron wrote:
> On Wed, 12 Aug 2026 10:53:57 +0800
> Kyle Hsieh <kylehsieh1995@gmail.com> wrote:
> 
> > Hi Conor,
> > 
> > On Wed, Aug 12, 2026 at 12:56 AM Conor Dooley <conor@kernel.org> wrote:
> > >
> > > On Tue, Aug 11, 2026 at 10:48:37AM +0800, Kyle Hsieh wrote:  
> > > > Add device tree binding documentation for Texas Instruments ADS112C04
> > > > I2C Analog-to-Digital Converters.
> > > >
> > > > These devices provide 4-channel, 16-bit delta-sigma ADCs with an I2C
> > > > interface, programmable gain amplifier (PGA), and data-ready (DRDY)
> > > > interrupt output.
> > > >
> > > > The binding uses child nodes to dynamically define the connected
> > > > single-ended or differential channels.
> > > >
> > > > Excitation current, burn-out current, and reference source properties
> > > > are also included to fully describe the chip's hardware capabilities,
> > > > aligned with the ti,ads112c14 binding conventions.
> > > >
> > > > Signed-off-by: Kyle Hsieh <kylehsieh1995@gmail.com>  
> > >  
> > > > +patternProperties:
> > > > +  "^channel@[0-9a-b]$":
> > > > +    $ref: adc.yaml
> > > > +    unevaluatedProperties: false
> > > > +    properties:
> > > > +      reg:
> > > > +        items:
> > > > +          - maximum: 11
> > > > +
> > > > +      single-channel:
> > > > +        maximum: 3  
> > >
> > > Can someone explain to me please why the maximum for this is 3 when reg
> > > goes up to 11? What do the additional reg entries beyond 3 represent?  
> > reg here is just an index for the channel node, not an input pin number.
> > The chip has 12 usable input MUX settings (8 differential pairs and 4
> > single-ended inputs), so at most 12 channel nodes can be described,
> > hence maximum 11.
> > 
> > single-channel refers to the physical analog input pin, and the chip
> > only has AIN0-AIN3, hence maximum 3.
> 
> Exactly as Kyle described - there is no right way to match reg to a property
> when we have mix of single-channel and diff-channels. Hence in this
> one corner case reg is just a magic number - though it may reflect
> ordering of channel acquisition I guess, though we've never documented
> that requirement in a binding.
> 
> We could restrict the differential to be only one direction which would
> give max 10 channels (4 single then 0-1, 0-2, 0-3, 1-2, 1-3, 2-3)
> but there isn't a huge advantage in doing so even though it is trivial
> for software to flip the sign if other direction is wanted.
> 
> Note that we don't actually expect to see all the channels configured,
> it can just be a useful to do things like single ended voltage at
> top of a resistor and differential across the resistor (to get
> allow current to be computed) - so it's not unheard to to mix
> and match.

This kinda thing is what I expected, I just was not sure.

I forget if I have to:
Acked-by: Conor Dooley <conor.dooley@microchip.com>
pw-bot: not-applicable

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

  reply	other threads:[~2026-08-12 16:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11  2:48 [PATCH v4 0/2] iio: adc: Add support for Texas Instruments ADS112C04 Kyle Hsieh
2026-08-11  2:48 ` [PATCH v4 1/2] dt-bindings: iio: adc: ti,ads112c04: Add binding for ADS112C04 Kyle Hsieh
2026-08-11 14:23   ` David Lechner
2026-08-11 16:56   ` Conor Dooley
2026-08-12  2:53     ` Kyle Hsieh
2026-08-12  4:11       ` Jonathan Cameron
2026-08-12 16:03         ` Conor Dooley [this message]
2026-08-11  2:48 ` [PATCH v4 2/2] iio: adc: ti-ads112c04: Add support for TI ADS112C04 Kyle Hsieh
2026-08-11  9:39   ` Andy Shevchenko
2026-08-12  2:58     ` Kyle Hsieh
2026-08-12  7:30       ` Andy Shevchenko
2026-08-12  8:51         ` Kyle Hsieh
2026-08-11 14:18   ` David Lechner
2026-08-12  1:25     ` Kyle Hsieh
2026-08-12  3:38     ` Kyle Hsieh
2026-08-12 13:26       ` David Lechner
2026-08-12  4:29   ` 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=20260812-kindness-compactly-2c3f5bb1f0a2@spud \
    --to=conor@kernel.org \
    --cc=andy@kernel.org \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=kylehsieh1995@gmail.com \
    --cc=lgirdwood@gmail.com \
    --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