On Monday 08 January 2007 12:43 pm, Matthew Garrett wrote: > 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 ... may potentially ... > 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. Considering that I've never seen ACPI wakeup GPEs work at all, having them work in the first place -- e.g. from STR -- would need to be a first step. It seems premature to discuss the UI of a tool that can't yet be written on Linux... Agreed, by the way, that drivers need to be able to tell things about the target system sleep state. My original examples come from USB: drivers need to know whether the target state requires disabling specific clocks, which must be active for remote wakeup to work. - Dave - 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
