public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
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>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH v2 4/4] iio: adc: ad4080: add support for AD4880 dual-channel ADC
Date: Sat, 7 Feb 2026 15:04:40 +0000	[thread overview]
Message-ID: <20260207150440.46d83d48@jic23-huawei> (raw)
In-Reply-To: <8685e3e53667e82c7cdfd66ee6fb1ec3d3c009cd.1770393792.git.antoniu.miclaus@analog.com>

On Fri, 6 Feb 2026 18:07:16 +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.
> 
> Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
Hi Antoniu

Just one minor comment from me.

Thanks,

Jonathan

> ---
> Changes in v2:
>   - Use second reg entry instead of custom adi,aux-spi-cs property for
>     secondary channel chip select
>   - Use devm_iio_backend_get_by_index() instead of named backends for
>     multi-channel backend lookup
>   - Separate iio_info structures for single-channel (ad4080) and
>     multi-channel (ad4880) devices
>   - Keep filter_type as shared attribute for single-channel devices,
>     use per-channel only for AD4880
>   - Add separate AD4880_CHANNEL_DEFINE macro with per-channel attributes
> 
>  drivers/iio/adc/ad4080.c | 256 +++++++++++++++++++++++++++++++--------
>  1 file changed, 205 insertions(+), 51 deletions(-)
> 
> diff --git a/drivers/iio/adc/ad4080.c b/drivers/iio/adc/ad4080.c
> index 7cf3b6ed7940..2b26f8a4d548 100644
> --- a/drivers/iio/adc/ad4080.c
> +++ b/drivers/iio/adc/ad4080.c

>
> @@ -617,13 +736,37 @@ 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);
> +	/* 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]);
>  
> -	st->info = spi_get_device_match_data(spi);
> -	if (!st->info)
> -		return -ENODEV;
> +	/* Setup ancillary SPI device for additional channel (AD4880) */
> +	if (st->info->num_channels > 1) {

I wonder if this would be clearer as a loop?  When there is a 2 channel device
around, a 4 channels one often shows up later.

	for (int i = 1; i < st->info->num_channels; i++) {

> +		u32 reg[2];
> +
> +		ret = device_property_read_u32_array(dev, "reg", reg,
> +						     ARRAY_SIZE(reg));
> +		if (ret)
> +			return dev_err_probe(dev, ret,
> +					     "missing second reg entry for multi-channel device\n");
> +
> +		st->spi[1] = spi_new_ancillary_device(spi, reg[1]);
> +		if (IS_ERR(st->spi[1]))
> +			return dev_err_probe(dev, PTR_ERR(st->spi[1]),
> +					     "failed to register ancillary device\n");
> +
> +		ret = devm_add_action_or_reset(dev, ad4080_unregister_ancillary,
> +					       st->spi[1]);
> +		if (ret)
> +			return ret;
> +
> +		st->regmap[1] = devm_regmap_init_spi(st->spi[1],
> +						     &ad4080_regmap_config);
> +		if (IS_ERR(st->regmap[1]))
> +			return PTR_ERR(st->regmap[1]);
> +	}


  reply	other threads:[~2026-02-07 15:04 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-06 16:07 [PATCH v2 0/4] iio: adc: ad4080: add support for AD4880 dual-channel ADC Antoniu Miclaus
2026-02-06 16:07 ` [PATCH v2 1/4] spi: allow ancillary devices to share parent's chip selects Antoniu Miclaus
2026-02-07 18:09   ` David Lechner
2026-02-06 16:07 ` [PATCH v2 2/4] iio: backend: add devm_iio_backend_get_by_index() Antoniu Miclaus
2026-02-07 14:57   ` Jonathan Cameron
2026-02-07 18:13   ` David Lechner
2026-02-08  9:24   ` Nuno Sá
2026-02-09 15:28     ` David Lechner
2026-02-09 16:47       ` Nuno Sá
2026-02-09 17:48         ` Nuno Sá
2026-02-09 18:20         ` David Lechner
2026-02-06 16:07 ` [PATCH v2 3/4] dt-bindings: iio: adc: ad4080: add AD4880 support Antoniu Miclaus
2026-02-07 10:41   ` Krzysztof Kozlowski
2026-02-08  9:16     ` Nuno Sá
2026-02-08  9:20       ` Krzysztof Kozlowski
2026-02-09 16:43         ` Nuno Sá
2026-02-09 17:13           ` Krzysztof Kozlowski
2026-02-09 17:45             ` Nuno Sá
2026-02-06 16:07 ` [PATCH v2 4/4] iio: adc: ad4080: add support for AD4880 dual-channel ADC Antoniu Miclaus
2026-02-07 15:04   ` Jonathan Cameron [this message]
2026-02-07 18:29   ` David Lechner
2026-02-08  9:26   ` Nuno Sá
2026-02-08 12:50 ` [PATCH v2 0/4] " Andy Shevchenko
2026-02-14 16:08   ` Jonathan Cameron
2026-02-14 18:11     ` Andy Shevchenko
2026-02-14 18:31       ` David Lechner
2026-02-15  8:03         ` Andy Shevchenko
2026-02-15 23:16           ` David Lechner
2026-02-16  7:14             ` Andy Shevchenko
2026-02-16 18:53               ` David Lechner
2026-02-17  8:28                 ` Andy Shevchenko
2026-02-17 22:55                   ` David Lechner
2026-02-18 19:08                     ` Jonathan Cameron
2026-02-20 10:45                       ` Andy Shevchenko
2026-02-25 19:07 ` (subset) " 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=20260207150440.46d83d48@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 \
    /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