On Mon, Jan 08, 2007 at 12:39:08PM -0800, David Brownell wrote: > In that current API there's no way to tell anything at all about the > target system state inside a driver's suspend() method. So if there > were some characteristic of S4 (or S3 etc) that mattered to the driver > (it should test for the attribute, not S4/etc since S4 is ACPI-specific) > the driver couldn't do anything about it ... so as I said, not useful. Well, it's not just a matter for the driver - in terms of userspace UI, we want to be able to expose which wakeup events will work in suspend to disk. If the API can't currently expose that, then we probably want to look into ways of fixing that. -- Matthew Garrett | mjg59 at srcf.ucam.org
