From: "lorenzo.bianconi@redhat.com" <lorenzo.bianconi@redhat.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Mario TESI <mario.tesi@st.com>,
Lorenzo Bianconi <lorenzo@kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH] iio: imu: st_lsm6dsx: wait for settling time in st_lsm6dsx_read_oneshot
Date: Sat, 5 Feb 2022 22:54:49 +0100 [thread overview]
Message-ID: <Yf7yKSdbtFr5HSnv@lore-desk> (raw)
In-Reply-To: <20220205174505.16e6d157@jic23-huawei>
[-- Attachment #1: Type: text/plain, Size: 1960 bytes --]
> On Mon, 31 Jan 2022 12:46:56 +0000
> Mario TESI <mario.tesi@st.com> wrote:
>
> > Tested-by: Mario Tesi <mario.tesi@st.com>
> > ________________________________________
> > Da: Lorenzo Bianconi <lorenzo@kernel.org>
> > Inviato: lunedì 31 gennaio 2022 12:08
> > A: jic23@kernel.org
> > Cc: lorenzo.bianconi@redhat.com; linux-iio@vger.kernel.org; Mario TESI
> > Oggetto: [PATCH] iio: imu: st_lsm6dsx: wait for settling time in st_lsm6dsx_read_oneshot
> >
> > We need to wait for sensor settling time (~ 3/ODR) before reading data
> > in st_lsm6dsx_read_oneshot routine in order to avoid corrupted samples.
> >
> > Reported-by: Mario Tesi <mario.tesi@st.com>
> > Signed-off-by: Lorenzo Bianconi <lorenzo@kernel.org>
>
> Fixes tag? This definitely looks like stable material to me
> so we want a clear record of when the issue was introduced.
>
> Thanks,
ack, right. I will add it in v2.
Regards,
Lorenzo
>
> Jonathan
>
>
> > ---
> > drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c | 6 +++++-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c
> > index 727b4b6ac696..93f0c6bce502 100644
> > --- a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c
> > +++ b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c
> > @@ -1374,8 +1374,12 @@ static int st_lsm6dsx_read_oneshot(struct st_lsm6dsx_sensor *sensor,
> > if (err < 0)
> > return err;
> >
> > + /*
> > + * we need to wait for sensor settling time before
> > + * reading data in order to avoid corrupted samples
> > + */
> > delay = 1000000000 / sensor->odr;
> > - usleep_range(delay, 2 * delay);
> > + usleep_range(3 * delay, 4 * delay);
> >
> > err = st_lsm6dsx_read_locked(hw, addr, &data, sizeof(data));
> > if (err < 0)
> > --
> > 2.34.1
> >
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2022-02-05 21:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 11:08 [PATCH] iio: imu: st_lsm6dsx: wait for settling time in st_lsm6dsx_read_oneshot Lorenzo Bianconi
2022-01-31 12:46 ` Mario TESI
2022-02-05 17:45 ` Jonathan Cameron
2022-02-05 21:54 ` lorenzo.bianconi [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=Yf7yKSdbtFr5HSnv@lore-desk \
--to=lorenzo.bianconi@redhat.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=mario.tesi@st.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