Patch "Input: zforce_ts - fix dual touch recognition" has been added to the 3.14-stable tree

This is a note to let you know that I've just added the patch titled

Input: zforce_ts - fix dual touch recognition

to the 3.14-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
input-zforce_ts-fix-dual-touch-recognition.patch
and it can be found in the queue-3.14 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.

From: Knut Wohlrab <[email protected]>
Date: Mon, 25 Apr 2016 14:08:25 -0700
Subject: Input: zforce_ts - fix dual touch recognition

From: Knut Wohlrab <[email protected]>

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.

---
 drivers/input/touchscreen/zforce_ts.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

@@ -350,8 +350,8 @@ static int zforce_touch_event(struct zfo
 			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],

Patches currently in stable-queue which might be from [email protected] are

queue-3.14/input-zforce_ts-fix-dual-touch-recognition.patch