From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Daniel Drake <dsd@laptop.org>
Cc: linux-pm@lists.linux-foundation.org
Subject: Re: Trying to understand new wakeup events architecture
Date: Wed, 12 Jan 2011 21:02:44 +0100 [thread overview]
Message-ID: <201101122102.44482.rjw@sisk.pl> (raw)
In-Reply-To: <AANLkTi=PL_tzxEnfKGjP4Qjv_jNyR-c95W8-caXfG2vo@mail.gmail.com>
On Wednesday, January 12, 2011, Daniel Drake wrote:
> Hi Rafael,
>
> On 16 December 2010 14:39, Daniel Drake <dsd@laptop.org> wrote:
> > On 15 December 2010 22:33, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> >> I guess it's sufficient to read the article at http://lwn.net/Articles/416690/
> >> (or the PDF linked from there is that's not enough :-)).
> >
> > Thanks, that helps a lot.
> >
> >> I don't really think it solves your problem right now, because it's only a
> >> high-level framework and it's missing some mechanics for this purpose.
> >
> > OK, so we'll push for a sysfs node that can be used by userspace to
> > determine the wakeup source.
>
> How do you feel about us using power_kobj to create
> /sys/power/wakeup_source from inside our OLPC code?
> This would include a textual representation of the last wakeup source.
>
> Alternatively we could put it as a sysfs attribute of our own platform device.
I'm basically fine with /sys/power/source as long as its contents are generally
suitable. What exactly do you want to show up in that file?
Rafael
next prev parent reply other threads:[~2011-01-12 20:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 17:57 Trying to understand new wakeup events architecture Daniel Drake
2010-12-15 22:33 ` Rafael J. Wysocki
2010-12-16 14:39 ` Daniel Drake
2011-01-12 15:01 ` Daniel Drake
2011-01-12 20:02 ` Rafael J. Wysocki [this message]
2011-01-13 15:06 ` Daniel Drake
2011-01-13 15:14 ` Alan Stern
2011-01-13 15:56 ` Daniel Drake
2011-01-13 16:55 ` Alan Stern
2011-01-13 19:34 ` Rafael J. Wysocki
2011-01-13 20:01 ` Daniel Drake
2011-01-13 20:31 ` Alan Stern
2011-01-13 20:41 ` Daniel Drake
2011-01-14 2:11 ` Paul Fox
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=201101122102.44482.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=dsd@laptop.org \
--cc=linux-pm@lists.linux-foundation.org \
/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