diff mbox

[v2] input: qt602240 - Add ATMEL QT602240 touchscreen driver

Message ID 4C28944A.4050501@euromail.se (mailing list archive)
State New, archived
Headers show

Commit Message

Henrik Rydberg June 28, 2010, 12:23 p.m. UTC
None
diff mbox

Patch

diff --git a/Documentation/input/multi-touch-protocol.txt b/Documentation/input/
index 3ab038d..bdcba15 100644
--- a/Documentation/input/multi-touch-protocol.txt
+++ b/Documentation/input/multi-touch-protocol.txt
@@ -43,15 +43,16 @@  input_sync() function. This instructs the receiver to act up
 accumulated since last EV_SYN/SYN_REPORT and prepare to receive a new set
 of events/packets.

-The main difference between the raw type A protocol and the higher level
-type B slot protocol lies in the usage of identifiable contacts. The slot
-protocol requires the use of the ABS_MT_TRACKING_ID, either provided by the
-hardware or computed from the raw data [5].
+The main difference between the stateless type A protocol and the stateful
+type B slot protocol lies in the usage of identifiable contacts to reduce
+the amount of data sent to userspace. The slot protocol requires the use of
+the ABS_MT_TRACKING_ID, either provided by the hardware or computed from
+the raw data [5].

 For type A devices, the kernel driver should generate an arbitrary
-enumeration of the set of anonymous contacts currently on the surface. The
-order in which the packets appear in the event stream is not important.
-Event filtering and finger tracking is left to user space [3].
+enumeration of the full set of anonymous contacts currently on the
+surface. The order in which the packets appear in the event stream is not
+important.  Event filtering and finger tracking is left to user space [3].

 For type B devices, the kernel driver should associate a slot with each
 identified contact, and use that slot to propagate changes for the contact.