Disable input device

Disable input device

[Pali Rohár]

[-- Attachment #1: Type: Text/Plain, Size: 1089 bytes --]

Hello,

there is request to introduce some option (via sysfs) to disable 
one input device. Originally it was for tsc2005 touchscreen found 
on Nokia N900 cellphone. Use case is to completely disable 
touchscreen when phone is in pocket or when screen is locked via 
slide switch (to prevent random clicks).

But it would be better to have disable option for all input 
devices. Sometimes input device is not use and only consume 
power. Another case is when input device (e.g. keyboard or 
touchpad) is integrated into machine (e.g. on laptops) and user 
does not want to use it (so make sure that kernel does not send 
events to userspace).

I would like to ask, how to solve it?

What do you think about adding new sysfs file "disable" (accept 
values 1 or 0) for every input device? With "1" it cause that 
kernel will drop all events from specific input device and if 
driver provide some function is can be called (e.g. for power 
management or disabling device at hardware level).

Or do you prefer something other?

-- 
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: Disable input device

[Pavel Machek]

On Sat 2014-11-29 18:24:03, Pali Rohár wrote:
> Hello,
> 
> there is request to introduce some option (via sysfs) to disable 
> one input device. Originally it was for tsc2005 touchscreen found 
> on Nokia N900 cellphone. Use case is to completely disable 
> touchscreen when phone is in pocket or when screen is locked via 
> slide switch (to prevent random clicks).
> 
> But it would be better to have disable option for all input 
> devices. Sometimes input device is not use and only consume 
> power. Another case is when input device (e.g. keyboard or 
> touchpad) is integrated into machine (e.g. on laptops) and user 
> does not want to use it (so make sure that kernel does not send 
> events to userspace).
> 
> I would like to ask, how to solve it?
> 
> What do you think about adding new sysfs file "disable" (accept 
> values 1 or 0) for every input device? With "1" it cause that 
> kernel will drop all events from specific input device and if 
> driver provide some function is can be called (e.g. for power 
> management or disabling device at hardware level).

That makes sense to me. Dmitry, would such interface be acceptable?

									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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Disable input device

[Chuck Ebbert]

On Sat, 29 Nov 2014 18:24:03 +0100
Pali Rohár <pali.rohar@gmail.com> wrote:

> What do you think about adding new sysfs file "disable" (accept 
> values 1 or 0) for every input device? With "1" it cause that 
> kernel will drop all events from specific input device and if 
> driver provide some function is can be called (e.g. for power 
> management or disabling device at hardware level).
> 

Yeah, I'd like to see this too. I am using xinput to disable the
notebook keyboard so the cats walking across it don't cause any
problems. It would be nice to have a better solution.
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html