linux-toradex.git/drivers/input/input.c, branch v3.14.57

Input: fix defuzzing logic

2014-07-31T19:52:56+00:00

commit 50c5d36dab930b1f1b1e3348b8608aa8b9ee7610 upstream.

We attempt to remove noise from coordinates reported by devices in
input_handle_abs_event(), unfortunately, unless we were dropping the
event altogether, we were ignoring the adjusted value and were passing
on the original value instead.

Reviewed-by: Andrew de los Reyes 
Reviewed-by: Benson Leung 
Reviewed-by: David Herrmann 
Reviewed-by: Henrik Rydberg 
Signed-off-by: Dmitry Torokhov 
Signed-off-by: Greg Kroah-Hartman

Merge branch 'next' into for-linus

2014-01-23T16:10:44+00:00

First round of input updates for 3.14.

Input: allocate absinfo data when setting ABS capability

2013-12-31T18:53:19+00:00

We need to make sure we allocate absinfo data when we are setting one of
EV_ABS/ABS_XXX capabilities, otherwise we may bomb when we try to emit this
event.

Rested-by: Paul Cercueil 
Signed-off-by: Dmitry Torokhov

Input: don't call input_dev_release_keys() in resume

2013-12-16T10:19:10+00:00

When waking up the platform by pressing a specific key, sending a
release on that key makes it impossible to react on the event in
user-space. This is fixed by moving the input_reset_device() call to
resume instead.

[dmitry.torokhov@gmail.com: make sure we still restore LED/sound state
after resume, handle hibernation properly]

Signed-off-by: Aleksej Makarov 
Signed-off-by: Oskar Andero 
Signed-off-by: Dmitry Torokhov

Merge branch 'next' into for-linus

2013-11-15T01:38:05+00:00

Merge first round of changes for 3.13 merge window.

Input: remove a redundant max() call

2013-10-31T15:46:07+00:00

dev->hint_events_per_packet is guaranteed to be >= packet_size.
so an extra max() call is not needed.

Signed-off-by: Kang Hu 
Signed-off-by: Dmitry Torokhov

Input: move name/timer init to input_alloc_dev()

2013-10-06T08:23:26+00:00

We want to allow drivers to call input_event() at any time after the
device got allocated. This means input_event() and input_register_device()
must be allowed to run in parallel.

The only conflicting calls in input_register_device() are init_timer() and
dev_set_name(). Both can safely be moved to device allocation and we're
good to go.

Signed-off-by: David Herrmann 
Signed-off-by: Dmitry Torokhov

Input: document that unregistering managed devices is not necessary

2013-01-09T17:07:56+00:00

Apparently some users of managed input devices are confused whether
input_unregister_device() is needed when working with them. Clarify
this in the kernel doc for devm_input_allocate_device(): in most cases
there is no need to call neither input_unregister_device() nor
input_free_device() when working with managed devices.

Signed-off-by: Dmitry Torokhov

Input: introduce managed input devices (add devres support)

2012-11-08T17:10:05+00:00

There is a demand from driver's writers to use managed devices framework
for their drivers. Unfortunately up to this moment input devices did not
provide support for managed devices and that lead to mixing two styles
of resource management which usually introduced more bugs, such as
manually unregistering input device but relying in devres to free
interrupt handler which (unless device is properly shut off) can cause
ISR to reference already freed memory.

This change introduces devm_input_allocate_device() that will allocate
managed instance of input device so that driver writers who prefer
using devm_* framework do not have to mix 2 styles.

Reviewed-by: Henrik Rydberg 
Reviewed-by: Tejun Heo 
Signed-off-by: Dmitry Torokhov

Input: fix sparse warning in __input_release_device()

2012-10-25T07:12:01+00:00

This fixes the following warning:
drivers/input/input.c:538:23: error: incompatible types in comparison expression (different address spaces)

Signed-off-by: Dmitry Torokhov