linux.git/drivers/input, branch v3.19-rc4

Revert "Input: atmel_mxt_ts - use deep sleep mode when stopped"

2014-12-31T20:59:34+00:00

This reverts commit 9d469d033d135d80742a4e39e6bbb4519dd5eee1.

It breaks the Chromebook Pixel touchpad (and touchscreen).

Reported-by: Dirk Hohndel 
Bisected-by: Linus Torvalds 
Cc: Nick Dyer 
Cc: Benson Leung 
Cc: Yufeng Shen 
Cc: Dmitry Torokhov 
Cc: stable@vger.kernel.org  # v3.16+
Signed-off-by: Linus Torvalds

Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input

2014-12-31T00:59:59+00:00

Pull input layer fixes from Dmitry Torokhov:
 "Fixes for v7 protocol for ALPS devices and few other driver fixes.

  Also users can request input events to be stamped with boot time
  timestamps, in addition to real and monotonic timestamps"

* 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input:
  Input: hil_kbd - fix incorrect use of init_completion
  Input: alps - v7: document the v7 touchpad packet protocol
  Input: alps - v7: fix finger counting for > 2 fingers on clickpads
  Input: alps - v7: sometimes a single touch is reported in mt[1]
  Input: alps - v7: ignore new packets
  Input: evdev - add CLOCK_BOOTTIME support
  Input: psmouse - expose drift duration for IBM trackpoints
  Input: stmpe - bias keypad columns properly
  Input: stmpe - enforce device tree only mode
  mfd: stmpe: add pull up/down register offsets for STMPE
  Input: optimize events_per_packet count calculation
  Input: edt-ft5x06 - fixed a macro coding style issue
  Input: gpio_keys - replace timer and workqueue with delayed workqueue
  Input: gpio_keys - allow separating gpio and irq in device tree

Input: hil_kbd - fix incorrect use of init_completion

2014-12-28T04:43:35+00:00

The successive init_completion calls should be reinit_completion calls.

Signed-off-by: Nicholas Mc Guire 
Acked-by: Helge Deller 
Tested-by: Helge Deller 
Signed-off-by: Dmitry Torokhov

Merge branch 'next' into for-linus

2014-12-18T18:02:39+00:00

Second round of input updates for 3.19.

Input: alps - v7: document the v7 touchpad packet protocol

2014-12-18T18:01:28+00:00

Add a table documenting where all the bits are in the v7 touchpad packets.

Signed-off-by: Hans de Goede 
Signed-off-by: Dmitry Torokhov

Input: alps - v7: fix finger counting for > 2 fingers on clickpads

2014-12-18T18:01:23+00:00

Protocol v7 uses the middle / right button bits on clickpads to communicate
"location" information of a 3th touch (and possible 4th) touch on
clickpads.

Specifically when 3 touches are down, if one of the 3 touches is in the
left / right button area, this will get reported in the middle / right
button bits and the touchpad will still send a TWO type packet rather then
a MULTI type packet, so when this happens we must add the finger reported
in the button area to the finger count.

Likewise we must also add fingers reported this way to the finger count
when we get MULTI packets.

BugLink: https://bugs.freedesktop.org/show_bug.cgi?id=86338
Cc: stable@vger.kernel.org # 3.17
Signed-off-by: Hans de Goede 
Tested-by: Benjamin Tissoires 
Signed-off-by: Dmitry Torokhov

Input: alps - v7: sometimes a single touch is reported in mt[1]

2014-12-18T18:01:17+00:00

The v7 proto differentiates between a primary touch (with high precision)
and a secondary touch (with lower precision). Normally when 2 fingers are
down and one is lifted the still present touch becomes the primary touch,
but some traces have shown that this does not happen always.

This commit deals with this by making alps_get_mt_count() not stop at the
first empty mt slot, and if a touch is present in mt[1] and not mt[0]
moving the data to mt[0] (for input_mt_assign_slots).

BugLink: https://bugs.freedesktop.org/show_bug.cgi?id=86338
Cc: stable@vger.kernel.org # 3.17
Signed-off-by: Hans de Goede 
Tested-by: Benjamin Tissoires 
Signed-off-by: Dmitry Torokhov

Input: alps - v7: ignore new packets

2014-12-18T18:00:58+00:00

NEW packets are send to indicate a discontinuity in the finger coordinate
reporting. Specifically a finger may have moved from slot 0 to 1 or vice
versa.  INPUT_MT_TRACK takes care of this for us.

NEW packets have 3 problems:
1) They do not contain middle / right button info (on non clickpads)
   this can be worked around by preserving the old button state
2) They do not contain an accurate fingercount, and they are
   typically send when the number of fingers changes. We cannot use
   the old finger count as that may mismatch with the amount of
   touch coordinates we've available in the NEW packet
3) Their x data for the second touch is inaccurate leading to
   a possible jump of the x coordinate by 16 units when the first
   non NEW packet comes in

Since problems 2 & 3 cannot be worked around, just ignore them.

BugLink: https://bugs.freedesktop.org/show_bug.cgi?id=86338
Cc: stable@vger.kernel.org # 3.17
Signed-off-by: Hans de Goede 
Tested-by: Benjamin Tissoires 
Signed-off-by: Dmitry Torokhov

Input: evdev - add CLOCK_BOOTTIME support

2014-12-17T23:46:59+00:00

This patch adds support for CLOCK_BOOTTIME for input event timestamp.
CLOCK_BOOTTIME includes suspend time, so it would allow aplications
to get correct time difference between two events even when system
resumes from suspend state.

Signed-off-by: Aniroop Mathur 
Signed-off-by: Dmitry Torokhov

Input: psmouse - expose drift duration for IBM trackpoints

2014-12-17T23:46:51+00:00

IBM Trackpoints have a feature to compensate for drift by recalibrating
themselves periodically. By default, if for 0.5 seconds there is no change
in position, it's used as the new zero. This duration is too low. Often,
the calibration happens when the trackpoint is in fact being used.

IBM's Trackpoint Engineering Specifications show a configuration register
that allows changing this duration, rstdft1.

Expose it via sysfs among the other settings.

Signed-off-by: Mike Murdoch 
Signed-off-by: Dmitry Torokhov