[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100525173446.GA4634@core.coreip.homeip.net>
Date: Tue, 25 May 2010 10:34:46 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Henrik Rydberg <rydberg@...omail.se>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
Mika Kuoppala <mika.kuoppala@...ia.com>,
Peter Hutterer <peter.hutterer@...-t.net>,
Benjamin Tissoires <tissoire@...a.fr>,
Stephane Chatty <chatty@...c.fr>,
Rafi Rubin <rafi@...s.upenn.edu>,
Michael Poole <mdpoole@...ilus.org>
Subject: Re: [PATCH 0/2] input: mt: Add EVIOC mechanism for MT slots
Hi Henrik,
On Tue, May 25, 2010 at 01:52:57PM +0200, Henrik Rydberg wrote:
> These patches are in response to the discussion about input state
> retrieval.
>
> The current EVIOCGABS method does not work with MT slots. These
> patches provides a mechanism where a slot is first selected via a call
> to EVIOCSABS, after which the corresponding MT events can be extracted
> with calls to EVIOCGABS.
>
> The symmetric operation, to set the MT state via EVIOCSABS, seems to
> violate input data integrity, and is therefore not implemented.
>
This looks sane, however the question remains - is there any users for
this data? Like I mentioned, I can see the need to fetch state of
switches and ranges of absolute axis, and even non-multitouch ABS values
(due to the fact that some input devices, like sliders, may stay in a
certain position for long periods of time), but I expect multitouch data
to be "refreshed" very quickly.
Thanks.
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists