linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arek Burdach <arek.burdach@gmail.com>
To: Benjamin Tissoires <benjamin.tissoires@gmail.com>
Cc: "Martin Kepplinger" <martin.kepplinger@ginzinger.com>,
	"Andrew Duggan" <aduggan@synaptics.com>,
	"Stéphane Chatty" <chatty@enac.fr>,
	linux-input <linux-input@vger.kernel.org>
Subject: Re: Missing release event for Synaptics touchscreen
Date: Tue, 16 May 2017 11:46:45 +0200	[thread overview]
Message-ID: <699f72dc-25fe-3ffb-a20a-7800a09f0c86@gmail.com> (raw)
In-Reply-To: <CAN+gG=HyxZGu5fJ-u+WXNOKG3oXuYL5DgU1aPnmavMOhwzoZbg@mail.gmail.com>



On 16.05.2017 10:18, Benjamin Tissoires wrote:
> On Mon, May 15, 2017 at 8:45 PM, Arek Burdach <arek.burdach@gmail.com> wrote:
>> Hi Benjamin,
>>
>> I found out what was wrong in the change that you've provided:
>>
>> On 12.05.2017 16:28, Benjamin Tissoires wrote:
>>
>> +       if (td->mtclass.quirks & MT_QUIRK_STICKY_FINGERS)
>> +               mod_timer(&td->release_timer, msecs_to_jiffies(250));
>>   }
>>
>> Should be:
>>
>> mod_timer(&td->release_timer, jiffies + msecs_to_jiffies(100));
> Right, thanks!
>
>> Delay should be added to current jiffies value. Also I found out that 250 ms
>> is too long delay - xserver recognize such a delay as a drag gesture. Using
>> 100 ms everything works perfectly!
> Does 160 ms works too?
160 ms works too but I have a feeling that values closer to 200 ms gives 
quite a laggy experience so I'd suggest to keep value closer to 100 ms. 
Beside that I haven't seen situation that "normal" syn_report have been 
repored after longer delay than 30 ms. Mean value is 9 ms and 95 pp ~10 
ms (tested by drags with evemu-record)

> I'd rather have 10 times the maximum time
> between 2 reports than 6.25 times it :)
> We can use 96 ms if 160 doesn't work.
In fact 100 ms it is exactly 6 times the maximum time between 2 reports, 
because 60 Hz frequency gives 16,(6) ms period

>> What do you think that should be changed
>> more in the patch to make it ready for being submitted as an official patch?
> Not much actually. I need to wrote down a commit message, sign it
> (your sign-off-by can also be added given that you debugged it), and
> that should be it.
>
>> I thought about some unit tests, but can't find any for hid drivers also I
> I have a test suite that can emulate hid devices and inject them in
> hid-multitouch. The setup is a little bit manual, so I'll try to run
> it today and see if there are differences with or without the patch.
Ok, waiting for signed patch

  parent reply	other threads:[~2017-05-16  9:46 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-06 19:28 Missing release event for Synaptics touchscreen Arek Burdach
2017-05-09  8:35 ` Benjamin Tissoires
2017-05-09  9:20   ` Arek Burdach
2017-05-09 12:20     ` Benjamin Tissoires
2017-05-09 12:51       ` Arek Burdach
2017-05-09 14:02         ` Benjamin Tissoires
2017-05-09 23:17           ` Arek Burdach
2017-05-09 23:47             ` Andrew Duggan
2017-05-10  9:36               ` Arek Burdach
2017-05-11  9:48                 ` Martin Kepplinger
2017-05-11 10:12                   ` Arek Burdach
2017-05-11 11:22                     ` Martin Kepplinger
2017-05-11 11:28                       ` Benjamin Tissoires
2017-05-11 11:44                         ` Arek Burdach
2017-05-11 11:47                         ` Martin Kepplinger
2017-05-11 12:28                           ` Benjamin Tissoires
2017-05-11 12:50                             ` Martin Kepplinger
2017-05-11 14:30                               ` Arek Burdach
2017-05-11 14:45                                 ` Benjamin Tissoires
2017-05-11 15:38                                   ` Arek Burdach
2017-05-12  6:56                                     ` Martin Kepplinger
2017-05-12  7:25                                       ` Arek Burdach
2017-05-12  7:34                                         ` Martin Kepplinger
2017-05-12  7:39                                         ` Benjamin Tissoires
2017-05-12  7:57                                           ` Arek Burdach
2017-05-12 14:23                                             ` Benjamin Tissoires
2017-05-12 14:28                                               ` Benjamin Tissoires
2017-05-12 17:50                                                 ` Arek Burdach
2017-05-15 18:49                                                 ` Arek Burdach
     [not found]                                                 ` <c0ba39eb-c8d5-2473-36d9-ce7c605ef845@gmail.com>
2017-05-16  8:18                                                   ` Benjamin Tissoires
2017-05-16  9:34                                                     ` Benjamin Tissoires
2017-05-16  9:46                                                     ` Arek Burdach [this message]
2017-06-07  7:27                                                       ` Arek Burdach
2017-06-07 13:12                                                         ` Benjamin Tissoires
2017-06-07 17:58                                                           ` Arek Burdach
2017-05-11 11:36                       ` Arek Burdach
2017-05-11 11:36                       ` Martin Kepplinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=699f72dc-25fe-3ffb-a20a-7800a09f0c86@gmail.com \
    --to=arek.burdach@gmail.com \
    --cc=aduggan@synaptics.com \
    --cc=benjamin.tissoires@gmail.com \
    --cc=chatty@enac.fr \
    --cc=linux-input@vger.kernel.org \
    --cc=martin.kepplinger@ginzinger.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).