Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: "Kurt Borja" <kuurtb@gmail.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 03/10] iio: adc: add the ti-ads1262 driver
Date: Thu, 10 Sep 2026 03:43:05 +0100	[thread overview]
Message-ID: <20260910034305.7ac409ca@jic23-hlaptop> (raw)
In-Reply-To: <DL8IE3OUIUZ4.2SND39L7P03VL@gmail.com>


...

> >> +static int ads1262_fwnode_xlate(struct iio_dev *indio_dev,
> >> +				const struct fwnode_reference_args *iiospec)
> >> +{
> >> +	/* REVISIT: the auxiliary ADC (ADC2) is currently not supported */
> >> +	if (iiospec->nargs > 1 && iiospec->args[1])
> >> +		return -EINVAL;
> >> +
> >> +	if (!iiospec->nargs)
> >> +		return 0;
> >> +
> >> +	for (unsigned int i = 0; i < indio_dev->num_channels; i++) {  
> >
> > Won't this include the timestamp channel?  
> 
> Yes, I'll fix it.
> 
> >  
> >> +		if (indio_dev->channels[i].address == iiospec->args[0])  
> >
> > I don't think .address is the right thing to use here (it is coming from
> > reg in the devcietree). I would expect channel. Otherwise consumers in the
> > devicetree have to be away of how channels were assigned rather than picking
> > the datasheet channel number.  
> 
> I was very confused about what approach should I take here. All channels
> in this chip are actually differential. In that case should I make
> #io-channel-cells = 3 i.e. positive, negative and ADC?

Yes. Given the flexibility that makes sense.
You would need to sanity check the channel is actually present that
matches those choices though.

> 
> >
> > And the devicetree bindings should mention the monitor channel numbers (11 - 14).
> >  
> >> +			return i;
> >> +	}
> >> +
> >> +	return -EINVAL;
> >> +}
> >> +  
> >
> > ...


  reply	other threads:[~2026-09-10  2:43 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-28  6:38 [PATCH v4 00/10] iio: adc: Add TI ADS126X ADC family support Kurt Borja
2026-08-28  6:38 ` [PATCH v4 01/10] dt-bindings: adc: add excitation-current-chopping property Kurt Borja
2026-08-28 16:33   ` Conor Dooley
2026-08-28  6:38 ` [PATCH v4 02/10] dt-bindings: iio: adc: support the TI ADS126x ADC family Kurt Borja
2026-08-28 16:39   ` Conor Dooley
2026-08-30  1:57     ` Jonathan Cameron
2026-08-31 16:24       ` Conor Dooley
2026-09-01  3:01         ` Jonathan Cameron
2026-09-06 20:16     ` Kurt Borja
2026-08-30  1:53   ` Jonathan Cameron
2026-09-06 20:16     ` Kurt Borja
2026-08-31 19:44   ` David Lechner
2026-09-06 20:17     ` Kurt Borja
2026-08-28  6:38 ` [PATCH v4 03/10] iio: adc: add the ti-ads1262 driver Kurt Borja
2026-08-28  8:09   ` Andy Shevchenko
2026-09-06 20:15     ` Kurt Borja
2026-09-08 10:01       ` Andy Shevchenko
2026-08-31 20:22   ` David Lechner
2026-09-01  3:07     ` Jonathan Cameron
2026-09-06 20:17     ` Kurt Borja
2026-09-10  2:43       ` Jonathan Cameron [this message]
2026-09-10 21:38       ` David Lechner
2026-08-28  6:38 ` [PATCH v4 04/10] iio: adc: ti-ads1262: support per-channel sampling frequency Kurt Borja
2026-08-30  1:36   ` Jonathan Cameron
2026-09-06 20:16     ` Kurt Borja
2026-08-30  2:22   ` Jonathan Cameron
2026-09-06 20:17     ` Kurt Borja
2026-08-28  6:38 ` [PATCH v4 05/10] iio: adc: ti-ads1262: support per-channel reference and gain Kurt Borja
2026-08-28  6:38 ` [PATCH v4 06/10] iio: adc: ti-ads1262: support input chopping Kurt Borja
2026-08-28  6:38 ` [PATCH v4 07/10] iio: adc: ti-ads1262: support excitation currents Kurt Borja
2026-08-28  6:38 ` [PATCH v4 08/10] iio: adc: ti-ads1262: support triggered buffer sampling Kurt Borja
2026-08-28  6:38 ` [PATCH v4 09/10] iio: adc: ti-ads1262: support REFOUT and VBIAS regulators Kurt Borja
2026-08-28  6:38 ` [PATCH v4 10/10] iio: adc: ti-ads1262: support common mode supplies Kurt Borja

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=20260910034305.7ac409ca@jic23-hlaptop \
    --to=jic23@kernel.org \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuurtb@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