Messages in this thread | | | Date | Fri, 6 Jan 2012 12:02:40 -0800 | From | Dmitry Torokhov <> | Subject | Re: [PATCH v2] Input: evdev - Add EVIOC mechanism to extract the MT slot state |
| |
On Fri, Jan 06, 2012 at 08:48:15PM +0100, Henrik Rydberg wrote: > > > Ok, maybe not to so easy after all, which probably answers my own > > > question. Looks like a EVIOCGMTSLOT, taking both slot and event code > > > as argument, would be the cleaner route to take. Another ioctl, how do we > > > feel about that? > > > > What's the problem with userspace locking? > > The idea was to get by without it. > > Regarding ioctls, it does not seem realizable due to ioctl number > exhaustion.
I am prettu sure we cabn spare 1 ioctl number. We just need to pass slot number not as part of ioctl number but in data instead. Like EVIOCGKEYCODE works.
-- Dmitry
| |