public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Drake <dsd@laptop.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-pm@lists.linux-foundation.org
Subject: Re: Trying to understand new wakeup events architecture
Date: Thu, 13 Jan 2011 15:06:28 +0000	[thread overview]
Message-ID: <1294931188.2244.5.camel@polyethylene> (raw)
In-Reply-To: <201101122102.44482.rjw@sisk.pl>

On Wed, 2011-01-12 at 21:02 +0100, Rafael J. Wysocki wrote:
> > 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?

Do you mean /sys/power/source or /sys/power/wakeup_source? I prefer the
latter as the first one sounds like "power source" (AC, battery,
solar, ...)

As for contents, it will read back a string. One of:

rtc alarm
power button
lid
key press
battery
battery state changed
battery error
ebook
wlan packet
ac power
battery critical
gp timer
hda
usb
unknown

Thanks,
Daniel

  reply	other threads:[~2011-01-13 15:06 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
2011-01-13 15:06         ` Daniel Drake [this message]
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=1294931188.2244.5.camel@polyethylene \
    --to=dsd@laptop.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --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