From: Lothar Rubusch <l.rubusch@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: lars@metafoo.de, Michael.Hennerich@analog.com,
cosmin.tanislav@analog.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org,
Marcelo Schmitt <marcelo.schmitt1@gmail.com>
Subject: Re: [PATCH v2 1/1] iio: accel: adxl367: fix setting odr for activity time update
Date: Mon, 10 Mar 2025 21:53:00 +0100 [thread overview]
Message-ID: <CAFXKEHb1zCpNX_t70dTCM6yBoU=gegcf4bJZyx8iWSEC+ibmMg@mail.gmail.com> (raw)
In-Reply-To: <20250310201042.0e8f06d7@jic23-huawei>
Hi Jonathan,
On Mon, Mar 10, 2025 at 9:10 PM Jonathan Cameron <jic23@kernel.org> wrote:
>
> On Sun, 9 Mar 2025 19:35:15 +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.
> >
> > Fixes: cbab791c5e2a5 ("iio: accel: add ADXL367 driver")
> > Signed-off-by: Lothar Rubusch <l.rubusch@gmail.com>
> > Reviewed-by: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
> > ---
> Change log missing, but I assume it's just the Fixes tag.
> If so, I would have been fine with that just being in a reply
> to the v1. Anyhow, new patch is fine too so applied to the
> fixes-togreg branch of iio.git. I may well queue this up for
> the merge window rather than send another pull request this cycle.
>
Yes, it is actually just the fixes tag and reviewed-by tag. I'm sorry
for the missing log.
Best,
L
> Thanks
>
> Jonathan
>
>
> > 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)
>
prev parent reply other threads:[~2025-03-10 20:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-09 19:35 [PATCH v2 1/1] iio: accel: adxl367: fix setting odr for activity time update Lothar Rubusch
2025-03-10 20:10 ` Jonathan Cameron
2025-03-10 20:53 ` Lothar Rubusch [this message]
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='CAFXKEHb1zCpNX_t70dTCM6yBoU=gegcf4bJZyx8iWSEC+ibmMg@mail.gmail.com' \
--to=l.rubusch@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=cosmin.tanislav@analog.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt1@gmail.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).