[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F689E9F.90902@itdev.co.uk>
Date: Tue, 20 Mar 2012 08:13:35 -0700
From: Nick Dyer <nick.dyer@...ev.co.uk>
To: Daniel Kurtz <djkurtz@...omium.org>
CC: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Joonyoung Shim <jy0922.shim@...sung.com>,
Iiro Valkonen <iiro.valkonen@...el.com>,
Henrik Rydberg <rydberg@...omail.se>,
linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
Benson Leung <bleung@...omium.org>,
Yufeng Shen <miletus@...omium.org>,
"Bowens, Alan" <Alan.Bowens@...el.com>,
"Tiwari, Atul" <Atul.Tiwari@...el.com>
Subject: Re: [PATCH 12/20] Input: atmel_mxt_ts - simplify event reporting
Daniel Kurtz wrote:
> Instead of carrying around per-finger state in the driver instance, just
> report each finger as it arrives to the input layer, and let the input
> layer (evdev) hold the event state (which it does anyway).
>
> Also, the atmel pad reports "amplitude", which is reported to userspace
> using the "PRESSURE" event type. The variables now reflect this.
>
> Note: this driver does not really do MT-B properly. Each input report
> (a goup of input events followed by a SYN_REPORT) only contains data for
> a single contact. When multiple fingers are present on a device, each is
> properly reported in its own MT_SLOT. However, there is only ever one
> MT_SLOT per SYN_REPORT. This is fixed in a subsequent patch.
>
> Signed-off-by: Daniel Kurtz <djkurtz@...omium.org>
This seems to be a good improvement, assuming it is valid. Which platforms
have you tested it on?
--
Nick Dyer
Software Engineer, ITDev Ltd
Hardware and Software Development Consultancy
Website: http://www.itdev.co.uk
--
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