All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Nyekjaer <sean@geanix.com>
To: Lorenzo Bianconi <lorenzo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel <linux-kernel@vger.kernel.org>
Cc: linux-iio <linux-iio@vger.kernel.org>
Subject: Re: IIO timestamp get skewed when suspending (st_lsm6dsx)
Date: Mon, 8 Jun 2020 14:20:40 +0200	[thread overview]
Message-ID: <fbef0ac8-e313-c20c-9300-9dee00588102@geanix.com> (raw)
In-Reply-To: <2d8b2b9b-5e63-1254-04d9-8b9be0d91877@geanix.com>

Hi Thomas,

I have a question regarding CLOCK_REALTIME and CLOCK_BOOTTIME when 
resuming from suspend.

We have run into problems with 
drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c + the first patch from 
Lorenzo Bianconi in this thread.
The accelerometer have an internal FIFO that includes a timestamp. When 
we resume from suspend,
the driver resets the fifo ts counter and sets an internal reference to 
that time.
But to me it looks like both CLOCK_REALTIME and CLOCK_BOOTIME aren't 
ready when st_lsm6dsx_resume() is called.

If this is a limitation, can you point to other drivers that have been 
able to workaround it?
Or can we wait for a flag or similar?

Best regards,
Sean Nyekjaer


  reply	other threads:[~2020-06-08 12:26 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28 18:01 IIO timestamp get skewed when suspending (st_lsm6dsx) Sean Nyekjaer
2020-05-28 21:07 ` 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 [this message]
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=fbef0ac8-e313-c20c-9300-9dee00588102@geanix.com \
    --to=sean@geanix.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenzo@kernel.org \
    --cc=tglx@linutronix.de \
    /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.