Hi! > But runtime-pm.txt says for example: > > Generally, remote wake-up should be enabled for all input devices > put into a low power state at run time. > > But in this case the requirement is to suppress input events from a > given device, effectively muting and putting it into low power state, > even though it's still open by some other parties. Runtime PM, on the > other hand tries not to interfere with the normal usage of the device. > > Later: > > (3) ->runtime_idle() and ->runtime_suspend() can only be executed for a > device the usage counter of which is equal to zero _and_ [...] > > which underlines the difference again: the usage counter (defined by > common sense) won't be zero in our case, because the device is > constantly kept open, while we want to mute it, putting it into a low > power state. ... > Actually, this could be implemented by the various users cooperating in > closing the device, letting it go to sleep automatically. But this > requires strictly cooperating parties and is more complicated that > flipping some master switch of the device. We're looking for this > master switch, before needlessly building our own. Please just close the device properly. I do not think we want 100 different 'please mute keys A and G', 'please mute middle mouse button', ... interfaces anywhere near mainline. Or just do it as local patch. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
