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 v1 11/12] iio: accel: adxl345: add activity feature
Date: Sat, 1 Feb 2025 17:27:39 +0000 [thread overview]
Message-ID: <20250201172739.40d12340@jic23-huawei> (raw)
In-Reply-To: <20250128120100.205523-12-l.rubusch@gmail.com>
On Tue, 28 Jan 2025 12:00:59 +0000
Lothar Rubusch <l.rubusch@gmail.com> wrote:
> Add the handling of activity events, also add sysfs entries to
> configure threshold values to trigger the event. Allow to push the
> event over to the iio channel.
>
> Signed-off-by: Lothar Rubusch <l.rubusch@gmail.com>
I was going to guess these were rate of change detectors or ones
at least slightly compensating for g, but superficially
looks like a straight forward rising mag threshold. Not seeing need
for new ABI.
We've had those interfaces with accelerometers for a long time.
Key is to map the pretty names in the datasheet into what is actually
being detected. That allows for a lot better generalization across manufacturers.
> ---
> drivers/iio/accel/adxl345_core.c | 158 ++++++++++++++++++++++++++++++-
> 1 file changed, 154 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/iio/accel/adxl345_core.c b/drivers/iio/accel/adxl345_core.c
> index 62d75d28b6fc..94c3ad818ba5 100644
> --- a/drivers/iio/accel/adxl345_core.c
> +++ b/drivers/iio/accel/adxl345_core.c
> @@ -121,6 +121,8 @@
>
> #define ADXL345_REG_TAP_AXIS_MSK GENMASK(2, 0)
> #define ADXL345_REG_TAP_SUPPRESS_MSK BIT(3)
> +#define ADXL345_REG_ACT_AXIS_MSK GENMASK(6, 4)
> +#define ADXL345_REG_ACT_ACDC_MSK BIT(7)
>
> enum adxl345_axis {
> ADXL345_Z_EN = BIT(0),
> @@ -163,6 +165,10 @@ struct adxl345_state {
> u8 watermark;
> u8 fifo_mode;
>
> + u32 act_axis_ctrl;
> + bool act_ac;
> + u8 act_value;
> +
> u32 tap_axis_ctrl;
> u8 tap_threshold;
> u32 tap_duration_us;
> @@ -177,6 +183,11 @@ struct adxl345_state {
> };
>
> static struct iio_event_spec adxl345_events[] = {
> + {
> + /* activity */
> + .type = IIO_EV_TYPE_THRESH,
> + .dir = IIO_EV_DIR_RISING,
> + },
> {
> /* single tap */
> .type = IIO_EV_TYPE_GESTURE,
> @@ -276,6 +287,117 @@ static inline int adxl345_write_interrupts(struct adxl345_state *st)
> return regmap_write(st->regmap, ADXL345_REG_INT_ENABLE, st->int_map);
> }
>
> +/* act/inact */
> +
> +static int adxl345_write_act_axis(struct adxl345_state *st, bool en)
> +{
> + int ret;
> +
> + /*
> + * A setting of 0 selects dc-coupled operation, and a setting of 1
> + * enables ac-coupled operation. In dc-coupled operation, the current
> + * acceleration magnitude is compared directly with THRESH_ACT and
> + * THRESH_INACT to determine whether activity or inactivity is
> + * detected.
> + *
> + * In ac-coupled operation for activity detection, the acceleration
> + * value at the start of activity detection is taken as a reference
> + * value. New samples of acceleration are then compared to this
> + * reference value, and if the magnitude of the difference exceeds the
> + * THRESH_ACT value, the device triggers an activity interrupt.
> + *
> + * Similarly, in ac-coupled operation for inactivity detection, a
> + * reference value is used for comparison and is updated whenever the
> + * device exceeds the inactivity threshold. After the reference value
> + * is selected, the device compares the magnitude of the difference
> + * between the reference value and the current acceleration with
> + * THRESH_INACT. If the difference is less than the value in
> + * THRESH_INACT for the time in TIME_INACT, the device is considered
> + * inactive and the inactivity interrupt is triggered.
> + */
> + ret = regmap_update_bits(st->regmap, ADXL345_REG_ACT_INACT_CTRL,
> + ADXL345_REG_ACT_ACDC_MSK, st->act_ac);
> + if (ret)
> + return ret;
> +
> + /*
> + * The ADXL345 allows for individually enabling/disabling axis for
> + * activity and inactivity detection, respectively. Here both axis are
> + * kept in sync, i.e. an axis will be generally enabled or disabled for
> + * both equally, activity and inactivity detection.
> + */
> + st->act_axis_ctrl = en
> + ? st->act_axis_ctrl | ADXL345_REG_ACT_AXIS_MSK
> + : st->act_axis_ctrl & ~ADXL345_REG_ACT_AXIS_MSK;
> +
> + ret = regmap_update_bits(st->regmap, ADXL345_REG_ACT_INACT_CTRL,
> + ADXL345_REG_ACT_AXIS_MSK,
> + st->act_axis_ctrl);
> + if (ret)
> + return ret;
> +
> + return 0;
> +}
> +
> +static int adxl345_set_act_int(struct adxl345_state *st)
> +{
> + bool args_valid;
> + bool axis_en;
> +
> + axis_en = FIELD_GET(ADXL345_REG_ACT_AXIS_MSK, st->act_axis_ctrl) > 0;
> + args_valid = axis_en && st->act_value > 0;
> + adxl345_intmap_switch_bit(st, args_valid, ADXL345_INT_ACTIVITY);
> +
> + return adxl345_write_interrupts(st);
> +}
> +
> +static int _adxl345_is_act_en(struct adxl345_state *st, bool *en)
> +{
> + int ret;
> + unsigned int regval;
> +
> + ret = adxl345_read_interrupts(st, ®val);
> + if (ret)
> + return ret;
> +
> + *en = FIELD_GET(ADXL345_INT_ACTIVITY, regval) > 0;
> +
> + return 0;
> +}
> +
> +static int _adxl345_set_act_en(struct adxl345_state *st, bool en)
> +{
> + int ret;
> +
> + ret = adxl345_write_act_axis(st, en);
> + if (ret)
> + return ret;
> +
> + return adxl345_set_act_int(st);
> +}
> +
> +static int adxl345_is_act_en(struct adxl345_state *st, bool *en)
> +{
> + return _adxl345_is_act_en(st, en);
> +}
> +
> +static int adxl345_set_act_en(struct adxl345_state *st, bool en)
> +{
> + return _adxl345_set_act_en(st, en);
> +}
> +
> +static int _adxl345_set_act_value(struct adxl345_state *st, u8 val)
> +{
> + st->act_value = val;
> +
> + return regmap_write(st->regmap, ADXL345_REG_THRESH_ACT, val);
> +}
> +
> +static int adxl345_set_act_value(struct adxl345_state *st, u8 val)
> +{
> + return _adxl345_set_act_value(st, val);
> +}
next prev parent reply other threads:[~2025-02-01 17:27 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 12:00 [PATCH v1 00/12] iio: accel: adxl345: add interrupt based sensor events Lothar Rubusch
2025-01-28 12:00 ` [PATCH v1 01/12] iio: accel: adxl345: migrate constants to core Lothar Rubusch
2025-02-01 16:35 ` Jonathan Cameron
2025-02-04 14:13 ` Lothar Rubusch
2025-02-04 14:46 ` Jonathan Cameron
2025-01-28 12:00 ` [PATCH v1 02/12] iio: accel: adxl345: reorganize measurement enable Lothar Rubusch
2025-02-01 16:37 ` Jonathan Cameron
2025-01-28 12:00 ` [PATCH v1 03/12] iio: accel: adxl345: add debug register access Lothar Rubusch
2025-01-28 12:00 ` [PATCH v1 04/12] iio: accel: adxl345: reorganize irq handler Lothar Rubusch
2025-02-01 16:43 ` Jonathan Cameron
2025-01-28 12:00 ` [PATCH v1 05/12] iio: accel: adxl345: improve access to the interrupt enable register Lothar Rubusch
2025-02-01 16:49 ` Jonathan Cameron
2025-01-28 12:00 ` [PATCH v1 06/12] iio: accel: adxl345: add single tap feature Lothar Rubusch
2025-02-01 17:02 ` Jonathan Cameron
2025-01-28 12:00 ` [PATCH v1 07/12] iio: accel: adxl345: show tap status and direction Lothar Rubusch
2025-02-01 17:09 ` Jonathan Cameron
2025-01-28 12:00 ` [PATCH v1 08/12] iio: accel: adxl345: add double tap feature Lothar Rubusch
2025-02-01 17:15 ` Jonathan Cameron
2025-01-28 12:00 ` [PATCH v1 09/12] iio: accel: adxl345: add double tap suppress bit Lothar Rubusch
2025-02-01 17:17 ` Jonathan Cameron
2025-01-28 12:00 ` [PATCH v1 10/12] iio: accel: adxl345: add freefall feature Lothar Rubusch
2025-02-01 17:22 ` Jonathan Cameron
2025-01-28 12:00 ` [PATCH v1 11/12] iio: accel: adxl345: add activity feature Lothar Rubusch
2025-02-01 17:27 ` Jonathan Cameron [this message]
2025-02-04 13:48 ` Lothar Rubusch
2025-01-28 12:01 ` [PATCH v1 12/12] iio: accel: adxl345: add inactivity feature Lothar Rubusch
2025-02-01 17:41 ` Jonathan Cameron
2025-02-01 17:48 ` [PATCH v1 00/12] iio: accel: adxl345: add interrupt based sensor events Jonathan Cameron
2025-02-04 13:40 ` Lothar Rubusch
2025-02-08 12:57 ` 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=20250201172739.40d12340@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