public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nuno Sá" <noname.nuno@gmail.com>
To: "Antoniu Miclaus" <antoniu.miclaus@analog.com>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"Michael Hennerich" <Michael.Hennerich@analog.com>,
	"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>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/6] iio: adc: ad4080: add support for AD4085
Date: Sun, 08 Feb 2026 09:36:26 +0000	[thread overview]
Message-ID: <8f0d63a6d2a4cfca52ea6c80595a2f1eda3713cf.camel@gmail.com> (raw)
In-Reply-To: <587dbc9c21b49c7d99b6b5b8dad419fad415e040.1770382796.git.antoniu.miclaus@analog.com>

On Fri, 2026-02-06 at 15:08 +0200, Antoniu Miclaus wrote:
> Add support for AD4085 16-bit SAR ADC. The AD4085 has the same
> resolution as AD4084 (16-bit) but differs in LVDS CNV clock count
> maximum (8 vs 2).
> 
> Changes:
> - Add AD4085_CHIP_ID definition (0x0055)
> - Create ad4085_channel with 16-bit resolution and 16-bit storage
> - Add ad4085_chip_info with lvds_cnv_clk_cnt_max = 8
> - Register AD4085 in device ID and OF match tables
> 
> Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
> ---
I do agree with Andy that the commit is too verbose. With that handled:

Reviewed-by: Nuno Sá <nuno.sa@analog.com>

>  drivers/iio/adc/ad4080.c | 15 +++++++++++++++
>  1 file changed, 15 insertions(+)
> 
> diff --git a/drivers/iio/adc/ad4080.c b/drivers/iio/adc/ad4080.c
> index 7cbbe284dea7..728df626f09e 100644
> --- a/drivers/iio/adc/ad4080.c
> +++ b/drivers/iio/adc/ad4080.c
> @@ -130,6 +130,7 @@
>  #define AD4082_CHIP_ID						0x0052
>  #define AD4083_CHIP_ID						0x0053
>  #define AD4084_CHIP_ID						0x0054
> +#define AD4085_CHIP_ID						0x0055
>  #define AD4086_CHIP_ID						0x0056
>  #define AD4087_CHIP_ID						0x0057
>  
> @@ -449,6 +450,8 @@ static const struct iio_chan_spec ad4083_channel =
> AD4080_CHANNEL_DEFINE(16, 16)
>  
>  static const struct iio_chan_spec ad4084_channel = AD4080_CHANNEL_DEFINE(16, 16);
>  
> +static const struct iio_chan_spec ad4085_channel = AD4080_CHANNEL_DEFINE(16, 16);
> +
>  static const struct iio_chan_spec ad4086_channel = AD4080_CHANNEL_DEFINE(14, 16);
>  
>  static const struct iio_chan_spec ad4087_channel = AD4080_CHANNEL_DEFINE(14, 16);
> @@ -503,6 +506,16 @@ static const struct ad4080_chip_info ad4084_chip_info = {
>  	.lvds_cnv_clk_cnt_max = 2,
>  };
>  
> +static const struct ad4080_chip_info ad4085_chip_info = {
> +	.name = "ad4085",
> +	.product_id = AD4085_CHIP_ID,
> +	.scale_table = ad4080_scale_table,
> +	.num_scales = ARRAY_SIZE(ad4080_scale_table),
> +	.num_channels = 1,
> +	.channels = &ad4085_channel,
> +	.lvds_cnv_clk_cnt_max = 8,
> +};
> +
>  static const struct ad4080_chip_info ad4086_chip_info = {
>  	.name = "ad4086",
>  	.product_id = AD4086_CHIP_ID,
> @@ -682,6 +695,7 @@ static const struct spi_device_id ad4080_id[] = {
>  	{ "ad4082", (kernel_ulong_t)&ad4082_chip_info },
>  	{ "ad4083", (kernel_ulong_t)&ad4083_chip_info },
>  	{ "ad4084", (kernel_ulong_t)&ad4084_chip_info },
> +	{ "ad4085", (kernel_ulong_t)&ad4085_chip_info },
>  	{ "ad4086", (kernel_ulong_t)&ad4086_chip_info },
>  	{ "ad4087", (kernel_ulong_t)&ad4087_chip_info },
>  	{ }
> @@ -694,6 +708,7 @@ static const struct of_device_id ad4080_of_match[] = {
>  	{ .compatible = "adi,ad4082", &ad4082_chip_info },
>  	{ .compatible = "adi,ad4083", &ad4083_chip_info },
>  	{ .compatible = "adi,ad4084", &ad4084_chip_info },
> +	{ .compatible = "adi,ad4085", &ad4085_chip_info },
>  	{ .compatible = "adi,ad4086", &ad4086_chip_info },
>  	{ .compatible = "adi,ad4087", &ad4087_chip_info },
>  	{ }

  reply	other threads:[~2026-02-08  9:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-06 13:08 [PATCH 0/6] iio: adc: ad4080: add support for AD4082, AD4085 and AD4088 Antoniu Miclaus
2026-02-06 13:08 ` [PATCH 1/6] dt-bindings: iio: adc: adi,ad4080: add support for AD4082 Antoniu Miclaus
2026-02-06 13:08 ` [PATCH 2/6] iio: adc: ad4080: " Antoniu Miclaus
2026-02-06 13:56   ` Andy Shevchenko
2026-02-06 13:57     ` Andy Shevchenko
2026-02-08  9:37   ` Nuno Sá
2026-02-06 13:08 ` [PATCH 3/6] dt-bindings: iio: adc: adi,ad4080: add support for AD4085 Antoniu Miclaus
2026-02-07 10:52   ` Krzysztof Kozlowski
2026-02-07 15:10     ` Jonathan Cameron
2026-02-16  9:23     ` Miclaus, Antoniu
2026-02-16 10:09       ` Krzysztof Kozlowski
2026-02-06 13:08 ` [PATCH 4/6] iio: adc: ad4080: " Antoniu Miclaus
2026-02-08  9:36   ` Nuno Sá [this message]
2026-02-06 13:08 ` [PATCH 5/6] dt-bindings: iio: adc: adi,ad4080: add support for AD4088 Antoniu Miclaus
2026-02-07 10:53   ` Krzysztof Kozlowski
2026-02-06 13:08 ` [PATCH 6/6] iio: adc: ad4080: " Antoniu Miclaus
2026-02-08  9:36   ` Nuno Sá

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=8f0d63a6d2a4cfca52ea6c80595a2f1eda3713cf.camel@gmail.com \
    --to=noname.nuno@gmail.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy@kernel.org \
    --cc=antoniu.miclaus@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.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