From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: Len Brown <lenb@kernel.org>
Cc: Pavel Machek <pavel@ucw.cz>,
"linux-acpi@vger" <linux-acpi@vger.kernel.org>,
Alessandro Zummo <alessandro.zummo@towertech.it>,
linux-pm@lists.osdl.org, Paul Sokolovsky <pmiscml@gmail.com>
Subject: Re: [linux-pm] [PATCH 3/6] [-mm]: ACPI: duplicate ACPI sleep "alarm" attribute in sysfs
Date: Fri, 26 Jan 2007 10:28:50 +1100 [thread overview]
Message-ID: <1169767730.1316.58.camel@nigel.suspend2.net> (raw)
In-Reply-To: <200701251812.21180.lenb@kernel.org>
Hi.
On Thu, 2007-01-25 at 18:12 -0500, Len Brown wrote:
> On Thursday 25 January 2007 14:47, Pavel Machek wrote:
> > Hi!
> >
> > > > Note that a few RTCs ignore rtc_wkalrm.enabled when setting alarms, or
> > > > aren't set up correctly, so they won't yet behave with this attribute.
> > > >
> > > > Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
> > >
> > > How do I ask to wake up "as soon as possible"?
> >
> > If you want to wake up ASAP, don't go to sleep :-).
> >
> > I see it might be handy for debugging... but I guess we should not
> > mess rtc design because of that. Just set alarm 10 seconds into
> > future.
>
> That's my point.
> What is the syntax to request "10-seconds into the future"?
AFAIK (and I think this is what Pavel is saying) there isn't one - you'd
have to use a shell script of some sort or such like to calculate now +
10s and echo the result to the entry.
Regards,
Nigel
next prev parent reply other threads:[~2007-01-25 23:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-06 11:35 [PATCH 3/6] [-mm]: ACPI: duplicate ACPI sleep "alarm" attribute in sysfs Zhang Rui
2007-01-06 22:42 ` David Brownell
2007-01-07 5:57 ` [linux-pm] " Matthew Garrett
2007-01-08 2:31 ` David Brownell
2007-01-08 10:10 ` Matthew Garrett
2007-01-08 20:39 ` David Brownell
2007-01-08 20:43 ` Matthew Garrett
2007-01-08 21:15 ` David Brownell
2007-01-08 10:13 ` Zhang Rui
2007-01-08 20:46 ` David Brownell
2007-01-07 11:19 ` Pavel Machek
2007-01-08 3:44 ` David Brownell
2007-01-08 11:36 ` Pavel Machek
2007-01-08 20:35 ` David Brownell
2007-01-25 4:21 ` Len Brown
2007-01-25 9:39 ` [linux-pm] " David Brownell
2007-01-25 19:47 ` Pavel Machek
2007-01-25 23:12 ` Len Brown
2007-01-25 23:28 ` Nigel Cunningham [this message]
2007-01-26 0:33 ` David Brownell
2007-01-26 17:07 ` Pavel Machek
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=1169767730.1316.58.camel@nigel.suspend2.net \
--to=nigel@nigel.suspend2.net \
--cc=alessandro.zummo@towertech.it \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@ucw.cz \
--cc=pmiscml@gmail.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