From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Stephan Costa Barros <stephanbrrs8@gmail.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"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>,
"Mike Looijmans" <mike.looijmans@topic.nl>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] iio: adc: add TI ADS1299
Date: Mon, 19 Oct 2026 13:16:58 +0300 [thread overview]
Message-ID: <atXuGv3esexdRJ4e@ashevche-desk.local> (raw)
In-Reply-To: <20261019001247.483005-1-stephanbrrs8@gmail.com>
On Sun, Oct 18, 2026 at 09:12:45PM -0300, Stephan Costa Barros wrote:
> This series adds a driver for the TI ADS1299 family (ADS1299, ADS1299-6
> and ADS1299-4): 24-bit, simultaneous-sampling biopotential front-ends
> for EEG, on SPI.
Why a brand new driver?
> This first version keeps to the generic IIO ABI: raw reads, the gain of
> each channel's PGA through its scale, the sampling frequency, and a
> kfifo buffer fed from the DRDY interrupt with a software timestamp.
>
> The part has more, which I would like to add in follow-up series, each
> with its own ABI discussion: SRB1 and SRB2 reference routing, the bias
> drive amplifier, lead-off detection (through IIO_EV_TYPE_FAULT and
> IIO_EV_DIR_FAULT_OPENWIRE), the internal test signal, the temperature
> sensor and supply monitors, GPIO1 to GPIO4 as a gpiochip, the CLK pin
> as a clock output, and daisy chains. The binding already describes the
> hardware for those.
>
> A question on structure. The driver started from ti-ads1298.c, and in
> this subset the two are close. What differs here is the PGA gain table
> (1 to 24 against 1 to 12 with 3), the data rates (no high-resolution
> mode), the fixed 4.5 V internal reference, the ID register layout and
> the 4 and 6 channel variants; above 0x14 the register maps also part
> (MISC1 and MISC2 here, PACE, RESP and WCT on the ADS1298). Most of what
> would follow, SRB1 and SRB2, the bias drive and lead-off on every
> channel, is specific to the ADS1299, so I kept a separate driver. If you
> would rather have the ADS1299 as a variant in ti-ads1298, I can rework
> it that way.
Okay, I think you can try to rework this as a series on top of the existing
code. I can't easily see if the above difference warrants a brand new driver.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-10-19 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 0:12 Stephan Costa Barros
2026-10-19 0:12 ` [PATCH 1/2] dt-bindings: " Stephan Costa Barros
2026-10-19 0:12 ` [PATCH 2/2] iio: adc: ti-ads1299: add driver for " Stephan Costa Barros
2026-10-19 7:03 ` Uwe Kleine-König
2026-10-19 10:16 ` Andy Shevchenko [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=atXuGv3esexdRJ4e@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--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=stephanbrrs8@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
all inboxes | Powered by JetHome®