From: Pavel Machek <pavel@suse.cz>
To: mtk.manpages@gmail.com
Cc: Jonathan Corbet <corbet@lwn.net>,
kernel list <linux-kernel@vger.kernel.org>,
dl9pf@gmx.de, rdunlap@xenotime.net, linux-doc@vger.kernel.org,
Andrew Morton <akpm@osdl.org>, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: Document sysfs interface to RTC system wakeup
Date: Tue, 9 Dec 2008 13:43:21 +0100 [thread overview]
Message-ID: <20081209124320.GC1547@ucw.cz> (raw)
In-Reply-To: <cfd18e0f0811281340r2317a1e4y938e11da27a35558@mail.gmail.com>
On Fri 2008-11-28 16:40:35, Michael Kerrisk wrote:
> On Wed, Nov 26, 2008 at 12:00 PM, Pavel Machek <pavel@suse.cz> wrote:
> >> On Wed, 26 Nov 2008 17:15:24 +0100
> >> Pavel Machek <pavel@suse.cz> wrote:
> >>
> >> > +How to use /sys/class/rtc/rtcX/wakealarm
> >> > +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >> > +This file takes the seconds since epoch to enable a wake event at the
> >> > +specified time.
> >>
> >> More documentation is cool. In this case, though, I'm left with an
> >> immediate question: *why* am I interested in wakealarm? Reading
> >> through, I eventually figure out that it can maybe be used to get a
> >> system to start up at some point in the future, maybe. It seems like
> >> that should be said at the outset.
> >
> > You can suspend/power down your machine, and it will power itself up
> > at appropriate time.
> >
> >> Also; why do I want to migrate from /proc/acpi/alarm?
> >
> > Because /proc/acpi/alarm is ugly hack that is going to go away :-).
>
> And these are the statements that (in slightly more polished terms)
> should be in your doc ;-), in order to address Jonathan's quite
> reasonable questions.
I'm bad at polishing, but I'll add short explanation.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-12-09 12:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 16:15 Document sysfs interface to RTC system wakeup Pavel Machek
2008-11-26 16:56 ` Jonathan Corbet
2008-11-26 17:00 ` Pavel Machek
2008-11-28 21:40 ` Michael Kerrisk
2008-12-09 12:43 ` Pavel Machek [this message]
2008-11-26 17:59 ` Alan Jenkins
2008-12-09 12:40 ` Pavel Machek
2008-11-28 21:49 ` Michael Kerrisk
2008-12-09 12:54 ` 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=20081209124320.GC1547@ucw.cz \
--to=pavel@suse.cz \
--cc=akpm@osdl.org \
--cc=corbet@lwn.net \
--cc=dl9pf@gmx.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=rdunlap@xenotime.net \
--cc=rjw@sisk.pl \
/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