From: Pavel Machek <pavel@ucw.cz>
To: Len Brown <lenb@kernel.org>
Cc: linux-pm@lists.osdl.org,
"linux-acpi@vger" <linux-acpi@vger.kernel.org>,
Alessandro Zummo <alessandro.zummo@towertech.it>,
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 18:07:54 +0100 [thread overview]
Message-ID: <20070126170754.GA964@elf.ucw.cz> (raw)
In-Reply-To: <200701251812.21180.lenb@kernel.org>
On Thu 2007-01-25 18:12:20, 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"?
echo $(( $(cat since_epoch) + 10 )) > wakealarm
...which is what you should expect. Yep, for users, nice utility would
be nice... but absence of nice utility does not mean that it belongs
in kernel.
Plus, old alarm file was such a mess that I were not figure out how to
use it within two hours... or maybe it just did not work on my
machine? ... so utility will be needed, anyway.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2007-01-26 17:08 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
2007-01-26 0:33 ` David Brownell
2007-01-26 17:07 ` Pavel Machek [this message]
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=20070126170754.GA964@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=alessandro.zummo@towertech.it \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--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;
as well as URLs for NNTP newsgroup(s).