On Thursday, 21 June 2007 22:46, David Brownell wrote: > On Thursday 21 June 2007, Rafael J. Wysocki wrote: > > > All of this is fine, but we need some way to tell ACPI what the next sleep > > state will be, because currently _we_ _have_ _not_ one. > > > > So, do we introduce an additional pm_op to do that or are we going to do > > something else? > > Simplest would be an additional op. OK Does anyone have any objections to adding a new pm_op that will tell the ACPI core (or generally, a platform core code) what target system sleep state we are going to enter? Greetings, Rafael -- "Premature optimization is the root of all evil." - Donald Knuth - 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