Messages in this thread | | | Date | Wed, 10 Sep 2003 02:06:27 +0200 | From | Pavel Machek <> | Subject | Re: [PM] Passing suspend level down to drivers |
| |
Hi!
> > APM suspend-to-ram > > APM suspend-to-disk > > ACPI standby (S1) > > ACPI suspend-to-ram (S3) > > ACPI suspend-to-disk (S4bios) > > swsusp > > > > Do we want to support ACPI S2? I don't think so. That list is not > > *that* bad. > > ACPI S2 is irrelevant. Nonetheless, you're suggesting that we add manual > checks at runtime for each device to determine what state to go into, > depending on whether the system is entering suspend-to-disk or suspend-to- > ram. > > That's a bad idea because: > > - It doesn't need to be done at runtime, only initialization. Though it's > not a permformant path, it's still more efficient to do it once only. > > - It forces policy into the drivers, instead of having them specify a > changeable default.
Okay, so you suggest "driver has table of default things to do on suspend-to-X, changeable by user", while I say "driver has table of default things to do on suspend-to-X". I do not thing changeability by user is so important here, but I'm not going to argue too much about that. Pavel -- When do you have a heart between your knees? [Johanka's followup: and *two* hearts?] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |