Input: zforce_ts - fix dual touch recognition
authorKnut Wohlrab <Knut.Wohlrab@de.bosch.com>
Mon, 25 Apr 2016 21:08:25 +0000 (14:08 -0700)
committerSasha Levin <sasha.levin@oracle.com>
Tue, 12 Jul 2016 12:48:03 +0000 (08:48 -0400)
commit5bb34c8e8e31b08a3027f5ef072ee950073dd20e
tree9b796bf0c4ca003ae16832f1bd5af3564c16585c
parent7934ff912c6ec1f29bc2ce30f7bda06f3fd6f6f9
Input: zforce_ts - fix dual touch recognition

[ Upstream commit 6984ab1ab35f422292b7781c65284038bcc0f6a6 ]

A wrong decoding of the touch coordinate message causes a wrong touch
ID. Touch ID for dual touch must be 0 or 1.

According to the actual Neonode nine byte touch coordinate coding,
the state is transported in the lower nibble and the touch ID in
the higher nibble of payload byte five.

Signed-off-by: Knut Wohlrab <Knut.Wohlrab@de.bosch.com>
Signed-off-by: Oleksij Rempel <linux@rempel-privat.de>
Signed-off-by: Dirk Behme <dirk.behme@de.bosch.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
drivers/input/touchscreen/zforce_ts.c