From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dyer Subject: Re: [PATCH] Input: atmel_mxt_ts - implement T100 touch object support Date: Fri, 19 Dec 2014 15:04:57 +0000 Message-ID: <54943E99.5060206@itdev.co.uk> References: <1418156167-11724-1-git-send-email-nick.dyer@itdev.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: Received: from kdh-gw.itdev.co.uk ([89.21.227.133]:12345 "EHLO hermes.kdh.itdev.co.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750968AbaLSPFE (ORCPT ); Fri, 19 Dec 2014 10:05:04 -0500 In-Reply-To: Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Benson Leung , Dmitry Torokhov Cc: Yufeng Shen , Daniel Kurtz , Henrik Rydberg , Joonyoung Shim , Alan Bowens , "linux-input@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Peter Meerwald , Olof Johansson , Sekhar Nori , Stephen Warren , Chung-yih Wang 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. cheers Nick