From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: "Gabriel Rondon" <grondon@gmail.com>,
"Matti Vaittinen" <mazziesaccount@gmail.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] iio: accel: kionix-kx022a: use scan struct for one-shot and trigger reads
Date: Thu, 20 Aug 2026 03:04:38 +0100 [thread overview]
Message-ID: <20260820030438.736b67e1@jic23-huawei> (raw)
In-Reply-To: <aoVYjc1ZRTj0OvTc@ashevche-desk.local>
On Wed, 19 Aug 2026 10:17:33 +0300
Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
> On Tue, Aug 18, 2026 at 10:51:21PM +0100, Gabriel Rondon wrote:
> > The driver kept two separate staging areas that hold the same thing:
> > buffer[8], a DMA-aligned area used by the one-shot read in
> > kx022a_get_axis() and by the triggered handler, and the scan struct,
> > used by the FIFO flush path. Both are three __le16 channels plus room
> > for the timestamp.
> >
> > Drop buffer and route the one-shot read and the triggered handler
> > through scan.channels, so the driver has a single staging area. Move the
> > IIO_DMA_MINALIGN alignment onto scan, since it now backs the regmap bulk
> > reads that buffer used to.
> >
> > No functional change. get_axis() only runs via read_raw() under
> > iio_device_claim_direct(), so it cannot run while the triggered buffer is
> > active, and the triggered handler only runs while it is; the two never
> > touch scan concurrently, exactly as they previously shared buffer.
>
> ...
>
> > static int kx022a_get_axis(struct kx022a_data *data,
>
> > {
>
> I would rather do this
>
> __le16 *buf = &data->scan.channels[0];
>
> > int ret;
> >
> > - ret = regmap_bulk_read(data->regmap, chan->address, &data->buffer[0],
> > - sizeof(__le16));
> > + ret = regmap_bulk_read(data->regmap, chan->address,
> > + &data->scan.channels[0], sizeof(__le16));
>
> ret = regmap_bulk_read(data->regmap, chan->address, buf, sizeof(*buf));
>
> > if (ret)
> > return ret;
> >
> > - *val = (s16)le16_to_cpu(data->buffer[0]);
> > + *val = (s16)le16_to_cpu(data->scan.channels[0]);
>
> *val = (s16)le16_to_cpup(buf);
True - that is nicer. Tweaked. Diff just to check I didn't get it wrong:
diff --git a/drivers/iio/accel/kionix-kx022a.c b/drivers/iio/accel/kionix-kx022a.c
index 86f17431aa23..8f2810c8ffeb 100644
--- a/drivers/iio/accel/kionix-kx022a.c
+++ b/drivers/iio/accel/kionix-kx022a.c
@@ -610,14 +610,15 @@ static int kx022a_get_axis(struct kx022a_data *data,
struct iio_chan_spec const *chan,
int *val)
{
+ __le16 *buf = &data->scan.channels[0];
int ret;
ret = regmap_bulk_read(data->regmap, chan->address,
- &data->scan.channels[0], sizeof(__le16));
+ buf, sizeof(*buf));
if (ret)
return ret;
- *val = (s16)le16_to_cpu(data->scan.channels[0]);
+ *val = (s16)le16_to_cpup(buf);
return IIO_VAL_INT;
}
>
next prev parent reply other threads:[~2026-08-20 2:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 21:51 [PATCH v2 0/2] iio: accel: kionix-kx022a: unify staging buffer and convert to iio_push_to_buffers_with_ts() Gabriel Rondon
2026-08-18 21:51 ` [PATCH v2 1/2] iio: accel: kionix-kx022a: use scan struct for one-shot and trigger reads Gabriel Rondon
2026-08-19 4:59 ` Matti Vaittinen
2026-08-19 7:17 ` Andy Shevchenko
2026-08-20 2:04 ` Jonathan Cameron [this message]
2026-08-18 21:51 ` [PATCH v2 2/2] iio: accel: kionix-kx022a: use iio_push_to_buffers_with_ts() Gabriel Rondon
2026-08-19 5:11 ` Matti Vaittinen
2026-08-20 2:11 ` Jonathan Cameron
2026-08-19 0:09 ` [PATCH v2 0/2] iio: accel: kionix-kx022a: unify staging buffer and convert to iio_push_to_buffers_with_ts() Jonathan Cameron
2026-08-19 5:15 ` Matti Vaittinen
2026-08-19 7:18 ` Andy Shevchenko
2026-08-20 2:15 ` Jonathan Cameron
2026-08-19 7:19 ` Andy Shevchenko
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=20260820030438.736b67e1@jic23-huawei \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=grondon@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--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