From: "Nuno Sá" <noname.nuno@gmail.com>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>,
jic23@kernel.org, robh@kernel.org, conor+dt@kernel.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/6] iio: adc: ad4080: fix chip identification
Date: Tue, 30 Sep 2025 13:35:46 +0100 [thread overview]
Message-ID: <3c959b42a01d3af75fdf536fc3e3289a076953c3.camel@gmail.com> (raw)
In-Reply-To: <20250930103229.28696-1-antoniu.miclaus@analog.com>
Hi Antoniu,
I think that for a series like this you should include a cover letter...
On Tue, 2025-09-30 at 10:32 +0000, Antoniu Miclaus wrote:
> Fix AD4080 chip identification by using the correct 16-bit product ID
> (0x0050) instead of GENMASK(2, 0). Update the chip reading logic to
> use regmap_bulk_read to read both PRODUCT_ID_L and PRODUCT_ID_H
> registers and combine them into a 16-bit value.
>
> The original implementation was incorrectly reading only 3 bits,
> which would not correctly identify the AD4080 chip.
>
> Fixes: 6b31ba1811b6 ("iio: adc: ad4080: add driver support")
> Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
> ---
> changes in v2:
> - add the chip id handling into a separate commit.
> - use regmap_bulk_read.
> drivers/iio/adc/ad4080.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/adc/ad4080.c b/drivers/iio/adc/ad4080.c
> index 6e61787ed321..b80560aebe2d 100644
> --- a/drivers/iio/adc/ad4080.c
> +++ b/drivers/iio/adc/ad4080.c
> @@ -125,7 +125,7 @@
>
> /* Miscellaneous Definitions */
> #define
> AD4080_SPI_READ BIT(7)
> -#define AD4080_CHIP_ID GENMASK(2, 0)
> +#define AD4080_CHIP_ID 0x0050
>
> #define AD4080_LVDS_CNV_CLK_CNT_MAX 7
>
> @@ -458,10 +458,11 @@ static int ad4080_setup(struct iio_dev *indio_dev)
> if (ret)
> return ret;
>
> - ret = regmap_read(st->regmap, AD4080_REG_CHIP_TYPE, &id);
> + ret = regmap_bulk_read(st->regmap, AD4080_REG_PRODUCT_ID_L, &id, 2);
> if (ret)
> return ret;
>
> + id = get_unaligned_le16(&id);
Being id an 'unsigned int' I'm not really sure the above will work on big endian
machines as we should only populate the 2 MSB, right? But independent of that,
id is only being used in here so I would use proper __le16 (and u16) and
le16_to_cpu().
- Nuno Sá
> if (id != AD4080_CHIP_ID)
> dev_info(dev, "Unrecognized CHIP_ID 0x%X\n", id);
>
next prev parent reply other threads:[~2025-09-30 12:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 10:32 [PATCH v2 1/6] iio: adc: ad4080: fix chip identification Antoniu Miclaus
2025-09-30 10:32 ` [PATCH v2 2/6] iio: adc: ad4080: prepare driver for multi-part support Antoniu Miclaus
2025-09-30 12:36 ` Nuno Sá
2025-09-30 10:32 ` [PATCH v2 3/6] dt-bindings: iio: adc: adi,ad4080: add support for AD4084 Antoniu Miclaus
2025-09-30 18:53 ` Conor Dooley
2025-09-30 10:32 ` [PATCH v2 4/6] iio: adc: ad4080: " Antoniu Miclaus
2025-09-30 12:37 ` Nuno Sá
2025-09-30 10:32 ` [PATCH v2 5/6] dt-bindings: iio: adc: adi,ad4080: add support for AD4081 Antoniu Miclaus
2025-09-30 18:53 ` Conor Dooley
2025-09-30 10:32 ` [PATCH v2 6/6] iio: adc: ad4080: " Antoniu Miclaus
2025-09-30 12:38 ` Nuno Sá
2025-09-30 12:35 ` Nuno Sá [this message]
2025-10-04 14:22 ` [PATCH v2 1/6] iio: adc: ad4080: fix chip identification Jonathan Cameron
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=3c959b42a01d3af75fdf536fc3e3289a076953c3.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=antoniu.miclaus@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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