From: Francesco Lavra <flavra@baylibre.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "Lorenzo Bianconi" <lorenzo@kernel.org>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] iio: imu: st_lsm6dsx: Decouple sensor ODR from FIFO batch data rate
Date: Fri, 10 Oct 2025 20:44:50 +0200 [thread overview]
Message-ID: <aa0fc9e1bf78b9390642e80db3fc1c51e6217e95.camel@baylibre.com> (raw)
In-Reply-To: <CAHp75VfOfeS21=5SK6Qa9Fc-WQdjDkz1ecoTFrk=hT1NGGt0TA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2217 bytes --]
On Fri, 2025-10-10 at 17:55 +0300, Andy Shevchenko wrote:
> On Thu, Oct 9, 2025 at 8:36 PM Francesco Lavra <flavra@baylibre.com>
> wrote:
> >
> > The rate at which accelerometer or gyroscope sensor samples are fed
> > to the hardware FIFO (batch data rate, or BDR) does not have to
> > coincide with the sensor sampling frequency (output data rate, or
> > ODR); the only requirement is for the BDR to not be greater than
> > the ODR. Having a BDR lower than the ODR is useful in cases where
> > an application requires a high sampling rate for accurate detection
> > of motion events (e.g. wakeup events), but wants to read sensor
> > sample values from the device buffer at a lower data rate.
> > To support the above use case, add a sampling_frequency sysfs
> > attribute to the buffer directory of st_lsm6dsx IIO devices, which
> > controls the BDR for a given sensor independently from the "main"
> > sampling_frequency attribute (which controls the ODR); introduce a
> > new `bdr` field in struct st_lsm6dsx_sensor to keep track of the
> > current BDR value, and use this field instead of the `odr` field in
> > the code that deals with the FIFO data rate. In the sensor hub
> > driver, make the bdr value always mirror the odr value, since there
> > is no separate configuration setting to control the BDR for data
> > produced by the sensor hub functionality.
>
> ...
>
> > - *max_odr = max_t(u32, *max_odr, sensor->odr);
> > - *min_odr = min_t(u32, *min_odr, sensor->odr);
> > + *max_odr = max_t(u32, *max_odr, sensor->bdr);
> > + *min_odr = min_t(u32, *min_odr, sensor->bdr);
>
> Can we get rid of '_t' parts at some point? Or IOW what is the good
> justification for typed macros here?
I think they are not justified here, I will get take this opportunity to
get rid of them.
> ...
>
> > + ret = iio_str_to_fixpoint(buf, 100, &integer, &fract);
> > + if (ret)
> > + return ret;
> > + bdr = integer * 1000 + fract;
>
> MILLI?
If you mean replacing fract with milli, will do.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2025-10-10 18:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 17:36 [PATCH 0/2] iio: imu: st_lsm6dsx: Decouple sensor ODR from FIFO batch data rate Francesco Lavra
2025-10-09 17:36 ` [PATCH 1/2] iio: imu: st_lsm6dsx: Fix measurement unit for odr struct member Francesco Lavra
2025-10-09 20:40 ` Lorenzo Bianconi
2025-10-09 17:36 ` [PATCH 2/2] iio: imu: st_lsm6dsx: Decouple sensor ODR from FIFO batch data rate Francesco Lavra
2025-10-09 22:30 ` Lorenzo Bianconi
2025-10-10 7:12 ` Francesco Lavra
2025-10-10 8:13 ` Lorenzo Bianconi
2025-10-10 9:28 ` Francesco Lavra
2025-10-10 13:15 ` Lorenzo Bianconi
2025-10-10 15:50 ` David Lechner
2025-10-10 16:22 ` Lorenzo Bianconi
2025-10-10 16:23 ` Andy Shevchenko
2025-10-10 18:35 ` Francesco Lavra
2025-10-10 14:55 ` Andy Shevchenko
2025-10-10 18:44 ` Francesco Lavra [this message]
2025-10-15 14:34 ` Andy Shevchenko
2025-10-10 17:44 ` Jonathan Cameron
2025-10-10 18:50 ` Francesco Lavra
-- strict thread matches above, loose matches on Subject: below --
2025-10-16 17:21 [PATCH v2 0/2] " Francesco Lavra
2025-10-16 17:21 ` [PATCH 2/2] " Francesco Lavra
2025-10-16 20:22 ` Lorenzo Bianconi
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=aa0fc9e1bf78b9390642e80db3fc1c51e6217e95.camel@baylibre.com \
--to=flavra@baylibre.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@kernel.org \
--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