Date: Thu, 5 Jan 2006 16:02:29 -0800 (PST)
From: Patrick Mochel <mochel@digitalimplant.org>
To: Preece Scott-PREECE <scott.preece@motorola.com>
cc: Pavel Machek <pavel@ucw.cz>, Alan Stern <stern@rowland.harvard.edu>,
       "" <akpm@osdl.org>, "" <linux-pm@lists.osdl.org>,
       "" <linux-kernel@vger.kernel.org>
Subject: RE: [linux-pm] [patch] pm: fix runtime powermanagement's /sys
 interface
In-Reply-To: <ADE4D9DBCFC3A345AAA95C195F62B6DDD3AD5D@de01exm64.ds.mot.com>
Message-ID: <Pine.LNX.4.50.0601051558100.10428-100000@monsoon.he.net>
References: <ADE4D9DBCFC3A345AAA95C195F62B6DDD3AD5D@de01exm64.ds.mot.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1187
Lines: 29


On Thu, 5 Jan 2006, Preece Scott-PREECE wrote:

> This is, of course, in an embedded framework rather than a desktop
> framework - we suspend and wakeup automatically, not via user
> intervention. Answering a question asked in another piece of mail, we
> have roughly a dozen different devices that cause the system to wakeup -
> keypad press, touchscreen touch, flip open/close, etc.

Hmm, it would be nice if that comment was in reply to the email in which
it came. At least if it was in the same thread..

Many systems have > 1 _possible_ wakeup devices (keyboard, touchscreen,
lid, etc). You implied that when a system wakes up, there could be > 1
device that actually woke the system up, which is in direct conflict with
what I've always assumed - that when a system wakes up, it is caused by a
single device (and if there were multiple events, like a key press *and* a
mouse movement, it's doesn't really matter)..

Thanks,


	Patrick

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/