On Thu, Jul 17, 2014 at 01:11:31AM +0200, Rafael J. Wysocki wrote: > Let me try to understand the scenario in the first place. > > To start with, a number of devices is in use (that is, open, there are > applications listening/talking to them etc). Now, an event happens, such > as a laptop lid close and you want some of those devices, but possibly > not all of them, to quiesce themselves and go into low-power states. > > Is that correct? Yes, that is accurate. The primary example is a laptop with an external monitor and mouse attached which you're using with the lid closed. You want the mouse to work, but input from the touchpad that might result from the lid being close to it should be skipped. Also, the touchpad should enter a low-power state. We think that triggering this is probably best done in userspace, but we would need a way of telling devices to quiesce themselves. And as Oliver has pointed out, it might be desirable to preserve some state/settings of devices. And it's probably undesirable to go through the whole process of completely unregistering the device and then probing/resetting/configuring it again. Kind regards, Patrik -- 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
