On Wed, 9 Sep 2015, Oliver Neukum wrote: > On Tue, 2015-09-08 at 10:44 -0400, Alan Stern wrote: > > It would not put the device into runtime suspend immediately, like you > > are proposing. Instead it would mean the same as the "auto" mode, > > except that remote wakeup should be disabled during runtime suspend. > > Hi, > > this proposal is incomplete. If you don't want remote wakeup you > imply that input is no longer needed or possible. If that is > already known, we can just as well inform the driver, so that > it can cease IO for input. Like I said, it was never implemented. For that reason, it was never completely fleshed out. > Yet that is not necessarily the only scenario. For example > if you run a screensaver, you might not care for where the > user touches the screen, but the event as such is valuable. I suspect it's not worth the effort to distinguish between getting an event with all the details and merely knowing that an event occurred. Alan Stern -- 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
