From: Pavel Machek <pavel@ucw.cz>
To: Todd Poynor <tpoynor@mvista.com>
Cc: ncunningham@linuxmail.org, Greg KH <greg@kroah.com>,
mochel@digitalimplant.org,
linux-hotplug-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: Hotplug events for system suspend/resume
Date: Sat, 15 May 2004 03:03:15 +0000 [thread overview]
Message-ID: <20040515030315.GB460@elf.ucw.cz> (raw)
In-Reply-To: <40A27CB8.1010507@mvista.com>
Hi!
> Hi, my main interest is embedded platforms that may or (usually) do not
> implement ACPI. Therefore, part of what I've been generally driving at
> is that there may be value to adding support for these sorts of
> kernel-to-userspace notifiers in the generic power layer. As I
> understand it (and I might be behind the times here, please do correct
> me if I'm wrong), acpid reads ACPI-specific power event notifiers, such
> as button pressed, thermal limit exceeded, etc. from the kernel via
> /proc, and acpid executes scripts in /etc/acpi/ to handle the event.
> Some of the embedded developers I deal with have asked for similar
> notifiers in a non-ACPI context. The system suspend/resume notifiers
> discussed in this thread could be thought of as a general form of "sleep
> button pressed" type event. (And I now realize it may have been better
> to implement and pitch it as such.)
Well, yes, generic "sleep button pressed" notifier is certainly better
idea. For example it does not have to be synchronous. I actaully like
that.
Is input subsystem any good? It might be as simple as defining keys
for POWER/SLEEP buttons and routing acpi events through even
subsystem...
Pavel
--
When do you have heart between your knees?
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id%62&alloc_ida84&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-05-15 3:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040511010015.GA21831@dhcp193.mvista.com>
2004-05-11 23:00 ` Hotplug events for system suspend/resume Greg KH
2004-05-12 0:39 ` Todd Poynor
2004-05-12 2:16 ` Nigel Cunningham
2004-05-12 2:44 ` Todd Poynor
2004-05-12 3:59 ` Nigel Cunningham
2004-05-12 19:36 ` Todd Poynor
2004-05-15 3:03 ` Pavel Machek [this message]
2004-05-12 15:08 ` Greg KH
2004-05-13 22:46 ` Tim Bird
2004-05-13 23:28 ` Greg KH
2004-05-15 2:59 ` Pavel Machek
2004-05-12 18:52 ` Grover, Andrew
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=20040515030315.GB460@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=ncunningham@linuxmail.org \
--cc=tpoynor@mvista.com \
/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;
as well as URLs for NNTP newsgroup(s).