Devicetree
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Md Shofiqul Islam <shofiqtest@gmail.com>,
	linux-iio@vger.kernel.org, dlechner@baylibre.com,
	nuno.sa@analog.com, andy@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, mike.looijmans@topic.nl,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: iio: adc: ti,ads1298: add ADS1299 EEG ADC variants
Date: Wed, 1 Jul 2026 10:44:12 +0100	[thread overview]
Message-ID: <20260701-relic-urologist-87fd855061cf@spud> (raw)
In-Reply-To: <20260701001428.1670e3cc@jic23-huawei>

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

On Wed, Jul 01, 2026 at 12:14:28AM +0100, Jonathan Cameron wrote:
> On Tue, 30 Jun 2026 17:03:10 +0300
> Md Shofiqul Islam <shofiqtest@gmail.com> wrote:
> 
> > The ADS1299, ADS1299-4, and ADS1299-6 share the same SPI interface
> > and register map as the ADS1298 ECG ADC family but are designed for
> > EEG and biopotential measurement.  Key differences from ADS1298:
> > - PGA gain up to 24x (vs 12x for ADS1298)
> > - Internal reference is always 2.4V (no 4V option)
> > 
> > Add compatible strings and update the vref-supply description to
> > document the ADS1299 reference voltage behaviour.
> > 
> > Signed-off-by: Md Shofiqul Islam <shofiqtest@gmail.com>
> 
> >  
> >  maintainers:
> >    - Mike Looijmans <mike.looijmans@topic.nl>
> > @@ -17,6 +22,9 @@ properties:
> >    compatible:
> >      enum:
> >        - ti,ads1298
> > +      - ti,ads1299
> > +      - ti,ads1299-4
> > +      - ti,ads1299-6
> 
> As the channel count is a discoverable feature (encoded as a field in the
> ID Register, I think we can use just the one compatible).  FWIW it is
> nice to see a manufacturer making this discoverable!  I'd expect any
> future drop in parts to vary the other part of the ID, but this field
> should be respected - as such this doesn't fall into the stuff I've been
> discussing with DT maintainers about fallback compatibles needing to
> be specific (I'm way behind so not sure where that thread got to!)

I forget that thread too, but I think the difference is discoverable ID
versus discoverable capabilities. If you match on a generic compatible
with a new discoverable ID you've got no idea how to handle it. Matching
on an existing specific compatible with a new ID, you treat it as the
existing device. Matching on a generic compatible with the ability to
discover the channel count, you know what to do.


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

      reply	other threads:[~2026-07-01  9:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30 14:03 [PATCH 1/2] dt-bindings: iio: adc: ti,ads1298: add ADS1299 EEG ADC variants Md Shofiqul Islam
2026-06-30 14:03 ` [PATCH 2/2] iio: adc: ti-ads1298: add ADS1299 EEG ADC family support Md Shofiqul Islam
2026-06-30 14:15   ` sashiko-bot
2026-06-30 18:32   ` David Lechner
2026-07-01  8:52   ` Andy Shevchenko
2026-06-30 15:24 ` [PATCH 1/2] dt-bindings: iio: adc: ti,ads1298: add ADS1299 EEG ADC variants David Lechner
2026-06-30 23:09   ` Jonathan Cameron
2026-06-30 23:14 ` Jonathan Cameron
2026-07-01  9:44   ` Conor Dooley [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=20260701-relic-urologist-87fd855061cf@spud \
    --to=conor@kernel.org \
    --cc=andy@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=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.looijmans@topic.nl \
    --cc=nuno.sa@analog.com \
    --cc=robh@kernel.org \
    --cc=shofiqtest@gmail.com \
    /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