From: Tony Lindgren <tony@atomide.com>
To: Tero.Kristo@nokia.com
Cc: linux-omap@vger.kernel.org
Subject: Re: getnstimeofday() and suspend
Date: Wed, 13 Aug 2008 17:00:19 +0300 [thread overview]
Message-ID: <20080813140016.GE27446@atomide.com> (raw)
In-Reply-To: <B71CE868F2BC2847B3F23C5A8EE394305AB785@vaebe110.NOE.Nokia.com>
* Tero.Kristo@nokia.com <Tero.Kristo@nokia.com> [080813 15:59]:
> Hi,
>
> I noticed an interesting feature in the getnstimeofday() function when
> used with suspend. System clock is effectively reset to the value it was
> just before suspend. You can see this behavior e.g. with this command
> line:
>
> date && echo mem > /sys/power/state && date
>
> With approx. 2 minutes in suspend state the output for me was this:
>
> / # date && echo mem > sys/power/state && date
> Thu Jan 1 00:13:40 UTC 1970PM: Syncing filesystems ...
> done.
> Freezing user space processes ... (elapsed 0.00 seconds) done.
> Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
> Suspending console(s)
> Successfully put all powerdomains to target state
> Restarting tasks ... done.
> Thu Jan 1 00:13:42 UTC 1970
>
> I.e., the calendar clock was only advanced 2 seconds. The time you spend
> in suspend does not matter, the end result is the same, it will reset
> the time to the value it was before suspend.
>
> Is this behavior intended?
Hmm, well it should get the value straight from the 32KiHZ sync timer.
Does that get stopped somehow during suspend?
Tony
next prev parent reply other threads:[~2008-08-13 13:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 12:57 getnstimeofday() and suspend Tero.Kristo
2008-08-13 14:00 ` Tony Lindgren [this message]
2008-08-13 14:46 ` Tero.Kristo
2008-08-15 9:32 ` Tero.Kristo
2008-08-15 9:33 ` Igor Stoppa
2008-08-15 9:55 ` Högander Jouni
2008-08-15 10:10 ` Igor Stoppa
2008-08-15 10:43 ` Tero.Kristo
2008-08-15 10:57 ` Högander Jouni
2008-08-15 14:43 ` Woodruff, Richard
2008-08-13 17:31 ` David Brownell
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=20080813140016.GE27446@atomide.com \
--to=tony@atomide.com \
--cc=Tero.Kristo@nokia.com \
--cc=linux-omap@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox