From: Jonathan Cameron <jic23@kernel.org>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.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>,
"Olivier Moysan" <olivier.moysan@foss.st.com>,
"Mark Brown" <broonie@kernel.org>,
"Sebastian Reichel" <sebastian.reichel@collabora.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH v4 5/5] iio: adc: ad4080: add support for AD4880 dual-channel ADC
Date: Sat, 28 Feb 2026 19:10:04 +0000 [thread overview]
Message-ID: <20260228191004.35be7652@jic23-huawei> (raw)
In-Reply-To: <20260223162110.156746-6-antoniu.miclaus@analog.com>
On Mon, 23 Feb 2026 18:21:04 +0200
Antoniu Miclaus <antoniu.miclaus@analog.com> wrote:
> Add support for the AD4880, a dual-channel 20-bit 40MSPS SAR ADC with
> integrated fully differential amplifiers (FDA).
>
> The AD4880 has two independent ADC channels, each with its own SPI
> configuration interface. The driver uses spi_new_ancillary_device() to
> create an additional SPI device for the second channel, allowing both
> channels to share the same SPI bus with different chip selects.
>
> Reviewed-by: David Lechner <dlechner@baylibre.com>
> Reviewed-by: Nuno Sá <nuno.sa@analog.com>
> Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
Hi Antoniu
One minor question / comment below. Not particularly important
but as you will be doing a v5 anyway, seems reasonable to aks the
question.
> static int ad4080_properties_parse(struct ad4080_state *st)
> {
> - struct device *dev = regmap_get_device(st->regmap);
> + struct device *dev = regmap_get_device(st->regmap[0]);
>
> st->lvds_cnv_en = device_property_read_bool(dev, "adi,lvds-cnv-enable");
>
> @@ -602,6 +711,7 @@ static int ad4080_probe(struct spi_device *spi)
> struct device *dev = &spi->dev;
> struct ad4080_state *st;
> struct clk *clk;
> + unsigned int ch;
> int ret;
>
> indio_dev = devm_iio_device_alloc(&spi->dev, sizeof(*st));
> @@ -610,6 +720,10 @@ static int ad4080_probe(struct spi_device *spi)
>
> st = iio_priv(indio_dev);
>
> + st->info = spi_get_device_match_data(spi);
> + if (!st->info)
> + return -ENODEV;
> +
> ret = devm_regulator_bulk_get_enable(dev,
> ARRAY_SIZE(ad4080_power_supplies),
> ad4080_power_supplies);
> @@ -617,13 +731,27 @@ static int ad4080_probe(struct spi_device *spi)
> return dev_err_probe(dev, ret,
> "failed to get and enable supplies\n");
>
> - st->regmap = devm_regmap_init_spi(spi, &ad4080_regmap_config);
> - if (IS_ERR(st->regmap))
> - return PTR_ERR(st->regmap);
> -
> - st->info = spi_get_device_match_data(spi);
> - if (!st->info)
> - return -ENODEV;
Moving this up doesn't seem to be necessary. Am I missing a reason
st->info should be set earlier? If not I'd have left it down here simpl
to avoid the churn.
> + /* Setup primary SPI device (channel 0) */
> + st->spi[0] = spi;
> + st->regmap[0] = devm_regmap_init_spi(spi, &ad4080_regmap_config);
> + if (IS_ERR(st->regmap[0]))
> + return PTR_ERR(st->regmap[0]);
> +
> + /* Setup ancillary SPI devices for additional channels */
> + if (st->info->num_channels > 1) {
> + for (int i = 1; i < st->info->num_channels; i++) {
> + st->spi[i] = devm_spi_new_ancillary_device(spi,
> + spi_get_chipselect(spi, i));
> + if (IS_ERR(st->spi[i]))
> + return dev_err_probe(dev, PTR_ERR(st->spi[i]),
> + "failed to register ancillary device\n");
> +
> + st->regmap[i] = devm_regmap_init_spi(st->spi[i],
> + &ad4080_regmap_config);
> + if (IS_ERR(st->regmap[i]))
> + return PTR_ERR(st->regmap[i]);
> + }
> + }
next prev parent reply other threads:[~2026-02-28 19:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 16:20 [PATCH v4 0/5] iio: adc: ad4080: add support for AD4880 dual-channel ADC Antoniu Miclaus
2026-02-23 16:21 ` [PATCH v4 1/5] spi: allow ancillary devices to share parent's chip selects Antoniu Miclaus
2026-02-24 10:09 ` Andy Shevchenko
2026-02-24 11:12 ` Miclaus, Antoniu
2026-02-24 11:24 ` Andy Shevchenko
2026-02-24 11:41 ` Miclaus, Antoniu
2026-02-23 16:21 ` [PATCH v4 2/5] spi: add devm_spi_new_ancillary_device() Antoniu Miclaus
2026-02-23 16:21 ` [PATCH v4 3/5] iio: backend: add devm_iio_backend_get_by_index() Antoniu Miclaus
2026-02-24 10:16 ` Andy Shevchenko
2026-02-28 19:05 ` Jonathan Cameron
2026-02-23 16:21 ` [PATCH v4 4/5] dt-bindings: iio: adc: ad4080: add AD4880 support Antoniu Miclaus
2026-02-23 16:21 ` [PATCH v4 5/5] iio: adc: ad4080: add support for AD4880 dual-channel ADC Antoniu Miclaus
2026-02-24 10:24 ` Andy Shevchenko
2026-02-28 19:10 ` Jonathan Cameron [this message]
2026-02-25 19:09 ` (subset) [PATCH v4 0/5] " Mark Brown
2026-02-28 19:00 ` Jonathan Cameron
2026-02-28 21:35 ` Mark Brown
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=20260228191004.35be7652@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=olivier.moysan@foss.st.com \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.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