linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arek Burdach <arek.burdach@gmail.com>
To: benjamin.tissoires@gmail.com, chatty@enac.fr, aduggan@synaptics.com
Cc: linux-input@vger.kernel.org
Subject: Missing release event for Synaptics touchscreen
Date: Sat, 6 May 2017 21:28:46 +0200	[thread overview]
Message-ID: <708339c2-2b70-81ae-a939-ac122e5fd6f2@gmail.com> (raw)

Hi,

A week ago I've reported a bug: 
https://bugzilla.kernel.org/show_bug.cgi?id=195625 Is there anybody that 
can help me with it?
I found out that some touchpads (and possible touchscreens?) are handled 
by both hid-multitouch and hid-rmi drivers. Is there a way to verify how 
the touchscreen would work on hid-rmi drivers? I've tested it with 
kernel 4.11.0-rc1 version where was this change:
279967a65b320d174a507498aea7d44db3fee7f4 HID: rmi: Handle all Synaptics 
touchpads using hid-rmi
which was reverted in later kernel's version. On this version, only my 
touchpad was handled by hid-rmi, touchscreen was still handled by 
hid-multitouch. Maybe I should change something in code or in 
compilation configuration to force hid-rmi?
Or it is a wrong way to go? I would be grateful for your help.

Regards,
Arek

             reply	other threads:[~2017-05-06 19:28 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-06 19:28 Arek Burdach [this message]
2017-05-09  8:35 ` Missing release event for Synaptics touchscreen 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
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=708339c2-2b70-81ae-a939-ac122e5fd6f2@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 \
    /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).