[linux-pm] [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 26 Apr 2006, Rafael J. Wysocki wrote:

> > So under these circumstances, how does it hurt anything to reset the 
> > resume device rather than to freeze it?
> 
> It just shouldn't be necessary.  Actually I think the resume device shouldn't
> be frozen too.

Well, you wouldn't want it doing DMA to unknown memory areas while you're
trying to place the image data in those same areas, would you?  And when
the image is reactivated, you wouldn't want the device generating
interrupt requests while its driver still thinks it is suspended.  (Or if 
it doesn't even have a driver in the image.)

And don't say that no resume device would ever do DMA or generate IRQs
while it was idle!  What if it was a remote disk accessible via a network 
interface?

Alan Stern


[Index of Archives]     [Linux ACPI]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [CPU Freq]     [Kernel Newbies]     [Fedora Kernel]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux