From: Jonathan Cameron <jic23@kernel.org>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"David Heidelberg" <david@ixit.cz>,
linux-iio@vger.kernel.org (open list:IIO SUBSYSTEM AND DRIVERS),
linux-kernel@vger.kernel.org (open list)
Subject: Re: [PATCH] iio: light: al3010: read both ALS ADC registers again
Date: Thu, 21 May 2026 12:23:50 +0100 [thread overview]
Message-ID: <20260521122350.1d705c8f@jic23-huawei> (raw)
In-Reply-To: <20260520175855.538098-1-grandmaster@al2klimov.de>
On Wed, 20 May 2026 19:58:49 +0200
"Alexander A. Klimov" <grandmaster@al2klimov.de> wrote:
> al3010_read_raw() used to read two adjacent registers
> until the driver was modernized using the regmap framework.
> That cleanup accidentally replaced the 16-bit word read
> with a single byte read. I'm reverting latter.
>
> Fixes: 0e5e21e23dd6 ("iio: light: al3010: Implement regmap support")
> Signed-off-by: Alexander A. Klimov <grandmaster@al2klimov.de>
Hi Alexander,
> ---
> drivers/iio/light/al3010.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/iio/light/al3010.c b/drivers/iio/light/al3010.c
> index 0932fa2b49fa..1800776d725e 100644
> --- a/drivers/iio/light/al3010.c
> +++ b/drivers/iio/light/al3010.c
> @@ -111,7 +111,8 @@ static int al3010_read_raw(struct iio_dev *indio_dev,
> int *val2, long mask)
> {
> struct al3010_data *data = iio_priv(indio_dev);
> - int ret, gain, raw;
> + int ret, gain;
> + uint16_t raw;
Kernel types, and more relevantly as the bot pointed out
__le16 raw;
>
> switch (mask) {
> case IIO_CHAN_INFO_RAW:
> @@ -120,11 +121,12 @@ static int al3010_read_raw(struct iio_dev *indio_dev,
> * - low byte of output is stored at AL3010_REG_DATA_LOW
> * - high byte of output is stored at AL3010_REG_DATA_LOW + 1
> */
> - ret = regmap_read(data->regmap, AL3010_REG_DATA_LOW, &raw);
> + ret = regmap_bulk_read(data->regmap, AL3010_REG_DATA_LOW,
> + &raw, sizeof(raw));
> if (ret)
> return ret;
>
> - *val = raw;
> + *val = le16_to_cpu(raw);
>
> return IIO_VAL_INT;
> case IIO_CHAN_INFO_SCALE:
prev parent reply other threads:[~2026-05-21 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 17:58 Alexander A. Klimov
2026-05-20 19:26 ` David Heidelberg
2026-05-21 3:33 ` kernel test robot
2026-05-21 11:23 ` Jonathan Cameron [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=20260521122350.1d705c8f@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=david@ixit.cz \
--cc=dlechner@baylibre.com \
--cc=grandmaster@al2klimov.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@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®