Re: Hotplug events for system suspend/resume

[Todd Poynor]

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