Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755769Ab0DHDN2 (ORCPT ); Wed, 7 Apr 2010 23:13:28 -0400 Received: from na3sys009aog106.obsmtp.com ([74.125.149.77]:42014 "HELO na3sys009aog106.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1754006Ab0DHDN0 (ORCPT ); Wed, 7 Apr 2010 23:13:26 -0400 X-Greylist: delayed 371 seconds by postgrey-1.27 at vger.kernel.org; Wed, 07 Apr 2010 23:13:26 EDT From: Michael Poole To: "Henrik Rydberg" Cc: Dmitry Torokhov , Andrew Morton , linux-input@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] input: mt: introduce MT event slots References: <1270685590-2204-1-git-send-email-rydberg@euromail.se> Date: Wed, 07 Apr 2010 23:07:09 -0400 In-Reply-To: <1270685590-2204-1-git-send-email-rydberg@euromail.se> (Henrik Rydberg's message of "Thu, 8 Apr 2010 02:13:10 +0200") Message-ID: <87tyrmiqw2.fsf@troilus.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1706 Lines: 33 Henrik Rydberg writes: > With the rapidly increasing number of intelligent multi-contact and > multi-user devices, the need to send digested, filtered information > from a set of different sources within the same device is imminent. > This patch adds the concept of slots to the MT protocol. The slots > enumerate a set of identified sources, such that all MT events > can be passed independently and selectively per identified source. > > The protocol works like this: Instead of sending a SYN_MT_REPORT > event immediately after the contact data, one sends a SYN_MT_SLOT > event immediately before the contact data. The input core will only > emit events for the slots corresponding to the contacts that have > changed. It is assumed that the same slot is used for the duration > of an initiated contact. How would the slot number for a contact be chosen? If the kernel makes that assignment, what should a "slot" correspond to from a computer user's perspective? "Set[s] of identified sources" is a little vague: Does it mean contacts from one hand, contacts in one displayed window (assuming the touch surface is a screen), or something else? (I assume it would not duplicate the blob or tracking IDs already defined for MT events.) It seems like those would be important aspects of the protocol to document in Documentation/input/multi-touch-protocol.txt -- otherwise, driver implementers or application developers might get it wrong. Michael Poole -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/