public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Leo L. Schwab" <ewhac@best.com>
To: linux-pm@osdl.org
Subject: Re: What woke system up?
Date: Wed, 4 Jan 2006 10:21:16 -0800	[thread overview]
Message-ID: <20060104182116.GA17218@best.com> (raw)
In-Reply-To: <20051222034630.GA4320@slurryseal.ddns.mvista.com>

[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]

On Wed, Dec 21, 2005 at 07:46:30PM -0800, Todd Poynor wrote:
> On Tue, Dec 20, 2005 at 06:11:40PM -0800, Patrick Mochel wrote:
> > What about stashing a pointer to the device that did the wakeup, then
> > using a symlink to point to the sysfs directory of that device?  [ ... ]
> 
> Sounds good, here's a new version that does just that.  [ ... ]

	I'm entering this discussion late, but if I were putting this
together:
	- There would be a single file named /sys/power/wake,
	- Upon resume, the file would contain lines of plaintext of the
	  format:

		device: reason

	- 'device' names the device that performed the wakeup.  'device'
	  could be either a sysfs path or a /dev/blah/blah path (sysfs is
	  probably better, if more verbose, as it remains consistent
	  regardless of how /dev is configured),
	- 'reason' is free-form text, supplied by the device performing the
	  wakeup, and is entirely device-dependent.

	This approach allows multiple wakeup sources (rare, but possible),
and also allows a single multifunction device to report multiple reasons for
a wakeup.  It's also darned simple to parse.

	IMHO, of course.

					Schwab

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2006-01-04 18:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-21  0:29 What woke system up? Todd Poynor
2005-12-21  2:11 ` Patrick Mochel
2005-12-22  3:46   ` Todd Poynor
2006-01-04 18:21     ` Leo L. Schwab [this message]
2006-01-05 15:08       ` Pavel Machek
2006-01-05 21:28       ` Patrick Mochel
2006-01-06  2:27         ` Todd Poynor
2005-12-22 10:58 ` 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=20060104182116.GA17218@best.com \
    --to=ewhac@best.com \
    --cc=linux-pm@osdl.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