From: Jonathan Cameron <jic23@kernel.org>
To: Jean-Baptiste Maneyrol via B4 Relay
<devnull+jean-baptiste.maneyrol.tdk.com@kernel.org>
Cc: jean-baptiste.maneyrol@tdk.com,
"Lars-Peter Clausen" <lars@metafoo.de>,
"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 v6 0/3] Add support for WoM (Wake-on-Motion) feature
Date: Sun, 6 Jul 2025 17:21:50 +0100 [thread overview]
Message-ID: <20250706172150.556972c0@jic23-huawei> (raw)
In-Reply-To: <20250630-losd-3-inv-icm42600-add-wom-support-v6-0-5bb0c84800d9@tdk.com>
On Mon, 30 Jun 2025 21:47:28 +0200
Jean-Baptiste Maneyrol via B4 Relay <devnull+jean-baptiste.maneyrol.tdk.com@kernel.org> wrote:
> Similar to feature present in older chip, it compares the magnitude of
> the last 2 accel samples against a threshold and returns an interrupt
> even if the value is higher.
>
> WoM maps best to accel x|y|z ROC event. This series add system wakeup
> functionality if WoM is on and wakeup is enabled when system suspends.
>
> This series also prepare the driver for supporting further APEX
> features like pedometer, tilt, ... It introduces an apex structure that
> will hold all APEX settings and track the enable state.
Applied to the togreg branch of iio.git and pushed out initially as testing
for 0-day to poke at it.
Thanks,
Jonathan
>
> Signed-off-by: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
> ---
> Changes in v6:
> - Rework scoped_guard() for not using break
> - Reword move DMA buffers initial patch to add better explanations
> - Link to v5: https://lore.kernel.org/r/20250623-losd-3-inv-icm42600-add-wom-support-v5-0-4b3b33e028fe@tdk.com
>
> Changes in v5:
> - Add preliminary patch to move DMA buffers at end of structure.
> - Check return code of devm_device_init_wakeup()
> - Rebase and rework series to use kernel types
> - Link to v4: https://lore.kernel.org/r/20250613-losd-3-inv-icm42600-add-wom-support-v4-0-7e5f554201bf@tdk.com
>
> Changes in v4:
> - Avoid mix of gotos and scoped_guard()
> - Invert conditionals for better code readability
> - Switch to use devm_device_init_wakeup()
> - Several code readabilities improvements
> - Link to v3: https://lore.kernel.org/r/20250418-losd-3-inv-icm42600-add-wom-support-v3-0-7a180af02bfe@tdk.com
>
> Changes in v3:
> - Rewrites following code review
> - Link to v2: https://lore.kernel.org/r/20250415-losd-3-inv-icm42600-add-wom-support-v2-0-de94dfb92b7e@tdk.com
>
> Changes in v2:
> - change struct order to avoir DMA overflow
> - separate wom enable/disable in 2 functions
> - delete mutex rework
> - Link to v1: https://lore.kernel.org/r/20250220-losd-3-inv-icm42600-add-wom-support-v1-0-9b937f986954@tdk.com
>
> ---
> Jean-Baptiste Maneyrol (3):
> iio: imu: inv_icm42600: reorganize DMA aligned buffers in structure
> iio: imu: inv_icm42600: add WoM support
> iio: imu: inv_icm42600: add wakeup functionality for Wake-on-Motion
>
> drivers/iio/imu/inv_icm42600/inv_icm42600.h | 56 +++-
> drivers/iio/imu/inv_icm42600/inv_icm42600_accel.c | 329 ++++++++++++++++++++-
> drivers/iio/imu/inv_icm42600/inv_icm42600_buffer.c | 2 +-
> drivers/iio/imu/inv_icm42600/inv_icm42600_core.c | 97 +++++-
> 4 files changed, 470 insertions(+), 14 deletions(-)
> ---
> base-commit: 42498420746a4db923f03d048a0ebc9bd2371f56
> change-id: 20250220-losd-3-inv-icm42600-add-wom-support-0620fef9db23
>
> Best regards,
prev parent reply other threads:[~2025-07-06 16:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 19:47 Jean-Baptiste Maneyrol via B4 Relay
2025-06-30 19:47 ` [PATCH v6 1/3] iio: imu: inv_icm42600: reorganize DMA aligned buffers in structure Jean-Baptiste Maneyrol via B4 Relay
2025-06-30 19:47 ` [PATCH v6 2/3] iio: imu: inv_icm42600: add WoM support Jean-Baptiste Maneyrol via B4 Relay
2025-07-06 16:20 ` Jonathan Cameron
2025-06-30 19:47 ` [PATCH v6 3/3] iio: imu: inv_icm42600: add wakeup functionality for Wake-on-Motion Jean-Baptiste Maneyrol via B4 Relay
2025-07-07 15:06 ` Sean Nyekjaer
2025-07-06 16:21 ` 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=20250706172150.556972c0@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=devnull+jean-baptiste.maneyrol.tdk.com@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jean-baptiste.maneyrol@tdk.com \
--cc=lars@metafoo.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®