Input: fix locking in memoryless force-feedback devices
authorDmitry Torokhov <dmitry.torokhov@gmail.com>
Sat, 7 Nov 2009 05:39:07 +0000 (21:39 -0800)
committerDmitry Torokhov <dmitry.torokhov@gmail.com>
Wed, 11 Nov 2009 05:13:32 +0000 (21:13 -0800)
commitbf3204cbff7d2606e758afb0994e8da6ae1c6c26
tree01951b829d2af6a52b82bec35cc05261dcf77fe2
parent558a5e296a02266ef43d6e933ee35df9976de987
Input: fix locking in memoryless force-feedback devices

Now that input core acquires dev->event_lock spinlock and disables
interrupts when propagating input events, using spin_lock_bh() in
ff-memless driver is not allowed. Actually, the timer_lock itself
is not needed anymore, we should simply use dev->event_lock
as well.

Also do a small cleanup in force-feedback core.

Reported-by: kerneloops.org
Reported-by: http://www.kerneloops.org/searchweek.php?search=ml_ff_set_gain
Reported-by: Arjan van de Ven <arjan@linux.intel.com>
Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
drivers/input/ff-core.c
drivers/input/ff-memless.c
include/linux/input.h