All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: Spurious touchpad events with closed LID
Date: Thu, 29 Jun 2017 12:37:39 +0200	[thread overview]
Message-ID: <1498732659.6564.8.camel@hadess.net> (raw)
In-Reply-To: <20170629073102.GG25196@pali>

On Thu, 2017-06-29 at 09:31 +0200, Pali Rohár wrote:
> On Thursday 29 June 2017 00:44:27 Bastien Nocera wrote:
> > On Wed, 2017-06-28 at 22:15 +0200, Pavel Machek wrote:
> > > 
> > 
> > <snip>
> > > While policy normally belongs to userspace, I'd argue this is
> > > workaround for a hardware bug, and in-kernel solution would be
> > > acceptable.
> > > 
> > > Anyway, disable attribute would be nice first step.
> > 
> > It's already fixed for those of us on recent distributions. The
> > "ID_INPUT_TOUCHPAD_INTEGRATION=internal" touchpads will be disabled
> > when the lid is closed, when libinput is used to process the
> > events.
> 
> But this does not fix other usage of /dev/input/* and also does not
> fix
> pressing spurious keys in linux virtual tty (ctrl+alt+f1). So it is
> not
> a fix.
> 
> Also important question is: How you detect which input device is
> "internal", non-removable part of notebook and which one is external?

We have heuristics and a database. Look at the hwdb/ subdirectory in
systemd.

> Maybe ACPI/DSDT provides some information? (No idea, just asking)

It could and should, but it's usually empty because when some hardware
makers can't be bothered to change the device's name, they'll hardly
spend that time adding location information, are they?

      parent reply	other threads:[~2017-06-29 10:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26 16:54 Spurious touchpad events with closed LID Pali Rohár
2017-06-26 17:03 ` 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 [this message]

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=1498732659.6564.8.camel@hadess.net \
    --to=hadess@hadess.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pali.rohar@gmail.com \
    --cc=pavel@ucw.cz \
    /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.