From: Todd Poynor <tpoynor@mvista•com>
To: Hollis Blanchard <hollis@austin•ibm.com>
Cc: devel list <linuxppc-dev@lists•linuxppc.org>
Subject: Re: RFC: 405LP sleep
Date: Thu, 19 Dec 2002 13:36:24 -0800 [thread overview]
Message-ID: <3E023BD8.8050107@mvista.com> (raw)
In-Reply-To: <1040330490.29647.340.camel@granite.austin.ibm.com>
+int alarm_secs;
+int cdiv;
+char mode[16] = "standby"; /* "clock-suspend", "power-down",
"standby" */
+int attempts; /* debugging */
Suggest more unique names for these globals.
+ jiffies += rtc_secs_elapsed * HZ;
If jiffies is jumped forward then can kernel events (such as those
waiting on a kernel timer) be missed? Whether or not timer queues et al
are processed on wakeup, not sure if it's harmful to update the "kernel
time" when the kernel has done nothing during the sleep interval, maybe
causing various timeouts. Has this been tried with applications like X
running and verified not to kill apps on wakeup?
Matt Locke and I have been discussing whether it's best to update wall
clock time but leave jiffies alone, since "kernel time" did not advance
during the sleep interval. It's a little worrisome: the kernel advances
time by 10ms for its own operations, but wallclock time (xtime and RTC)
jumps forward 10 minutes. We've tried this a little bit on a TI OMAP
and haven't seen anything die so far, but I imagine there'll be some
application that isn't happy about the situation no matter what choice
is made.
--
Todd
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-12-19 21:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-19 20:41 RFC: 405LP sleep Hollis Blanchard
2002-12-19 21:36 ` Todd Poynor [this message]
2002-12-20 23:31 ` Hollis Blanchard
2002-12-23 15:03 ` Tom Rini
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=3E023BD8.8050107@mvista.com \
--to=tpoynor@mvista$(echo .)com \
--cc=hollis@austin$(echo .)ibm.com \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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