Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Jagath Jog J <jagathjog1996@gmail.com>
Cc: andy.shevchenko@gmail.com, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] iio: Add new event type gesture and use direction for single and double tap
Date: Sun, 19 Jun 2022 13:54:27 +0100	[thread overview]
Message-ID: <20220619135427.4ffc2d3d@jic23-huawei> (raw)
In-Reply-To: <20220613191706.31239-2-jagathjog1996@gmail.com>

On Tue, 14 Jun 2022 00:47:05 +0530
Jagath Jog J <jagathjog1996@gmail.com> wrote:

> Add new event type for tap called gesture and the direction can be used
> to differentiate single and double tap. This may be used by accelerometer
> sensors to express single and double tap events. For directional tap,
> modifiers like IIO_MOD_(X/Y/Z) can be used along with singletap and
> doubletap direction.
> 
> Signed-off-by: Jagath Jog J <jagathjog1996@gmail.com>

Hi,

With fresh eyes I think we need to rethink the use of _period to make sure
we have 'space' for another very like ABI element which is the maximum
time between events for them to be considered a double tap.

Jonathan

> ---
>  Documentation/ABI/testing/sysfs-bus-iio | 24 ++++++++++++++++++++++++
>  drivers/iio/industrialio-event.c        |  5 ++++-
>  include/uapi/linux/iio/types.h          |  3 +++
>  tools/iio/iio_event_monitor.c           |  8 +++++++-
>  4 files changed, 38 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/ABI/testing/sysfs-bus-iio b/Documentation/ABI/testing/sysfs-bus-iio
> index 3e00d7f7ee22..4eaf85e01911 100644
> --- a/Documentation/ABI/testing/sysfs-bus-iio
> +++ b/Documentation/ABI/testing/sysfs-bus-iio
> @@ -2035,3 +2035,27 @@ Description:
>  		Available range for the forced calibration value, expressed as:
>  
>  		- a range specified as "[min step max]"
> +
> +What:		/sys/.../events/in_accel_gesture_singletap_en
> +What:		/sys/.../events/in_accel_gesture_doubletap_en
> +KernelVersion:	5.19
> +Contact:	linux-iio@vger.kernel.org
> +Description:
> +		Device generates an event on a single or double tap.
> +
> +What:		/sys/.../events/in_accel_gesture_singletap_value
> +What:		/sys/.../events/in_accel_gesture_doubletap_value
> +KernelVersion:	5.19
> +Contact:	linux-iio@vger.kernel.org
> +Description:
> +		Specifies the threshold value that the device is comparing
> +		against to generate the tap gesture event. Units and exact
> +		meaning of value are device specific.

I'm fine with this one being device specific, as likely a complex alg
involved.

> +
> +What:		/sys/.../events/in_accel_gesture_doubletap_period
> +KernelVersion:	5.19
> +Contact:	linux-iio@vger.kernel.org
> +Description:
> +		Minimum time period between before and after the double tap
> +		event. Units and exact meaning of period value are device
> +		specific.

I think the units need to be standard.  Also would this work better
as a description?

	Minimum time in seconds between the two taps making up a double
        tap event.

Raises a question though. How would we specify the maximum time? I.e.
if taps are further apart than Xseconds, they are reported as two single
taps.

Maybe reusing period here isn't a good idea and we need to have new ABI for
this?





  reply	other threads:[~2022-06-19 12:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 19:17 [PATCH v1 0/2] iio: Add single and double tap events support Jagath Jog J
2022-06-13 19:17 ` [PATCH v1 1/2] iio: Add new event type gesture and use direction for single and double tap Jagath Jog J
2022-06-19 12:54   ` Jonathan Cameron [this message]
2022-06-26 13:21     ` Jagath Jog J
2022-07-16 14:56       ` Jonathan Cameron
2022-07-23  8:55         ` Jagath Jog J
2022-06-13 19:17 ` [PATCH v1 2/2] iio: accel: bma400: Add support for single and double tap events Jagath Jog J
2022-06-14  9:20   ` Andy Shevchenko
2022-06-14 19:18     ` Jagath Jog J
2022-06-19 12:47       ` Jonathan Cameron
2022-06-19 13:18   ` Jonathan Cameron
2022-06-26 13:23     ` Jagath Jog J
2022-07-16 15:20       ` Jonathan Cameron
2022-07-23  8:59         ` Jagath Jog J
2022-07-31 17:46           ` Jonathan Cameron

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=20220619135427.4ffc2d3d@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=jagathjog1996@gmail.com \
    --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