From: Jonathan Cameron <jic23@kernel.org>
To: Lothar Rubusch <l.rubusch@gmail.com>
Cc: lars@metafoo.de, Michael.Hennerich@analog.com,
dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
corbet@lwn.net, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
eraretuya@gmail.com
Subject: Re: [PATCH v12 0/7] iio: accel: adxl345: add interrupt based sensor events
Date: Sat, 2 Aug 2025 12:47:32 +0100 [thread overview]
Message-ID: <20250802124732.1cd4c5ce@jic23-huawei> (raw)
In-Reply-To: <20250727210014.27766-1-l.rubusch@gmail.com>
On Sun, 27 Jul 2025 21:00:07 +0000
Lothar Rubusch <l.rubusch@gmail.com> wrote:
> Add several interrupt based sensor detection events:
> - refactoring and fixes
> - activity/inactivity linked and auto-sleep
> - AC-coupled activity/inactivity
> - Extend inactivity for inactivity under 1s (using free-fall register)
> - documentation
>
> Signed-off-by: Lothar Rubusch <l.rubusch@gmail.com>
Applied to the testing branch of iio.git. I'll rebase on rc1 once
available.
Thanks,
Jonathan
prev parent reply other threads:[~2025-08-02 11:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-27 21:00 [PATCH v12 0/7] iio: accel: adxl345: add interrupt based sensor events Lothar Rubusch
2025-07-27 21:00 ` [PATCH v12 1/7] iio: accel: adxl345: simplify tap suppress bit Lothar Rubusch
2025-07-27 21:00 ` [PATCH v12 2/7] iio: accel: adxl345: add activity event feature Lothar Rubusch
2025-07-27 21:00 ` [PATCH v12 3/7] iio: accel: adxl345: add inactivity feature Lothar Rubusch
2025-07-27 21:00 ` [PATCH v12 4/7] iio: accel: adxl345: add coupling detection for activity/inactivity Lothar Rubusch
2025-07-27 21:00 ` [PATCH v12 5/7] iio: accel: adxl345: extend inactivity time for less than 1s Lothar Rubusch
2025-07-27 21:00 ` [PATCH v12 6/7] docs: iio: add documentation for adxl345 driver Lothar Rubusch
2025-07-27 21:00 ` [PATCH v12 7/7] docs: iio: describe inactivity and free-fall detection on the ADXL345 Lothar Rubusch
2025-08-02 11:47 ` 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=20250802124732.1cd4c5ce@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=corbet@lwn.net \
--cc=dlechner@baylibre.com \
--cc=eraretuya@gmail.com \
--cc=l.rubusch@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).