[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1422258820-4236-1-git-send-email-javier.martinez@collabora.co.uk>
Date: Mon, 26 Jan 2015 08:53:39 +0100
From: Javier Martinez Canillas <javier.martinez@...labora.co.uk>
To: Nick Dyer <nick.dyer@...ev.co.uk>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Yufeng Shen <miletus@...gle.com>,
Daniel Kurtz <djkurtz@...omium.org>,
Henrik Rydberg <rydberg@...omail.se>,
Joonyoung Shim <jy0922.shim@...sung.com>,
Alan Bowens <Alan.Bowens@...el.com>,
linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
Peter Meerwald <pmeerw@...erw.net>,
Benson Leung <bleung@...omium.org>,
Olof Johansson <olofj@...omium.org>,
Sekhar Nori <nsekhar@...com>,
Stephen Warren <swarren@...dotorg.org>,
Javier Martinez Canillas <javier.martinez@...labora.co.uk>
Subject: Re: [PATCH] Input: atmel_mxt_ts - implement T100 touch object support
Hello Nick,
On 12/19/2014 15:04 PM, Nick Dyer wrote:>
> Hi Benson-
> On 18/12/14 18:49, Benson Leung wrote:
>> Dmitry and Chung-Yih have had some discussion about how to handle
>> hovering fingers, and I think the direction they wanted to go was to
>> use ABS_MT_DISTANCE instead.
>>
>> http://www.spinics.net/lists/linux-input/msg33950.html
>
> Thanks for flagging this up. The patch I submitted is written against the
> Android touch devices spec, which treats ABS_MT_PRESSURE being zero as
> hover, but indeed currently the handling of BTN_TOUCH when using
> input_mt_report_pointer_emaultion() won't be quite right.
>
> I will have a look at straightening this out and re-post.
Are you planning to send your patch using ABS_MT_DISTANCE for 3.20?
If not, I can take a look since T100 support is needed for the Samsung
Peach Pi Chromebook.
Best regards,
Javier
--
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