From: Jonathan Cameron <jic23@kernel.org>
To: Lothar Rubusch <l.rubusch@gmail.com>
Cc: lars@metafoo.de, Michael.Hennerich@analog.com,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
eraretuya@gmail.com
Subject: Re: [PATCH v9 0/4] iio: accel: adxl345: add FIFO operating with IRQ triggered watermark events
Date: Sat, 4 Jan 2025 13:09:16 +0000 [thread overview]
Message-ID: <20250104130916.5a25b5bd@jic23-huawei> (raw)
In-Reply-To: <20241228232949.72487-1-l.rubusch@gmail.com>
On Sat, 28 Dec 2024 23:29:45 +0000
Lothar Rubusch <l.rubusch@gmail.com> wrote:
> The adxl345 sensor offers several features. Most of them are based on
> using the hardware FIFO and reacting on events coming in on an interrupt
> line. Add access to configure and read out the FIFO, handling of interrupts
> and configuration and application of the watermark feature on that FIFO.
>
> Signed-off-by: Lothar Rubusch <l.rubusch@gmail.com>
Series applied but with a tweak on patch 3. Please take a look at the
testing branch where this will sit for a few days,
Jonathan
> ---
> v8 -> v9:
> - move FIELD_PREP() usage to a local usage in adxl345_core.c
> - remove ADXL345_{SD}_TAP_MSK macros
> v7 -> v8:
> - remove dt-binding quotation marks
> - add DMA alignment
> - fix indention, formatting and text alignment
> v6 -> v7:
> - reorder dt-binding patches
> - extracted FIFO specific from constants list
> - reorder constants list in header patch to the end
> - verify watermark input is within valid range
> v5 -> v6:
> - dropped justify patch, since unnecessary change to format mask
> - added separate dt-bindings patch to remove required interrupts property
> - merged FIFO watermark patches
> - reworked bitfield handling
> - group irq setup in probe()
> - several type fixes by smatch and tools
> v4 -> v5:
> - fix dt-binding for enum array of INT1 and INT2
> v3 -> v4:
> - fix dt-binding indention
> v2 -> v3:
> - reorganize commits, merge the watermark handling
> - INT lines are defined by binding
> - kfifo is prepared by devm_iio_kfifo_buffer_setup()
> - event handler is registered w/ devm_request_threaded_irq()
> v1 -> v2:
> Fix comments according to Documentation/doc-guide/kernel-doc.rst
> and missing static declaration of function.
> ---
> Lothar Rubusch (4):
> iio: accel: adxl345: introduce interrupt handling
> iio: accel: adxl345: initialize FIFO delay value for SPI
> iio: accel: adxl345: add FIFO with watermark events
> iio: accel: adxl345: complete the list of defines
>
> drivers/iio/accel/adxl345.h | 77 +++++--
> drivers/iio/accel/adxl345_core.c | 338 ++++++++++++++++++++++++++++++-
> drivers/iio/accel/adxl345_i2c.c | 2 +-
> drivers/iio/accel/adxl345_spi.c | 7 +-
> 4 files changed, 404 insertions(+), 20 deletions(-)
>
next prev parent reply other threads:[~2025-01-04 13:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-28 23:29 [PATCH v9 0/4] iio: accel: adxl345: add FIFO operating with IRQ triggered watermark events Lothar Rubusch
2024-12-28 23:29 ` [PATCH v9 1/4] iio: accel: adxl345: introduce interrupt handling Lothar Rubusch
2024-12-28 23:29 ` [PATCH v9 2/4] iio: accel: adxl345: initialize FIFO delay value for SPI Lothar Rubusch
2025-01-12 15:54 ` Andy Shevchenko
2024-12-28 23:29 ` [PATCH v9 3/4] iio: accel: adxl345: add FIFO with watermark events Lothar Rubusch
2025-01-04 13:08 ` Jonathan Cameron
2025-01-12 16:05 ` Andy Shevchenko
2024-12-28 23:29 ` [PATCH v9 4/4] iio: accel: adxl345: complete the list of defines Lothar Rubusch
2025-01-04 13:09 ` Jonathan Cameron [this message]
2025-01-05 22:22 ` [PATCH v9 0/4] iio: accel: adxl345: add FIFO operating with IRQ triggered watermark events Lothar Rubusch
2025-01-12 16:06 ` Andy Shevchenko
2025-01-12 16:38 ` Jonathan Cameron
2025-01-12 19:28 ` 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=20250104130916.5a25b5bd@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=eraretuya@gmail.com \
--cc=l.rubusch@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.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