linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH v4 4/4] HID: multitouch: Combine all left-button events in a frame
Date: Wed, 22 Nov 2017 12:55:34 +0100	[thread overview]
Message-ID: <e2f18cad-616a-9272-cad4-a3081d016745@redhat.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.1711211310230.11505@cbobk.fhfr.pm>

Hi,

On 21-11-17 13:11, Jiri Kosina wrote:
> On Tue, 14 Nov 2017, Benjamin Tissoires wrote:
> 
>>> According to the Win8 Precision Touchpad spec, inside the HID_UP_BUTTON
>>> usage-page usage 1 is for a clickpad getting clicked, 2 for an external
>>> left button and 3 for an external right button. Since Linux uses
>>> BTN_LEFT for a clickpad being clicked we end up mapping both usage 1
>>> and 2 to BTN_LEFT and if a single report contains both then we ended
>>> up always reporting the value of both in a single SYN, e.g. :
>>> BTN_LEFT 1, BTN_LEFT 0, SYN. This happens for example with Hantick
>>> HTT5288 i2c mt touchpads.
>>>
>>> This commit fixes this by not immediately reporting left button when we
>>> parse the report, but instead storing or-ing together the values and
>>> reporting the result from mt_sync_frame() when we've a complete frame.
>>>
>>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>>> ---
>>
>> Thanks Hans for the re-spin of the series.
>> I think we are good now, series is:
>>
>> Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
> 
> Thanks. Hans, last request for you -- HID_DG_SCANTIME handling has in the
> meantime added for forwarding the MSC_TIMESTAMP (commit 29cc309d8bf1).
> Could you please respin your patch on top of that (basically just merge
> your handling with the one added for MSC_TIMESTAMP) and resend? I'll then
> queue it for 4.16. Thanks,

Ok, v5 with this fixed coming up.

Since this fixes 2 touchpad models not working (not being usable at
least) it would be nice to get this series into 4.15 rc2/rc3 as a
bugfix IMHO.

Regards,

Hans

  reply	other threads:[~2017-11-22 11:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-13 16:32 [PATCH v4 1/4] HID: multitouch: Fix alphabetic sorting of mt_devices table Hans de Goede
2017-11-13 16:32 ` [PATCH v4 2/4] HID: multitouch: Properly deal with Win8 PTP reports with 0 touches Hans de Goede
2017-11-13 16:32 ` [PATCH v4 3/4] HID: multitouch: Only look at non touch fields in first packet of a frame Hans de Goede
2017-11-13 16:32 ` [PATCH v4 4/4] HID: multitouch: Combine all left-button events in " Hans de Goede
2017-11-14  8:02   ` Benjamin Tissoires
2017-11-21 12:11     ` Jiri Kosina
2017-11-22 11:55       ` Hans de Goede [this message]
2017-11-22 13:37         ` Jiri Kosina
2017-11-22 13:41           ` Hans de Goede
2017-11-22 13:59             ` Benjamin Tissoires
2017-11-22 14:01               ` Hans de Goede
2017-11-22 14:08                 ` Benjamin Tissoires

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=e2f18cad-616a-9272-cad4-a3081d016745@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    /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).