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