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)
committerDmitry Torokhov <dmitry.torokhov@gmail.com>
Mon, 25 Apr 2016 21:27:56 +0000 (14:27 -0700)
commit6984ab1ab35f422292b7781c65284038bcc0f6a6
treee1900b55975a16028f35ebad15664bf46bc1dc26
parent28a994fad95dd8475f04bd036e08a14aa8d125ea
Input: zforce_ts - fix dual touch recognition

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>
drivers/input/touchscreen/zforce_ts.c