From: Jonathan Cameron <jic23@kernel.org>
To: Lothar Rubusch <l.rubusch@gmail.com>
Cc: lars@metafoo.de, Michael.Hennerich@analog.com,
cosmin.tanislav@analog.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] iio: accel: adxl367: fix setting odr for activity time update
Date: Sat, 22 Feb 2025 15:03:29 +0000 [thread overview]
Message-ID: <20250222150329.66d6e79b@jic23-huawei> (raw)
In-Reply-To: <20250221203352.41941-1-l.rubusch@gmail.com>
On Fri, 21 Feb 2025 20:33:52 +0000
Lothar Rubusch <l.rubusch@gmail.com> wrote:
> Fix setting the odr value to update activity time based on frequency
> derrived by recent odr, and not by obsolete odr value.
>
> The [small] bug: When _adxl367_set_odr() is called with a new odr value,
> it first writes the new odr value to the hardware register
> ADXL367_REG_FILTER_CTL.
> Second, it calls _adxl367_set_act_time_ms(), which calls
> adxl367_time_ms_to_samples(). Here st->odr still holds the old odr value.
> This st->odr member is used to derrive a frequency value, which is
> applied to update ADXL367_REG_TIME_ACT. Hence, the idea is to update
> activity time, based on possibilities and power consumption by the
> current ODR rate.
> Finally, when the function calls return, again in _adxl367_set_odr() the
> new ODR is assigned to st->odr.
>
> The fix: When setting a new ODR value is set to ADXL367_REG_FILTER_CTL,
> also ADXL367_REG_TIME_ACT should probably be updated with a frequency
> based on the recent ODR value and not the old one. Changing the location
> of the assignment to st->odr fixes this.
>
> Signed-off-by: Lothar Rubusch <l.rubusch@gmail.com>
Fixes tag?
Otherwise looks good to me.
> ---
> drivers/iio/accel/adxl367.c | 10 +++-------
> 1 file changed, 3 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/iio/accel/adxl367.c b/drivers/iio/accel/adxl367.c
> index add4053e7a02..0c04b2bb7efb 100644
> --- a/drivers/iio/accel/adxl367.c
> +++ b/drivers/iio/accel/adxl367.c
> @@ -601,18 +601,14 @@ static int _adxl367_set_odr(struct adxl367_state *st, enum adxl367_odr odr)
> if (ret)
> return ret;
>
> + st->odr = odr;
> +
> /* Activity timers depend on ODR */
> ret = _adxl367_set_act_time_ms(st, st->act_time_ms);
> if (ret)
> return ret;
>
> - ret = _adxl367_set_inact_time_ms(st, st->inact_time_ms);
> - if (ret)
> - return ret;
> -
> - st->odr = odr;
> -
> - return 0;
> + return _adxl367_set_inact_time_ms(st, st->inact_time_ms);
> }
>
> static int adxl367_set_odr(struct iio_dev *indio_dev, enum adxl367_odr odr)
next prev parent reply other threads:[~2025-02-22 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 20:33 [PATCH v1 1/1] iio: accel: adxl367: fix setting odr for activity time update Lothar Rubusch
2025-02-22 15:03 ` Jonathan Cameron [this message]
2025-03-08 21:26 ` Lothar Rubusch
2025-03-09 14:25 ` Marcelo Schmitt
2025-03-09 16:14 ` 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=20250222150329.66d6e79b@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=cosmin.tanislav@analog.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