Re: [RFC][PATCH] PM: Separate suspend and hibernation callbacks (highest level) - updated

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

 



On Monday 10 March 2008, Rafael J. Wysocki wrote:
> + * @poweroff: Hibernation-specific, executed after saving a hibernation image.
> + *     Quiesce the device, put it into a low power state appropriate for the
> + *     upcoming system state (such as PCI_D3hot), and enable wakeup events as
> + *     appropriate.

This seems uncomfortably similar to device_driver.shutdown().
The only obvious difference is wakeup event handling, and even
that is already a function of the target system state.

Are both methods needed?

Shouldn't this be more generic, not "hibernation-specific"?

_______________________________________________
linux-pm mailing list
linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/linux-pm


[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