Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Petre Rodan <petre.rodan@subdimension.ro>
Cc: "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 6/6] iio: accel: bma220: add any-motion detection
Date: Sat, 18 Oct 2025 18:32:38 +0100	[thread overview]
Message-ID: <20251018183238.05b60ac7@jic23-huawei> (raw)
In-Reply-To: <20251014-bma220_events-v1-6-153424d7ea08@subdimension.ro>

On Tue, 14 Oct 2025 19:43:02 +0300
Petre Rodan <petre.rodan@subdimension.ro> wrote:

> Add support for what Bosch calls "any-motion (slope)" detection.

Slope is normally rate of change in IIO ABI terms. See the _roc_
event types.

The slight wrinkle here is that we have it based on the magnitude
and, whilst it has been a while since most of the sensors using
_roc_ were added I think they were typically signed. So it was
acceleration is getting higher at x rate, rather than what I think
we have here which is that the acceleration is either growing or shrinking
at x rate.  (kind of _rocmag_, similar to _mag_ relationship to _thresh_
events)

What this has to do with 'any motion' I have no idea - I'm just
looking at the graphs.  If I read them right we need something new.
Or it's entirely possible I've forgotten some part of existing ABI
that can handle this.

Jonathan


> 
> Signed-off-by: Petre Rodan <petre.rodan@subdimension.ro>
> ---
> I think Jonathan remarked that this might be improper use of the iio API?
> please advise.



      reply	other threads:[~2025-10-18 17:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-14 16:42 [PATCH 0/6] iio: accel: bma220: add events Petre Rodan
2025-10-14 16:42 ` [PATCH 1/6] iio: accel: bma220: white space cleanup Petre Rodan
2025-10-18 16:55   ` Jonathan Cameron
2025-10-14 16:42 ` [PATCH 2/6] iio: accel: bma220: remove useless include Petre Rodan
2025-10-18 16:55   ` Jonathan Cameron
2025-10-14 16:42 ` [PATCH 3/6] iio: accel: bma220: add tap detection Petre Rodan
2025-10-18 17:16   ` Jonathan Cameron
2025-11-01  7:56     ` Petre Rodan
2025-11-02 12:20       ` Jonathan Cameron
2025-11-07  0:30         ` Petre Rodan
2025-11-09 12:41           ` Jonathan Cameron
2025-10-14 16:43 ` [PATCH 4/6] iio: accel: bma220: add low-g event detection Petre Rodan
2025-10-18 17:20   ` Jonathan Cameron
2025-10-18 17:22   ` Jonathan Cameron
2025-10-14 16:43 ` [PATCH 5/6] iio: accel: bma220: add high-g " Petre Rodan
2025-10-14 16:43 ` [PATCH 6/6] iio: accel: bma220: add any-motion detection Petre Rodan
2025-10-18 17:32   ` 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=20251018183238.05b60ac7@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=petre.rodan@subdimension.ro \
    /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