* Oliver Neukum <oliver@xxxxxxxxxx> wrote: > Am Montag, 8. Juni 2009 15:22:35 schrieb Ingo Molnar: > > > What will the 'user space policy' bit do what the kernel cannot? > > > > If you mean the user has to configure something manually - that > > wont really happen in practice. We are happy if they know where > > to put those USB sticks in ;-) > > User space need not be the user. Currently user space doesn't tell > the kernel how much functionality it needs. open/close give a > binary opposition which badly maps onto the graduated capabilities > devices have. If the kernel isnt told what capabilities are used that's buggy code then. > For example do you really need every key pressed while the screen > saver is running or is it enough for the keyboard to be able to > generate a wakeup event? The sane default here is to suspend the keyboard, except if an audio app is running that binds to the volume keys of the keyboard. If the 'keyboard' is properly abstracted in the kernel and the kernel driver _knows_ that the volume keys are in use, this is not a problem. Arguing otherwise is just saying the equivalent of: "we have a broken model to utilize hardware, and instead of fixing it properly, introduce an _even more broken_ model, because in the current model things cannot be made to work". The kernel _needs_ to have precise information about whether a piece of hardware is in use or not. Ingo -- 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
