All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wladimir Mutel <mwg@mwg.dp.ua>
To: dmitry.torokhov@gmail.com
Cc: linux-input@vger.kernel.org
Subject: support for some types of Asus+Elantech touchpads
Date: Tue, 1 Dec 2015 21:59:28 +0200	[thread overview]
Message-ID: <565DFC20.7070303@mwg.dp.ua> (raw)

Dear Dmitry & linux-input members,

some new Asus (and probably non-Asus) laptops are shipped with a new 
kind of Elantech (not sure if only Elantech) touchpads which are not 
adequately handled by Linux kernel module (psmouse). First problem is 
that these touchpads are dying off (losing their sensitivity and 
response) when the system is put into pm-suspend and then waken up. 
Another problem is that on reload (modprobe -r ... && modprobe ...) of 
psmouse module they are dying off too, in 'dmesg' coming with some 
weird-numbered indexes (like, input5 on initial load and input292 on 
reload of psmouse).

There are some bugs reported in Ubuntu Launchpad on this topic 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519034 is my own, 
also
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490130 , 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506363 , 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504445 and some 
others).
Also there is a proposed patch at
https://marc.info/?l=linux-input&m=144312209020616
and one more report at
http://www.spinics.net/lists/linux-input/msg41634.html

For me, these problems look related. I have Asus X302LA on which I am 
testing Ubuntu Xenial and whose touchpad exhibits this problem. If you 
need I could provide my assistance in testing psmouse module on this 
hardware. Thank you in advance for your response.

             reply	other threads:[~2015-12-01 20:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01 19:59 Wladimir Mutel [this message]
2015-12-01 21:08 ` support for some types of Asus+Elantech touchpads Dmitry Torokhov
2015-12-04 11:32   ` Wladimir Mutel

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=565DFC20.7070303@mwg.dp.ua \
    --to=mwg@mwg.dp.ua \
    --cc=dmitry.torokhov@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.