mirror of https://lore.kernel.org/lkml/
 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 05/11] iio: accel: adxl345: add freefall feature
Date: Fri, 18 Apr 2025 19:22:54 +0100	[thread overview]
Message-ID: <20250418192254.0becd27d@jic23-huawei> (raw)
In-Reply-To: <20250414184245.100280-6-l.rubusch@gmail.com>

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

> Add the freefall detection of the sensor together with a threshold and
> time parameter. A freefall event is detected if the measuring signal
> falls below the threshold.
> 
> Introduce a freefall threshold stored in regmap cache, and a freefall
> time, having the scaled time value stored as a member variable in the
> state instance.
> 
Reading this I wondered whether we had the event code consistent for
freefall detectors... Or indeed inactivity ones (which are kind of similarish)

:( We don't it seems.  The issue is that
freefall is actually that all channels are simultaneously under the the magnitude
threshold, not one of them.  So it should I think be
X_AND_Y_AND_Z not X_OR_Y_OR_Z

This is as opposed to activity detectors which tend to be any axis shows
activity and X_OR_Y_OR_Z applies.

Anyhow upshot is I think I lead you astray on this and we should make this
one IIO_MOD_X_AND_Y_AND_Z 

A few other things inline.

Unfortunately we don't deal with these events that often so I forget
what we did before :(

> Signed-off-by: Lothar Rubusch <l.rubusch@gmail.com>
> ---
>  drivers/iio/accel/adxl345_core.c | 125 +++++++++++++++++++++++++++++++
>  1 file changed, 125 insertions(+)
> 
> diff --git a/drivers/iio/accel/adxl345_core.c b/drivers/iio/accel/adxl345_core.c
> index c464c87033fb..ae02826e552b 100644
> --- a/drivers/iio/accel/adxl345_core.c
> +++ b/drivers/iio/accel/adxl345_core.c
> @@ -75,6 +75,7 @@ struct adxl345_state {
>  	u32 tap_duration_us;
>  	u32 tap_latent_us;
>  	u32 tap_window_us;
> +	u32 ff_time_ms;
>  
>  	__le16 fifo_buf[ADXL345_DIRS * ADXL345_FIFO_SIZE + 1] __aligned(IIO_DMA_MINALIGN);
>  };
> @@ -96,6 +97,14 @@ static struct iio_event_spec adxl345_events[] = {
>  			BIT(IIO_EV_INFO_RESET_TIMEOUT) |
>  			BIT(IIO_EV_INFO_TAP2_MIN_DELAY),
>  	},
> +	{
> +		/* free fall */
> +		.type = IIO_EV_TYPE_MAG,
> +		.dir = IIO_EV_DIR_FALLING,
> +		.mask_shared_by_type = BIT(IIO_EV_INFO_ENABLE) |
> +			BIT(IIO_EV_INFO_VALUE) |
> +			BIT(IIO_EV_INFO_PERIOD),
> +	},
This is creating separate per axis enables, values and period. Does that make
sense?  If not you need to spin a kind of virtual channel (with mod X_AND_Y_AND_Z)
and add the events to it.

See how the sca3000 does it for example.
>  };
>  
>  #define ADXL345_CHANNEL(index, reg, axis) {					\
> @@ -383,6 +392,63 @@ static int adxl345_set_tap_latent(struct adxl345_state *st, u32 val_int,
>  	return _adxl345_set_tap_time(st, ADXL345_TAP_TIME_LATENT, val_fract_us);
>  }
>  
> +/* freefall */
> +
> +static int adxl345_is_ff_en(struct adxl345_state *st, bool *en)
> +{
> +	int ret;
> +	unsigned int regval;
> +
> +	ret = regmap_read(st->regmap, ADXL345_REG_INT_ENABLE, &regval);
> +	if (ret)
> +		return ret;
> +
> +	*en = FIELD_GET(ADXL345_INT_FREE_FALL, regval) > 0;
> +
> +	return 0;
> +}
> +
> +static int adxl345_set_ff_en(struct adxl345_state *st, bool cmd_en)
> +{
> +	unsigned int regval, ff_threshold;
> +	bool en;
> +	int ret;
> +
> +	ret = regmap_read(st->regmap, ADXL345_REG_THRESH_FF, &ff_threshold);
> +	if (ret)
> +		return ret;
> +
> +	en = cmd_en && ff_threshold > 0 && st->ff_time_ms > 0;
> +
> +	regval = en ? ADXL345_INT_FREE_FALL : 0x00;
> +
> +	return regmap_update_bits(st->regmap, ADXL345_REG_INT_ENABLE,
> +				  ADXL345_INT_FREE_FALL, regval);
> +}
> +
> +static int adxl345_set_ff_time(struct adxl345_state *st, u32 val_int,
> +			       u32 val_fract_us)
> +{
> +	unsigned int regval;
> +	int val_ms;
> +
> +	/*
> +	 * max value is 255 * 5000 us = 1.275000 seconds
> +	 *
> +	 * Note: the scaling is similar to the scaling in the ADXL380
> +	 */
> +	if (1000000 * val_int + val_fract_us > 1275000)
> +		return -EINVAL;
> +
> +	val_ms = val_int * 1000 + DIV_ROUND_UP(val_fract_us, 1000);
> +	st->ff_time_ms = val_ms;
> +
> +	regval = DIV_ROUND_CLOSEST(val_ms, 5);
> +
> +	/* Values between 100ms and 350ms (0x14 to 0x46) are recommended. */
> +	return regmap_write(st->regmap, ADXL345_REG_TIME_FF, min(regval, 0xff));
> +}
> +
>  static int adxl345_read_raw(struct iio_dev *indio_dev,
>  			    struct iio_chan_spec const *chan,
>  			    int *val, int *val2, long mask)
> @@ -495,6 +561,11 @@ static int adxl345_read_event_config(struct iio_dev *indio_dev,
>  		default:
>  			return -EINVAL;
>  		}
> +	case IIO_EV_TYPE_MAG:
> +		ret = adxl345_is_ff_en(st, &int_en);
> +		if (ret)
> +			return ret;
> +		return int_en;
>  	default:
>  		return -EINVAL;
>  	}
> @@ -518,6 +589,8 @@ static int adxl345_write_event_config(struct iio_dev *indio_dev,
>  		default:
>  			return -EINVAL;
>  		}
> +	case IIO_EV_TYPE_MAG:
> +		return adxl345_set_ff_en(st, state);
>  	default:
>  		return -EINVAL;
>  	}
> @@ -532,6 +605,7 @@ static int adxl345_read_event_value(struct iio_dev *indio_dev,
>  {
>  	struct adxl345_state *st = iio_priv(indio_dev);
>  	unsigned int tap_threshold;
> +	unsigned int ff_threshold;
>  	int ret;
>  
>  	switch (type) {
> @@ -565,6 +639,22 @@ static int adxl345_read_event_value(struct iio_dev *indio_dev,
>  		default:
>  			return -EINVAL;
>  		}
> +	case IIO_EV_TYPE_MAG:
> +		switch (info) {
> +		case IIO_EV_INFO_VALUE:
> +			ret = regmap_read(st->regmap, ADXL345_REG_THRESH_FF,
> +					  &ff_threshold);
> +			if (ret)
> +				return ret;
> +			*val = ff_threshold;
> +			return IIO_VAL_INT;
> +		case IIO_EV_INFO_PERIOD:
> +			*val = st->ff_time_ms;
> +			*val2 = 1000;
> +			return IIO_VAL_FRACTIONAL;
> +		default:
> +			return -EINVAL;
> +		}
>  	default:
>  		return -EINVAL;
>  	}
> @@ -612,6 +702,22 @@ static int adxl345_write_event_value(struct iio_dev *indio_dev,
>  			return -EINVAL;
>  		}
>  		break;
> +	case IIO_EV_TYPE_MAG:
> +		switch (info) {
> +		case IIO_EV_INFO_VALUE:
> +			ret = regmap_write(st->regmap, ADXL345_REG_THRESH_FF, val);
> +			if (ret)
> +				return ret;
> +			break;
> +		case IIO_EV_INFO_PERIOD:
> +			ret = adxl345_set_ff_time(st, val, val2);
> +			if (ret)
> +				return ret;
> +			break;
> +		default:
> +			return -EINVAL;
> +		}
> +		break;
>  	default:
>  		return -EINVAL;
>  	}
> @@ -865,6 +971,17 @@ static int adxl345_push_event(struct iio_dev *indio_dev, int int_stat,
>  			return ret;
>  	}
>  
> +	if (FIELD_GET(ADXL345_INT_FREE_FALL, int_stat)) {
> +		ret = iio_push_event(indio_dev,
> +				     IIO_MOD_EVENT_CODE(IIO_ACCEL, 0,
> +							IIO_MOD_X_OR_Y_OR_Z,

This is the event that got me thinking about whether we were doing this right..

> +							IIO_EV_TYPE_MAG,
> +							IIO_EV_DIR_FALLING),
> +				     ts);
> +		if (ret)
> +			return ret;
> +	}
> +


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

Thread overview: 25+ 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
2025-04-14 18:42 ` [PATCH v6 05/11] iio: accel: adxl345: add freefall feature Lothar Rubusch
2025-04-18 18:22   ` Jonathan Cameron [this message]
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

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=20250418192254.0becd27d@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

all inboxes | Powered by JetHome®