linux.git/drivers/input/joydev.c, branch v2.6.31

Input: joydev - decouple axis and button map ioctls from input constants

2009-08-12T08:16:13+00:00

The KEY_MAX change in 2.6.28 changed the values of the JSIOCSBTNMAP and
JSIOCGBTNMAP constants; software compiled with the old values no longer
works with kernels following 2.6.28, because the ioctl switch statement
no longer matches the values given by the software. This patch handles
these ioctls independently of the length of data specified, and applies the
same treatment to JSIOCSAXMAP and JSIOCGAXMAP which currently depend on
ABS_MAX.

Signed-off-by: Stephen Kitt 
Signed-off-by: Dmitry Torokhov

Input: fix EVIOCGNAME/JSIOCGNAME regression

2009-07-14T05:24:29+00:00

Commit 3d5cb60e ("Input: simplify name handling for certain input
handles") introduced a regression for the EVIOCGNAME/JSIOCGNAME
ioctl.

Before this, patch, the platform device's name was given back to
userspace which was good to identify devices. After this patch, the
device is ("event%d", minor) which is not descriptive at all.

This fixes the behaviour by taking dev->name.

Reported-by: Sven Neumann 
Signed-off-by: Daniel Mack 
Reviewed-by: Thadeu Lima de Souza Cascardo 
Signed-off-by: Dmitry Torokhov

Merge commit 'v2.6.30' into next

2009-06-11T08:58:01+00:00

Input: simplify name handling for certain input handles

2009-05-11T07:11:43+00:00

For evdev, joydev and mousedev, instead of having a separate character array
holding name of the handle, use struct devce's name which is the same.

Signed-off-by: Thadeu Lima de Souza Cascardo 
Signed-off-by: Dmitry Torokhov

Input: joydev - blacklist digitizers

2009-05-08T02:04:03+00:00

BTN_TOUCH is not set by the wacom driver which causes it to be handled by the
joydev driver while the resulting device is broken. This causes problems with
applications that try to use a joystick device.

Ubuntu BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/300143

Signed-off-by: Tim Cole 
Signed-off-by: Stefan Bader 
Acked-by: Tim Gardner 
Acked-by: Amit Kucheria 
Signed-off-by: Dmitry Torokhov

Rationalize fasync return values

2009-03-16T14:34:35+00:00

Most fasync implementations do something like:

     return fasync_helper(...);

But fasync_helper() will return a positive value at times - a feature used
in at least one place.  Thus, a number of other drivers do:

     err = fasync_helper(...);
     if (err < 0)
             return err;
     return 0;

In the interests of consistency and more concise code, it makes sense to
map positive return values onto zero where ->fasync() is called.

Cc: Al Viro 
Signed-off-by: Jonathan Corbet

Merge commit 'v2.6.28-rc9' into next

2008-12-20T09:54:54+00:00

saner FASYNC handling on file close

2008-11-01T16:49:46+00:00

As it is, all instances of ->release() for files that have ->fasync()
need to remember to evict file from fasync lists; forgetting that
creates a hole and we actually have a bunch that *does* forget.

So let's keep our lives simple - let __fput() check FASYNC in
file->f_flags and call ->fasync() there if it's been set.  And lose that
crap in ->release() instances - leaving it there is still valid, but we
don't have to bother anymore.

Signed-off-by: Al Viro 
Signed-off-by: Linus Torvalds

Input: struct device - replace bus_id with dev_name(), dev_set_name()

2008-10-30T13:29:05+00:00

Acked-by: Greg Kroah-Hartman 
Signed-off-by: Kay Sievers 
Signed-off-by: Dmitry Torokhov

Input: make sure input interfaces pin parent input devices

2008-04-01T04:22:53+00:00

Recent driver core change causes references to parent devices being
dropped early, at device_del() time, as opposed to when all children
are freed. This causes oops in evdev with grabbed devices. Take the
reference to the parent input device ourselves to ensure that it
stays around long enough.

Signed-off-by: Dmitry Torokhov