From: Todd Poynor <tpoynor@mvista.com>
To: Greg KH <greg@kroah.com>
Cc: mochel@digitalimplant.org,
linux-hotplug-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: Hotplug events for system suspend/resume
Date: Wed, 12 May 2004 00:39:45 +0000 [thread overview]
Message-ID: <40A17251.2000500@mvista.com> (raw)
In-Reply-To: <20040511230001.GA26569@kroah.com>
Greg KH wrote:
> I still do not see the need for this. As a user, you caused the
> suspend/resume event to happen, why get notified of it again? :)
The idea is to notify the "power management application" of impending
suspend and just-completed resume, regardless of who or what asked for
the suspend. Actions taken at suspend might include dropping network
connections and saving application state to stable storage.
The reasons for which this was requested of me as a kernel-to-userspace
notifier, that I am aware of, are:
(a) some embedded platforms currently trigger suspend within kernel
drivers (in response to a button press or some sort of device timeout).
(b) the system designer wants to make sure certain actions are always
taken regardless of the interface used to suspend (not only in the case
of a certain application that incorporates these actions and triggers
the suspend via the standard interfaces at the appropriate time). For
example, a user manually enters a command from a shell prompt.
But again, I'll let the embedded system designers jump in here if they'd
like to add some insight. In both of the above cases, some ad-hoc
method of kernel-to-userspace notification could be used, but I am
trying to gauge interest in using hotplug as a generic notifier for these.
Thanks -- Todd
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
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-12 0:39 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 [this message]
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
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=40A17251.2000500@mvista.com \
--to=tpoynor@mvista.com \
--cc=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.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;
as well as URLs for NNTP newsgroup(s).