Linux IIO development
 help / color / mirror / Atom feed
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 v6 04/11] iio: accel: adxl345: set the tap suppress bit permanently
Date: Fri, 18 Apr 2025 19:14:13 +0100	[thread overview]
Message-ID: <20250418191413.4a0a873e@jic23-huawei> (raw)
In-Reply-To: <20250414184245.100280-5-l.rubusch@gmail.com>

On Mon, 14 Apr 2025 18:42:38 +0000
Lothar Rubusch <l.rubusch@gmail.com> wrote:

> Set the suppress bit feature to the double tap detection, whenever
> double tap is enabled. This impedes the suppress bit dangling in any
> state, and thus varying in sensitivity for double tap detection.
> 
> Any tap event is defined by a rising signal edge above threshold, i.e.
> duration time starts counting; and the falling edge under threshold
> within duration time, i.e. then the tap event is issued. This means
> duration is used individually for each tap event.
> 
> For double tap detection after a single tap, a latency time needs to be
> specified. Usually tap events, i.e. spikes above and returning below
> threshold will be ignored within latency. After latency, the window
> time starts counting for a second tap detection which has to happen
> within a duration time.
> 
> If the suppress bit is not set, spikes within latency time are ignored.
> Setting the suppress bit will invalidate the double tap function. The
> sensor will thus be able to save the window time for double tap
> detection, and follow a more strict definition of what signal qualifies
> for a double tap.
> 
> In a summary having the suppress bit set, fewer signal spikes will be
> considered as double taps. This is an optional add on to double tap,
> thus a separate patch.
> 
> Signed-off-by: Lothar Rubusch <l.rubusch@gmail.com>
Applied 1-4.

Thanks,
Jonathan

  reply	other threads:[~2025-04-18 18:14 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-14 18:42 [PATCH v6 00/11] iio: accel: adxl345: add interrupt based sensor events Lothar Rubusch
2025-04-14 18:42 ` [PATCH v6 01/11] iio: accel: adxl345: introduce adxl345_push_event function Lothar Rubusch
2025-04-14 18:42 ` [PATCH v6 02/11] iio: accel: adxl345: add single tap feature Lothar Rubusch
2025-04-14 18:42 ` [PATCH v6 03/11] iio: accel: adxl345: add double " Lothar Rubusch
2025-04-14 18:42 ` [PATCH v6 04/11] iio: accel: adxl345: set the tap suppress bit permanently Lothar Rubusch
2025-04-18 18:14   ` Jonathan Cameron [this message]
2025-04-14 18:42 ` [PATCH v6 05/11] iio: accel: adxl345: add freefall feature Lothar Rubusch
2025-04-18 18:22   ` Jonathan Cameron
2025-04-20 21:26     ` Lothar Rubusch
2025-04-21 10:16       ` Jonathan Cameron
2025-04-21 13:31         ` Lothar Rubusch
2025-04-21 13:51           ` Jonathan Cameron
2025-04-14 18:42 ` [PATCH v6 06/11] iio: accel: adxl345: extend sample frequency adjustments Lothar Rubusch
2025-04-14 18:42 ` [PATCH v6 07/11] iio: accel: adxl345: add g-range configuration Lothar Rubusch
2025-04-14 18:42 ` [PATCH v6 08/11] iio: accel: adxl345: add activity event feature Lothar Rubusch
2025-04-14 18:42 ` [PATCH v6 09/11] iio: accel: adxl345: add inactivity feature Lothar Rubusch
2025-04-18 18:34   ` Jonathan Cameron
2025-04-20 22:12     ` Lothar Rubusch
2025-04-21 10:22       ` Jonathan Cameron
2025-04-21 13:39         ` Lothar Rubusch
2025-04-21 13:54           ` Jonathan Cameron
2025-04-21 22:11             ` Lothar Rubusch
2025-04-14 18:42 ` [PATCH v6 10/11] iio: accel: adxl345: add coupling detection for activity/inactivity Lothar Rubusch
2025-04-14 18:42 ` [PATCH v6 11/11] docs: iio: add documentation for adxl345 driver Lothar Rubusch
2025-04-18 18:38   ` Jonathan Cameron
  -- strict thread matches above, loose matches on Subject: below --
2025-04-29 18:26 [PATCH v6 04/11] iio: accel: adxl345: set the tap suppress bit permanently oryakerbay

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=20250418191413.4a0a873e@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