Messages in this thread Patch in this message | | | From | Dmitry Torokhov <> | Subject | Re: [PATCH 001/001] INPUT: new ioctl's to retrieve values of EV_REP and EV_SND event codes | Date | Wed, 26 Apr 2006 01:06:38 -0400 |
| |
On Tuesday 25 April 2006 11:26, Vojtech Pavlik wrote: > On Tue, Apr 25, 2006 at 11:23:02AM -0400, Dmitry Torokhov wrote: > > On 4/25/06, Vojtech Pavlik <vojtech@suse.cz> wrote: > > > On Tue, Apr 25, 2006 at 09:19:42AM -0400, Dmitry Torokhov wrote: > > > > On 4/24/06, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote: > > > > > On 4/24/06, Vojtech Pavlik <vojtech@suse.cz> wrote: > > > > > > On Mon, Apr 24, 2006 at 10:31:39AM -0400, Dmitry Torokhov wrote: > > > > > > > > > > > > > > Vojtech, could you remind me why EVIOC{G|S}REP were removed? Some > > > > > > > people want to have ability to separate keyboards (via grabbing); they > > > > > > > also might want to control repeat rate independently. Shoudl we > > > > > > > reinstate these ioctls? > > > > > > > > > > > > I believe they were replaced by the ability to send EV_REP style events > > > > > > to the device, setting the repeat rate. > > > > > > > > > > > > > > > > Argh, why am I always forgetting about ability to write events into devices? > > > > > > > > Thinking about it some more - writing to the event device is an > > > > elegant way to set repeat rate but how do you retrieve current repeat > > > > rate for a given device? > > > > > > You can't. And that's likely a problem that needs fixing. > > > > > > > So do you agree that we need to ressurect EVIOCGREP (and EVIOCSREP > > just to complement the interface)? > > Yes. And EVIOCSREP should just generate the events needed to notify the > drivers to do the change. >
What do you gius think about the patch below?
-- Dmitry
Signed-off-by: Dmitry Torokhov <dtor@mail.ru> ---
drivers/input/evdev.c | 21 +++++++++++++++++++++ include/linux/input.h | 2 ++ 2 files changed, 23 insertions(+)
Index: work/drivers/input/evdev.c =================================================================== --- work.orig/drivers/input/evdev.c +++ work/drivers/input/evdev.c @@ -403,6 +403,27 @@ static long evdev_ioctl_handler(struct f case EVIOCGID: if (copy_to_user(p, &dev->id, sizeof(struct input_id))) return -EFAULT; + return 0; + + case EVIOCGREP: + if (!test_bit(EV_REP, dev->evbit)) + return -ENOSYS; + if (put_user(dev->rep[REP_DELAY], ip)) + return -EFAULT; + if (put_user(dev->rep[REP_PERIOD], ip + 1)) + return -EFAULT; + return 0; + + case EVIOCSREP: + if (!test_bit(EV_REP, dev->evbit)) + return -ENOSYS; + if (get_user(u, ip)) + return -EFAULT; + if (get_user(v, ip + 1)) + return -EFAULT; + + input_event(dev, EV_REP, REP_DELAY, u); + input_event(dev, EV_REP, REP_PERIOD, v); return 0; Index: work/include/linux/input.h =================================================================== --- work.orig/include/linux/input.h +++ work/include/linux/input.h @@ -56,6 +56,8 @@ struct input_absinfo { #define EVIOCGVERSION _IOR('E', 0x01, int) /* get driver version */ #define EVIOCGID _IOR('E', 0x02, struct input_id) /* get device ID */ +#define EVIOCGREP _IOR('E', 0x03, int[2]) /* get repeat settings */ +#define EVIOCSREP _IOW('E', 0x03, int[2]) /* get repeat settings */ #define EVIOCGKEYCODE _IOR('E', 0x04, int[2]) /* get keycode */ #define EVIOCSKEYCODE _IOW('E', 0x04, int[2]) /* set keycode */ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |