Re: [PATCH v2] input: fix BTN_TOUCH reporting in input_mt_report_pointer_emulation

2014-10-28 Thread Peter Hutterer
On Tue, Oct 28, 2014 at 02:07:06PM -0700, Dmitry Torokhov wrote: > On Tue, Oct 28, 2014 at 04:47:56PM -0400, Benjamin Tissoires wrote: > > Hi Chung-yih, > > > > On Mon, Oct 27, 2014 at 6:08 AM, Chung-yih Wang wrote: > > > From the definition of BTN_TOUCH, BTN_TOOL_ and BTN_TOUCH codes > > > are

Re: [PATCH v2] input: fix BTN_TOUCH reporting in input_mt_report_pointer_emulation

2014-10-28 Thread Dmitry Torokhov
On Tue, Oct 28, 2014 at 04:47:56PM -0400, Benjamin Tissoires wrote: > Hi Chung-yih, > > On Mon, Oct 27, 2014 at 6:08 AM, Chung-yih Wang wrote: > > From the definition of BTN_TOUCH, BTN_TOOL_ and BTN_TOUCH codes > > are orthogonal. BTN_TOUCH should be zero if there is no physical contact > > hap

Re: [PATCH v2] input: fix BTN_TOUCH reporting in input_mt_report_pointer_emulation

2014-10-28 Thread Benjamin Tissoires
Hi Chung-yih, On Mon, Oct 27, 2014 at 6:08 AM, Chung-yih Wang wrote: > From the definition of BTN_TOUCH, BTN_TOOL_ and BTN_TOUCH codes > are orthogonal. BTN_TOUCH should be zero if there is no physical contact > happened on device. With ABS_MT_DISTANCE information, the patch uses > touch_count

[PATCH v2] input: fix BTN_TOUCH reporting in input_mt_report_pointer_emulation

2014-10-27 Thread Chung-yih Wang
From the definition of BTN_TOUCH, BTN_TOOL_ and BTN_TOUCH codes are orthogonal. BTN_TOUCH should be zero if there is no physical contact happened on device. With ABS_MT_DISTANCE information, the patch uses touch_count and finger_count to get the final reporting code for BTN_TOUCH and BTN_TOOL_, r