summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKnut Wohlrab <Knut.Wohlrab@de.bosch.com>2016-04-25 14:08:25 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2016-05-11 11:21:34 +0200
commit182029d97919c3712676c46c18b4190d28fc802a (patch)
tree8cc373021b4854b307cc4da8e26edf551fd54145
parenteadd64d6214ae166105fda54509a9240f39cdb2a (diff)
downloadlwn-182029d97919c3712676c46c18b4190d28fc802a.tar.gz
lwn-182029d97919c3712676c46c18b4190d28fc802a.zip
Input: zforce_ts - fix dual touch recognition
commit 6984ab1ab35f422292b7781c65284038bcc0f6a6 upstream. 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: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-rw-r--r--drivers/input/touchscreen/zforce_ts.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/input/touchscreen/zforce_ts.c b/drivers/input/touchscreen/zforce_ts.c
index 9bbadaaf6bc3..7b3845aa5983 100644
--- a/drivers/input/touchscreen/zforce_ts.c
+++ b/drivers/input/touchscreen/zforce_ts.c
@@ -370,8 +370,8 @@ static int zforce_touch_event(struct zforce_ts *ts, u8 *payload)
point.coord_x = point.coord_y = 0;
}
- point.state = payload[9 * i + 5] & 0x03;
- point.id = (payload[9 * i + 5] & 0xfc) >> 2;
+ point.state = payload[9 * i + 5] & 0x0f;
+ point.id = (payload[9 * i + 5] & 0xf0) >> 4;
/* determine touch major, minor and orientation */
point.area_major = max(payload[9 * i + 6],