From: Sean Nyekjaer <sean@geanix.com>
To: linux-iio <linux-iio@vger.kernel.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Lorenzo Bianconi <lorenzo@kernel.org>
Subject: IIO timestamp get skewed when suspending (st_lsm6dsx)
Date: Thu, 28 May 2020 20:01:55 +0200 [thread overview]
Message-ID: <54cb146d-e54e-acae-e89c-075521b8e7dc@geanix.com> (raw)
Hi,
I don't know if it's normal behavior or maybe just a problem related to
the buffered reads in st_lsm6dsx.
But when we have the buffered reads enabled and suspending for x amount
of time. The iio timestamps is, x amount of time is delayed. As seen here:
https://gist.github.com/sknsean/60e20c2fa3a3c6d69ef128c703ed43fc
From your own software (but I'm able to reproduce with libiio/iio_readdev)
First col is system time,
Second timestamp is the iio timestamp
Could a solution, be to call st_lsm6dsx_reset_hw_ts() in
st_lsm6dsx_resume() ?
/Sean
next reply other threads:[~2020-05-28 18:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 18:01 Sean Nyekjaer [this message]
2020-05-28 21:07 ` IIO timestamp get skewed when suspending (st_lsm6dsx) Lorenzo Bianconi
2020-05-29 7:32 ` Sean Nyekjaer
2020-05-29 7:44 ` Lorenzo Bianconi
2020-05-29 8:33 ` Sean Nyekjaer
2020-05-29 8:50 ` Lorenzo Bianconi
2020-05-29 11:19 ` Sean Nyekjaer
2020-05-29 12:16 ` Lorenzo Bianconi
2020-05-29 12:29 ` Sean Nyekjaer
2020-06-02 11:48 ` Sean Nyekjaer
2020-06-02 13:39 ` Sean Nyekjaer
2020-06-02 18:02 ` Sean Nyekjaer
2020-06-03 8:06 ` Lorenzo Bianconi
2020-06-03 10:05 ` Sean Nyekjaer
2020-06-03 10:28 ` Lorenzo Bianconi
2020-06-03 10:37 ` Sean Nyekjaer
2020-06-03 10:51 ` Lorenzo Bianconi
2020-06-03 11:29 ` Sean Nyekjaer
2020-06-03 12:12 ` Lorenzo Bianconi
2020-06-03 12:49 ` Sean Nyekjaer
2020-06-03 12:56 ` Lorenzo Bianconi
2020-06-03 13:15 ` Sean Nyekjaer
2020-06-03 13:40 ` Lorenzo Bianconi
2020-06-03 14:10 ` Sean Nyekjaer
2020-06-08 12:20 ` Sean Nyekjaer
2020-06-08 14:09 ` Thomas Gleixner
2020-07-10 12:10 ` Sean Nyekjaer
2020-07-10 13:20 ` 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=54cb146d-e54e-acae-e89c-075521b8e7dc@geanix.com \
--to=sean@geanix.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=linux-iio@vger.kernel.org \
--cc=lorenzo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.