Hi! > > > > This is just a RFC patch, not tested yet. Original post about > > > > motivation > > > > about this patch is there: https://lkml.org/lkml/2014/11/29/92 > > > > > > Having implemented something of that ilk in user-space (we > > > automatically disable touch devices when the associated screen is > > > turned off/suspended), I think this might need more thought. > > > > How to implement such thing in userspace? I think you cannot do that > > without rewriting every one userspace application which uses input. > > In case integrated device is absolutely unusable and generates > > always > > random events, it does not solve problem at boot time. > > > > But more real case is laptop with closed LID press buttons and here > > it > > is useful. > > There's usually a display manager in between the application and the > input device. Whether it's X.org, or a Wayland compositor. Even David's > https://github.com/dvdhrm/kmscon could help for console applications. We'd really like it to work on plain old text console, too, because that's what I'm using on n900, and with old maemo userspace, because that's what everyone else uses. You mentioned you think X.org can do this kind of device disabling (and powersave). Would you have an idea how to activate that? I'd like to disable touchscreen and most of the buttons when the device is "in the pocket". Best regards, 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
