From: Jonathan Cameron <jic23@kernel.org>
To: Lothar Rubusch <l.rubusch@gmail.com>
Cc: dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
corbet@lwn.net, lucas.p.stankus@gmail.com, lars@metafoo.de,
Michael.Hennerich@analog.com, bagasdotme@gmail.com,
linux-iio@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 7/8] iio: accel: adxl313: add AC coupled activity/inactivity events
Date: Sun, 22 Jun 2025 12:37:52 +0100 [thread overview]
Message-ID: <20250622123752.1834fbe2@jic23-huawei> (raw)
In-Reply-To: <20250615222258.117771-8-l.rubusch@gmail.com>
On Sun, 15 Jun 2025 22:22:57 +0000
Lothar Rubusch <l.rubusch@gmail.com> wrote:
> Introduce AC-coupled activity and inactivity as MAG_ADAPTIVE events.
> This adds a new set of threshold and duration configuration options,
> ensures proper handling of event disabling, and extends the use of the
> link bit to support complementary event configurations.
>
> For example, either ACTIVITY or ACTIVITY_AC can be enabled, but only the
> most recently set configuration will remain active. Disabling ACTIVITY
> will have no effect if ACTIVITY_AC is currently enabled, as the event
> types must match (i.e., ACTIVITY_AC must be explicitly disabled). When
> either INACTIVITY or INACTIVITY_AC is enabled alongside an activity
> event, the link bit is set.
>
> With the link bit and auto-sleep enabled, activity and inactivity events
> represent changes in the sensor's power-saving state and are only
> triggered upon actual state transitions. Since AC coupling uses separate
> bits for activity and inactivity, each can be configured independently.
> For instance, ACTIVITY can be linked with INACTIVITY_AC.
>
> If one of the linked events is disabled, the link bit is cleared. In
> that case, the remaining event will no longer reflect a state transition
> but will instead trigger based on periodic inactivity or whenever the
> activity threshold is exceeded.
>
> Signed-off-by: Lothar Rubusch <l.rubusch@gmail.com>
One small suggestion below.
>
> static int adxl313_set_act_inact_linkbit(struct adxl313_data *data, bool en)
> {
> - int act_en, inact_en;
> + int act_en, inact_en, act_ac_en, inact_ac_en;
>
> act_en = adxl313_is_act_inact_en(data, ADXL313_ACTIVITY);
> if (act_en < 0)
> return act_en;
>
> + act_ac_en = adxl313_is_act_inact_en(data, ADXL313_ACTIVITY_AC);
> + if (act_ac_en < 0)
> + return act_ac_en;
> +
> + act_en = act_en || act_ac_en;
All ends up a little confusing as act_en changes meaning as it is built
up. Maybe better to just have act_dc_en in earlier patch then so
the boolean complexity all in one place?...
> +
> inact_en = adxl313_is_act_inact_en(data, ADXL313_INACTIVITY);
> if (inact_en < 0)
> return inact_en;
>
> + inact_ac_en = adxl313_is_act_inact_en(data, ADXL313_INACTIVITY_AC);
> + if (inact_ac_en < 0)
> + return inact_ac_en;
> +
> + inact_en = inact_en || inact_ac_en;
> +
> en = en && act_en && inact_en;
en = en && (act_dc_en || act_ac_en) && (inact_dc_en || inact_ac_en);
>
> return regmap_assign_bits(data->regmap, ADXL313_REG_POWER_CTL,
next prev parent reply other threads:[~2025-06-22 11:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-15 22:22 [PATCH v5 0/8] iio: accel: adxl313: add power-save on activity/inactivity Lothar Rubusch
2025-06-15 22:22 ` [PATCH v5 1/8] iio: accel: adxl313: make use of regmap cache Lothar Rubusch
2025-06-22 11:12 ` Jonathan Cameron
2025-06-15 22:22 ` [PATCH v5 2/8] iio: accel: adxl313: add function to enable measurement Lothar Rubusch
2025-06-22 11:13 ` Jonathan Cameron
2025-06-15 22:22 ` [PATCH v5 3/8] iio: accel: adxl313: add buffered FIFO watermark with interrupt handling Lothar Rubusch
2025-06-16 9:32 ` Andy Shevchenko
2025-06-17 9:27 ` Lothar Rubusch
2025-06-22 11:28 ` Jonathan Cameron
2025-06-15 22:22 ` [PATCH v5 4/8] iio: accel: adxl313: add activity sensing Lothar Rubusch
2025-06-16 9:35 ` Andy Shevchenko
2025-06-15 22:22 ` [PATCH v5 5/8] iio: accel: adxl313: add inactivity sensing Lothar Rubusch
2025-06-16 10:58 ` Andy Shevchenko
2025-06-17 10:10 ` Lothar Rubusch
2025-06-17 11:54 ` Andy Shevchenko
2025-06-15 22:22 ` [PATCH v5 6/8] iio: accel: adxl313: implement power-save on inactivity Lothar Rubusch
2025-06-15 22:22 ` [PATCH v5 7/8] iio: accel: adxl313: add AC coupled activity/inactivity events Lothar Rubusch
2025-06-16 11:08 ` Andy Shevchenko
2025-06-22 11:37 ` Jonathan Cameron [this message]
2025-06-15 22:22 ` [PATCH v5 8/8] docs: iio: add ADXL313 accelerometer Lothar Rubusch
2025-06-16 10:59 ` [PATCH v5 0/8] iio: accel: adxl313: add power-save on activity/inactivity Andy Shevchenko
2025-06-17 1:14 ` Bagas Sanjaya
2025-06-25 8:15 ` Lothar Rubusch
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=20250622123752.1834fbe2@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=dlechner@baylibre.com \
--cc=l.rubusch@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.p.stankus@gmail.com \
--cc=nuno.sa@analog.com \
/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;
as well as URLs for NNTP newsgroup(s).