From: David Lechner <dlechner@baylibre.com>
To: Md Shofiqul Islam <shofiqtest@gmail.com>, linux-iio@vger.kernel.org
Cc: jic23@kernel.org, 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 2/2] iio: adc: ti-ads1298: add ADS1299 EEG ADC family support
Date: Tue, 30 Jun 2026 13:32:34 -0500 [thread overview]
Message-ID: <752a33ab-41a1-404d-8413-888cc1a8f446@baylibre.com> (raw)
In-Reply-To: <20260630140311.1473031-2-shofiqtest@gmail.com>
Please add a cover letter for multi-patch series.
On 6/30/26 9:03 AM, Md Shofiqul Islam wrote:
> The ADS1299, ADS1299-4 and ADS1299-6 are 8/4/6-channel, 24-bit
> biopotential (EEG) ADCs from Texas Instruments. They share the same
> SPI interface, command set and register map as the ADS1298 ECG family,
> making it straightforward to support them in this driver.
>
> Key differences from the ADS1298:
> - PGA gain range is 1/2/4/6/8/12/24 (vs 6/1/2/3/4/8/12 for ADS1298)
> - Internal voltage reference is always 2.4V (no 4V option)
> - Channel count is encoded differently in the ID register: bits [4:3]
> identify the ADS1299 family (both bits set), bits [1:0] encode the
> channel count as (bits + 2) * 2
>
> Detect the chip family in ads1298_init() by checking bits [4:3] of
> the ID register. Store the result in the is_ads1299 flag and use it
> to select the correct PGA table in ads1298_get_scale() and to skip
> the 4V reference option in the CONFIG3 initialisation.
>
> Signed-off-by: Md Shofiqul Islam <shofiqtest@gmail.com>
> ---
> drivers/iio/adc/ti-ads1298.c | 88 ++++++++++++++++++++++++++++--------
> 1 file changed, 69 insertions(+), 19 deletions(-)
>
> diff --git a/drivers/iio/adc/ti-ads1298.c b/drivers/iio/adc/ti-ads1298.c
> index 579200e06cbd..8c48a72e6c61 100644
> --- a/drivers/iio/adc/ti-ads1298.c
> +++ b/drivers/iio/adc/ti-ads1298.c
> @@ -1,6 +1,7 @@
> // SPDX-License-Identifier: GPL-2.0
> -/* TI ADS1298 chip family driver
> +/* TI ADS1298/ADS1299 biopotential ADC driver
> * Copyright (C) 2023 - 2024 Topic Embedded Products
> + * Copyright (C) 2026 Md Shofiqul Islam <shofiqtest@gmail.com>
> */
>
> #include <linux/bitfield.h>
> @@ -43,6 +44,20 @@
> #define ADS1298_MASK_ID_CHANNELS GENMASK(2, 0)
> #define ADS1298_ID_FAMILY_ADS129X 0x90
> #define ADS1298_ID_FAMILY_ADS129XR 0xd0
> +/*
> + * ADS1299 family is identified by bits [4:3] = 0b11. Bits [7:5] encode
> + * the silicon revision and vary between production lots, so only bits [4:3]
> + * are checked for family identification.
> + */
> +#define ADS1299_MASK_ID_FAMILY GENMASK(4, 3)
> +#define ADS1299_ID_FAMILY_EEG GENMASK(4, 3)
> +/*
> + * ADS1299 channel count is encoded in bits [1:0] of the ID register:
> + * 00 -> 4 channels (ADS1299-4)
> + * 01 -> 6 channels (ADS1299-6)
> + * 10 -> 8 channels (ADS1299)
> + */
> +#define ADS1299_MASK_ID_CHANNELS GENMASK(1, 0)
>
> #define ADS1298_REG_CONFIG1 0x01
> #define ADS1298_MASK_CONFIG1_HR BIT(7)
> @@ -101,6 +116,7 @@
> struct ads1298_private {
> const struct ads1298_chip_info *chip_info;
> struct spi_device *spi;
> + bool is_ads1299;
This is not how we handle chip-specific differences in IIO. Instead we
should add a new chip info struct and pass that as the data in the
module device tables.
This new struct should have a flag, e.g. `bool is_fixed_internal_ref` and
`const u8 *pga_settings` that is a pointer to the appropriate array.
> struct regulator *reg_avdd;
> struct regulator *reg_vref;
> struct clk *clk;
> @@ -276,7 +292,10 @@ static int ads1298_set_samp_freq(struct ads1298_private *priv, int val)
> cfg);
> }
>
> +/* ADS1298 PGA: register bits [6:4] -> gain (000=6, 001=1, 010=2, ...) */
> static const u8 ads1298_pga_settings[] = { 6, 1, 2, 3, 4, 8, 12 };
> +/* ADS1299 PGA: register bits [6:4] -> gain (000=1, 001=2, 010=4, ...) */
> +static const u8 ads1299_pga_settings[] = { 1, 2, 4, 6, 8, 12, 24 };
>
> static int ads1298_get_scale(struct ads1298_private *priv,
> int channel, int *val, int *val2)
> @@ -291,12 +310,15 @@ static int ads1298_get_scale(struct ads1298_private *priv,
> return ret;
>
> *val = ret / MILLI; /* Convert to millivolts */
> + } else if (priv->is_ads1299) {
So this would change to:
} else if (priv->info->is_fixed_internal_ref) {
> + /* ADS1299 internal reference is always 2.4V */
> + *val = 2400;
> } else {
> ret = regmap_read(priv->regmap, ADS1298_REG_CONFIG3, ®val);
> if (ret)
> return ret;
>
> - /* Reference in millivolts */
> + /* ADS1298 reference in millivolts: 2.4V or 4V */
> *val = regval & ADS1298_MASK_CONFIG3_VREF_4V ? 4000 : 2400;
> }
>
> @@ -304,7 +326,8 @@ static int ads1298_get_scale(struct ads1298_private *priv,
> if (ret)
> return ret;
>
> - gain = ads1298_pga_settings[FIELD_GET(ADS1298_MASK_CH_PGA, regval)];
> + gain = (priv->is_ads1299 ? ads1299_pga_settings : ads1298_pga_settings)
> + [FIELD_GET(ADS1298_MASK_CH_PGA, regval)];
And this would be:
gain = priv->info->pga_settings[FIELD_GET(ADS1298_MASK_CH_PGA, regval)];
> *val /= gain; /* Full scale is VREF / gain */
>
> *val2 = ADS1298_BITS_PER_SAMPLE - 1; /* Signed, hence the -1 */
> @@ -600,20 +623,39 @@ static int ads1298_init(struct iio_dev *indio_dev)
> if (ret)
> return ret;
>
> - /* Fill in name and channel count based on what the chip told us */
> - indio_dev->num_channels = 4 + 2 * (val & ADS1298_MASK_ID_CHANNELS);
> - switch (val & ADS1298_MASK_ID_FAMILY) {
> - case ADS1298_ID_FAMILY_ADS129X:
> - suffix = "";
> - break;
> - case ADS1298_ID_FAMILY_ADS129XR:
> - suffix = "r";
> - break;
> - default:
> - return dev_err_probe(dev, -ENODEV, "Unknown ID: 0x%x\n", val);
> + /*
> + * Detect chip family from the ID register. The ADS1299 EEG family
> + * is identified by bits [4:3] = 0b11; the ADS1298 ECG family uses
> + * bits [7:3] for family identification.
> + */
> + if (FIELD_GET(ADS1299_MASK_ID_FAMILY, val) == ADS1299_ID_FAMILY_EEG) {
> + /*
> + * ADS1299 family: channel count from bits [1:0].
> + * 00 -> 4ch, 01 -> 6ch, 10 -> 8ch.
> + */
> + priv->is_ads1299 = true;
> + indio_dev->num_channels =
> + (FIELD_GET(ADS1299_MASK_ID_CHANNELS, val) + 2) * 2;
Number of channels should come from the new chip info based on the compatible
string as well.
> + indio_dev->name = devm_kasprintf(dev, GFP_KERNEL, "ads1299%s",
> + indio_dev->num_channels == 4 ? "-4" :
> + indio_dev->num_channels == 6 ? "-6" : "");
Generally, we put the chip name in the chip info as well.
> + } else {
> + /* ADS1298 family: channel count from bits [2:0], name from family */
> + indio_dev->num_channels = 4 + 2 * (val & ADS1298_MASK_ID_CHANNELS);
> + switch (val & ADS1298_MASK_ID_FAMILY) {
> + case ADS1298_ID_FAMILY_ADS129X:
> + suffix = "";
> + break;
> + case ADS1298_ID_FAMILY_ADS129XR:
> + suffix = "r";
> + break;
> + default:
> + return dev_err_probe(dev, -ENODEV,
> + "Unknown ID: 0x%x\n", val);
> + }
> + indio_dev->name = devm_kasprintf(dev, GFP_KERNEL, "ads129%u%s",
> + indio_dev->num_channels, suffix);
> }
> - indio_dev->name = devm_kasprintf(dev, GFP_KERNEL, "ads129%u%s",
> - indio_dev->num_channels, suffix);
> if (!indio_dev->name)
> return -ENOMEM;
>
> @@ -621,8 +663,9 @@ static int ads1298_init(struct iio_dev *indio_dev)
> if (!priv->reg_vref) {
> /* Enable internal reference */
> val |= ADS1298_MASK_CONFIG3_PWR_REFBUF;
> - /* Use 4V VREF when power supply is at least 4.4V */
> - if (regulator_get_voltage(priv->reg_avdd) >= 4400000)
> + /* ADS1298 only: use 4V VREF when supply is at least 4.4V */
> + if (!priv->is_ads1299 &&
And of course use priv->info->is_fixed_internal_ref here too.
> + regulator_get_voltage(priv->reg_avdd) >= 4400000)
> val |= ADS1298_MASK_CONFIG3_VREF_4V;
> }
> return regmap_write(priv->regmap, ADS1298_REG_CONFIG3, val);
> @@ -739,12 +782,18 @@ static int ads1298_probe(struct spi_device *spi)
>
> static const struct spi_device_id ads1298_id[] = {
> { "ads1298" },
> + { "ads1299" },
> + { "ads1299-4" },
> + { "ads1299-6" },
> { }
> };
> MODULE_DEVICE_TABLE(spi, ads1298_id);
>
> static const struct of_device_id ads1298_of_table[] = {
> { .compatible = "ti,ads1298" },
> + { .compatible = "ti,ads1299" },
> + { .compatible = "ti,ads1299-4" },
> + { .compatible = "ti,ads1299-6" },
> { }
> };
> MODULE_DEVICE_TABLE(of, ads1298_of_table);
> @@ -760,5 +809,6 @@ static struct spi_driver ads1298_driver = {
> module_spi_driver(ads1298_driver);
>
> MODULE_AUTHOR("Mike Looijmans <mike.looijmans@topic.nl>");
> -MODULE_DESCRIPTION("TI ADS1298 ADC");
> +MODULE_AUTHOR("Md Shofiqul Islam <shofiqtest@gmail.com>");
> +MODULE_DESCRIPTION("TI ADS1298/ADS1299 biopotential ADC");
> MODULE_LICENSE("GPL");
next prev parent reply other threads:[~2026-06-30 18:32 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 [this message]
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
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=752a33ab-41a1-404d-8413-888cc1a8f446@baylibre.com \
--to=dlechner@baylibre.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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