linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Spurious touchpad events with closed LID
Date: Mon, 26 Jun 2017 18:54:53 +0200	[thread overview]
Message-ID: <201706261854.53970@pali> (raw)

[-- Attachment #1: Type: text/plain, Size: 690 bytes --]

Hi!

When I'm using dock with external input devices (keyboard + mouse) and 
LID is closed, I'm getting spurious touchpad events and random mouse 
clicks and movements.

It is because top part of LID is above touchpad and probably generates 
touch pushes.

Year (or two?) when I had conversation with ALPS people I was told that 
Windows driver is automatically turning touchpad off when ACPI LID close 
event is received (and similarly turn touchpad on).

Maybe Linux should do similar thing? Random movement or touchpad clicks 
is really annoying. But I'm not sure if kernel or userspace should do 
this job... What do you think?

-- 
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2017-06-26 16:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26 16:54 Pali Rohár [this message]
2017-06-26 17:03 ` Spurious touchpad events with closed LID Dmitry Torokhov
2017-06-26 19:09   ` Pali Rohár
2017-06-28 20:15     ` Pavel Machek
2017-06-28 22:44       ` Bastien Nocera
2017-06-29  7:31         ` Pali Rohár
2017-06-29 10:08           ` Pavel Machek
2017-06-29 10:11             ` Pali Rohár
2017-06-29 10:15               ` Pavel Machek
2017-06-29 10:24                 ` Pali Rohár
2017-06-29 10:37           ` Bastien Nocera

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=201706261854.53970@pali \
    --to=pali.rohar@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@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).