From patchwork Mon Jun 28 12:23:38 2010 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Henrik Rydberg X-Patchwork-Id: 108372 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by demeter.kernel.org (8.14.4/8.14.3) with ESMTP id o5SCO8C9014934 for ; Mon, 28 Jun 2010 12:24:08 GMT Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751665Ab0F1MYH (ORCPT ); Mon, 28 Jun 2010 08:24:07 -0400 Received: from ch-smtp03.sth.basefarm.net ([80.76.149.214]:51827 "EHLO ch-smtp03.sth.basefarm.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751284Ab0F1MYH (ORCPT ); Mon, 28 Jun 2010 08:24:07 -0400 Received: from c83-248-196-134.bredband.comhem.se ([83.248.196.134]:53905 helo=[192.168.0.183]) by ch-smtp03.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1OTDNE-000579-Ad; Mon, 28 Jun 2010 14:23:42 +0200 Message-ID: <4C28944A.4050501@euromail.se> Date: Mon, 28 Jun 2010 14:23:38 +0200 From: Henrik Rydberg User-Agent: Thunderbird 2.0.0.24 (X11/20100411) MIME-Version: 1.0 To: Joonyoung Shim CC: dmitry.torokhov@gmail.com, linux-input@vger.kernel.org, kyungmin.park@samsung.com Subject: Re: [PATCH v2] input: qt602240 - Add ATMEL QT602240 touchscreen driver References: <1277430882-3685-1-git-send-email-jy0922.shim@samsung.com> <4C24B86E.1030407@euromail.se> <4C283048.1090601@samsung.com> <4C285124.1050201@euromail.se> <4C285AB1.7030301@samsung.com> <4C285E85.6080008@euromail.se> <4C2865D0.7020605@samsung.com> <4C28689A.60701@euromail.se> <4C2872B2.1030405@samsung.com> <4C2877F3.8020003@euromail.se> <4C2883A9.5060305@samsung.com> In-Reply-To: <4C2883A9.5060305@samsung.com> X-Originating-IP: 83.248.196.134 X-Scan-Result: No virus found in message 1OTDNE-000579-Ad. X-Scan-Signature: ch-smtp03.sth.basefarm.net 1OTDNE-000579-Ad 01928cc78f9ed835cb77b3b2d8222c7c Sender: linux-input-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-input@vger.kernel.org X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.2.3 (demeter.kernel.org [140.211.167.41]); Mon, 28 Jun 2010 12:24:08 +0000 (UTC) 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.