From: Jonathan Cameron <jic23@kernel.org>
To: Francesco Lavra <flavra@baylibre.com>
Cc: "Ramona Gradinariu" <ramona.gradinariu@analog.com>,
"Antoniu Miclaus" <antoniu.miclaus@analog.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.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 0/2] accel: adxl380: Improve data reading from FIFO
Date: Thu, 22 Jan 2026 19:54:23 +0000 [thread overview]
Message-ID: <20260122195423.692d90ec@jic23-huawei> (raw)
In-Reply-To: <20260119102317.1565417-1-flavra@baylibre.com>
On Mon, 19 Jan 2026 11:23:15 +0100
Francesco Lavra <flavra@baylibre.com> wrote:
> Patch 1 fixes a bug that might cause the adxl380 interrupt handler
> to read from the sensor FIFO more entries than actually present.
> Patch 2 optimizes transfer of FIFO data by minimizing transport protocol
> overhead.
>
> Changes from v1 [1]:
> - replaced 2 with sizeof(*st->fifo_buf) in adxl380_irq_handler (Jonathan)
>
> [1] https://lore.kernel.org/linux-iio/20260106193627.3989930-1-flavra@baylibre.com/T/
Series applied.
Given timing I've queued it up on the testing (soon to be togreg) branch of iio.git
but marked the first patch for stable so that it'll get backported after the merge
window.
Thanks,
Jonathan
>
> Francesco Lavra (2):
> iio: accel: adxl380: Avoid reading more entries than present in FIFO
> iio: accel: adxl380: Optimize reading of FIFO entries in interrupt
> handler
>
> drivers/iio/accel/adxl380.c | 13 ++++++-------
> 1 file changed, 6 insertions(+), 7 deletions(-)
>
prev parent reply other threads:[~2026-01-22 19:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 10:23 Francesco Lavra
2026-01-19 10:23 ` [PATCH v2 1/2] iio: accel: adxl380: Avoid reading more entries than present in FIFO Francesco Lavra
2026-01-19 10:23 ` [PATCH v2 2/2] iio: accel: adxl380: Optimize reading of FIFO entries in interrupt handler Francesco Lavra
2026-01-22 19:53 ` Jonathan Cameron
2026-01-23 8:13 ` Andy Shevchenko
2026-01-23 9:54 ` Jonathan Cameron
2026-01-23 11:09 ` Francesco Lavra
2026-01-23 11:12 ` Andy Shevchenko
2026-01-22 19:54 ` 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=20260122195423.692d90ec@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=dlechner@baylibre.com \
--cc=flavra@baylibre.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=ramona.gradinariu@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®