Am Freitag, 24. September 2004 22:15 schrieb Alan Stern:
> Here's an example. �Suppose the device is in D2 when suspend-to-disk
> starts. �Assume it's a PCI device, so the driver doesn't need to do
> anything more to idle it, and thus the last state the driver remembers is
> that the device was in D2. �That fact gets stored in the memory image. �
> Later on the system reboots and the compiled-in driver initializes the
> device to its fully-powered D0 state. �The resume-from-disk procedure
> begins by asking drivers to idle their devices in preparation for
> restoring the memory image. �Let's assume this device doesn't perform DMA
> or generate IRQs even when it's in D0, so the driver leaves it there. �
> The memory image is restored and all devices are resumed. �Now the device
> really is in D0, but the driver's last memory is of putting it into D2,
> since that value was stored in the image.
Ignore what I wrote last. Resume is:
int (*resume) (struct device * dev, u32 level);
Resumption from D0 would be a little odd, but that's what is required.
Regards
Oliver
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
