[lkml]   [2004]   [May]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] Hotplug for device power state changes
Nigel Cunningham wrote:

> Given this model, I would suggest that hotplug should silently drop any
> events that happen while suspending, and queue events that occur while
> resuming until the kernelspace part of resuming is complete and
> userspace can run as normal. It shouldn't rely upon device
> suspend/resume notifications because they can and do happen while we're
> still in the process of suspending and resuming. The means to detect
> whether we're suspending or resuming or running normally could be
> implemented as a simple function that could test the status of the
> different suspend implementations.

If needed, there's already a "system_running" flag used to ignore the
underlying usermode helper execution if requested prior to the system
being ready for such an event at boot time, and perhaps this could be
co-opted or extended for use at suspend/resume time. Sounds like the
correct behavior is to leave the exec requests queued until userspace is
resumed (and I'd assume that device power state notifications are not
needed, but perhaps hotplug events and/or modprobes of drivers for
hotpluggable devices and associated features may be generated at resume
time). Thanks,

Todd Poynor
MontaVista Software

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:02    [W:0.064 / U:9.628 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site