From: Andrew Duggan <aduggan@synaptics.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Peter Hutterer <peter.hutterer@who-t.net>
Cc: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: [GIT PULL] HID for 4.11
Date: Tue, 28 Feb 2017 23:43:08 -0800 [thread overview]
Message-ID: <06556567-7a6a-5d40-ce4a-1c408956e51e@synaptics.com> (raw)
In-Reply-To: <CA+55aFxeX5SW7kki=wqAhDfxtzuDG0xach7f5eOgJCD8drLuFA@mail.gmail.com>
On 02/28/2017 09:05 PM, Linus Torvalds wrote:
> On Tue, Feb 28, 2017 at 7:24 PM, Peter Hutterer
> <peter.hutterer@who-t.net> wrote:
>> I suspect you're just triggering a bug that wasn't triggered by the ps/2
>> emulation. you can run linput-debug-events --verbose and have a look at the
>> various state debugging information, that may hint at what's going on (e.g.
>> a finger mistaken as palm touch, or something). Or record one such
>> interaction with evemu-record and send it to me (preferrably here [1], if
>> you're using libinput). Also, what version of libinput/synaptics are you on?
> bug reported (it's bug 100014).
>
> This is libinput-1.5.4 on Fedora 24. I attached both the
> libinput-debug-events output as well as evemu-report output, which
> hopefully fills in all the details.
>
> Linus
Actually, it looks like this is a regression which was introduced by
bf3e8502eefd ("Input: synaptics-rmi4 - clean up F30 implementation").
From the bug report I noticed that the INPUT_PROP_BUTTONPAD property
was not set for the touchpad. The previous behavior was to set
INPUT_PROP_BUTTONPAD if F30 detected only one valid button (or if there
was a flag in the platform data). But, now INPUT_PROP_BUTTONPAD is not
being set and libinput does not know that the touchpad is a clickpad.
After updating I was able to reproduce the issue with bf3e8502eefd applied.
Andrew
next prev parent reply other threads:[~2017-03-01 11:25 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 15:20 Jiri Kosina
2017-02-21 2:48 ` Linus Torvalds
2017-02-21 3:03 ` Linus Torvalds
2017-02-21 3:19 ` Linus Torvalds
2017-02-21 4:13 ` Linus Torvalds
2017-02-21 4:37 ` Linus Torvalds
2017-03-01 0:56 ` Linus Torvalds
2017-03-01 2:31 ` Andrew Duggan
2017-03-01 3:24 ` Peter Hutterer
2017-03-01 5:05 ` Linus Torvalds
2017-03-01 7:43 ` Andrew Duggan [this message]
2017-03-01 9:03 ` Benjamin Tissoires
2017-03-01 9:06 ` Benjamin Tissoires
2017-03-01 17:31 ` Dmitry Torokhov
2017-03-01 17:54 ` Linus Torvalds
2017-03-01 17:58 ` Dmitry Torokhov
2017-03-01 18:02 ` Linus Torvalds
2017-02-21 14:17 ` [PATCH] HID: rmi: fallback to generic/multitouch if hid-rmi is not built (was Re: [GIT PULL] HID for 4.11) Jiri Kosina
2017-02-21 15:43 ` Linus Torvalds
2017-02-21 15:46 ` Jiri Kosina
2017-02-21 15:49 ` Linus Torvalds
2017-02-21 17:42 ` Benjamin Tissoires
2017-02-21 21:03 ` Jiri Kosina
2017-02-22 0:53 ` Jason Gerecke
2017-02-21 17:37 ` Benjamin Tissoires
2017-02-21 21:16 ` Andrew Duggan
2017-02-21 9:32 ` ath10k regression on XPS13 Kalle Valo
2017-02-21 18:18 ` David Miller
2017-02-21 18:38 ` Kalle Valo
2017-02-21 18:53 ` David Miller
2017-02-21 19:49 ` Kalle Valo
2017-02-21 21:00 ` David Miller
2017-02-21 18:52 ` Linus Torvalds
2017-02-21 21:01 ` David Miller
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=06556567-7a6a-5d40-ce4a-1c408956e51e@synaptics.com \
--to=aduggan@synaptics.com \
--cc=benjamin.tissoires@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®