tree 88a4435c24280c9d8d01c4cd4129f2e7b761e3d1
parent 0bd88c5bb77fc515ab2017c4fbf75594d05c927b
author Anurag Singh <anursing@codeaurora.org> 1363738461 -0700
committer Dmitry Shmidt <dimitrysh@google.com> 1488582514 -0800

input: evdev: Move wake_lock_destroy call

Calling wake_lock_destroy from inside a spinlock
protected region (or, in general, from atomic context)
leads to a 'scheduling while atomic bug' because the
internal wakeup source deletion logic calls
synchronize_rcu, which can sleep. Moreover,
since the interal lists are already protected with
RCUs and spinlocks, putting the wake_lock_destroy
call in a spinlock is redundant.

Change-Id: I10a2239b664a5f43e54495f24fe588fb09282305
Signed-off-by: Anurag Singh <anursing@codeaurora.org>