From: "Nuno Sá" <nuno.sa@analog.com>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>
Cc: Michael Hennerich <Michael.Hennerich@analog.com>,
Jonathan Cameron <jic23@kernel.org>,
David Lechner <dlechner@baylibre.com>,
linux@analog.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: adc: ad4080: enable address ascension for chip identification
Date: Tue, 22 Sep 2026 15:15:19 +0100 [thread overview]
Message-ID: <arKNNx-6RAXbus6R@nsa> (raw)
In-Reply-To: <20260922110958.1329-1-antoniu.miclaus@analog.com>
On Tue, Sep 22, 2026 at 02:09:58PM +0300, Antoniu Miclaus wrote:
> The two byte bulk read at AD4080_REG_PRODUCT_ID_L expects PRODUCT_ID_L
> followed by PRODUCT_ID_H. After a software reset the AD408x defaults to
> descending address mode, so the second byte comes from CHIP_TYPE (0x03)
> instead. CHIP_TYPE reads 0x07 on all AD408x parts, so an AD4080 reports
> 0x0750 rather than 0x0050 and every part logs "Unrecognized CHIP_ID".
>
> Set ADDR_ASC along with SDO_ENABLE before the read. This is the only
> multi byte transfer in the driver, so no other access is affected.
>
> Fixes: b66cddc8be72 ("iio: adc: ad4080: fix chip identification")
> Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
> ---
You could also just use change AD4080_REG_PRODUCT_ID_L to
AD4080_REG_PRODUCT_ID_H (maybe a slight smaller diff). Nut no strong
feelings:
Reviewed-by: Nuno Sá <nuno.sa@analog.com>
> drivers/iio/adc/ad4080.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iio/adc/ad4080.c b/drivers/iio/adc/ad4080.c
> index 4843ecdd91a8..4ed82aa42400 100644
> --- a/drivers/iio/adc/ad4080.c
> +++ b/drivers/iio/adc/ad4080.c
> @@ -710,7 +710,8 @@ static int ad4080_setup_channel(struct ad4080_state *st, unsigned int ch)
> return ret;
>
> ret = regmap_write(st->regmap[ch], AD4080_REG_INTERFACE_CONFIG_A,
> - AD4080_INTERFACE_CONFIG_A_SDO_ENABLE);
> + AD4080_INTERFACE_CONFIG_A_SDO_ENABLE |
> + AD4080_INTERFACE_CONFIG_A_ADDR_ASC);
> if (ret)
> return ret;
>
>
> base-commit: dceba8e581e3e8f475da0efbd7a73f3d9524ddd2
> --
> 2.43.0
>
prev parent reply other threads:[~2026-09-22 14:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 11:09 Antoniu Miclaus
2026-09-22 14:15 ` Nuno Sá [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=arKNNx-6RAXbus6R@nsa \
--to=nuno.sa@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=antoniu.miclaus@analog.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@analog.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®