On Mon, Jun 08, 2009 at 04:44:55PM +0200, Ingo Molnar wrote: > > * Matthew Garrett <mjg59@xxxxxxxxxxxxx> wrote: > > No, we can't just close it - then we won't get notification that a > > key's been hit in order to unlock the screensaver. [...] > > Looks like a broken notification model. We've closed the input device. Where are we supposed to get the input event from? > > [...] Yes, we can greatly expand the userland-visible interface to > > every piece of hardware in order to make this work, but that's a > > huge amount of effort to avoid a model where userspace sets some > > tunables appropriately. > > What huge amount of effort? All you are doing is to track the "is > the device really used" state in user-space - and, if the current > desktop experience is any measure, highly imperfectly so. > > What i'm suggesting is to track it properly in the kernel. It's not > like the kernel doesnt need to know whether a piece of hardware is > under use or not ... So, for instance, we need to add interfaces like "I care about hotplug events on this SATA port" and "I'm listening for these keys so please don't suspend the device" and "The service bound to this port needs to maintain network connectivity and the one bound to this port doesn't, so only put the wireless card into deep powersave if the first exits", and then we need to wait for userspace to adopt these interfaces before we can enable any of the functionality because otherwise old userspace will be broken with new kernels. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx -- 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
