From: jouni.hogander@nokia.com (Högander Jouni)
To: igor.stoppa@nokia.com
Cc: "ext Tero.Kristo@nokia.com" <Tero.Kristo@nokia.com>,
tony@atomide.com, linux-omap@vger.kernel.org
Subject: Re: getnstimeofday() and suspend
Date: Fri, 15 Aug 2008 13:57:53 +0300 [thread overview]
Message-ID: <87r68qmtou.fsf@trdhcp146196.ntc.nokia.com> (raw)
In-Reply-To: <1218795052.28834.40.camel@localhost> (Igor Stoppa's message of "Fri, 15 Aug 2008 10:10:52 +0000")
Igor Stoppa <igor.stoppa@nokia.com> writes:
> On Fri, 2008-08-15 at 12:55 +0300, Högander Jouni wrote:
>
>> Using them both would also generate more complexity. What would be the
>> benefit in using them both?
>
> The RTC should be used during suspend since it's supposed to keep track
> of time regardless of how long the duration of the suspension is.
>
> The 32kHz alone is not a good generic solution since it overflows after
> a couple of days.
Yes you are right on that timer overflow. How generic this is, I'm not
sure. This is only for measuring time pwrdms spent in their states on
suspend. How about removing that time from pm debug interfaces? They
are meant for debugging dynamic sleep anyway.
--
Jouni Högander
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-08-15 10: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
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 [this message]
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=87r68qmtou.fsf@trdhcp146196.ntc.nokia.com \
--to=jouni.hogander@nokia.com \
--cc=Tero.Kristo@nokia.com \
--cc=igor.stoppa@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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