linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yves-Alexis Perez <corsac@debian.org>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Andrew Duggan <aduggan@synaptics.com>,
	Hans de Goede <hdegoede@redhat.com>,
	Peter Hutterer <peter.hutterer@who-t.net>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/7] New Lenovos 2015 touchpads: party time!
Date: Thu, 19 Mar 2015 17:47:46 +0100	[thread overview]
Message-ID: <20150319164746.GA1648@balvenie> (raw)
In-Reply-To: <20150319155830.GB18134@mail.corp.redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Thu, Mar 19, 2015 at 11:58:31AM -0400, Benjamin Tissoires wrote:
> On Mar 19 2015 or thereabouts, Yves-Alexis Perez wrote:
> > Am I right? Thanks for the information, I'll also try to point our
> > kernel maintainers to that thread and ask them if it's possible to
> > backport them to the 3.16 kernel for Jessie.
> 
> Yes, please do. For the record, they are already in Fedora.
> 
Ok, will do.

> Again, sorry, I thought I answered it. With the kernel patches applied:
> - disabled in the bios without psmouse.proto=imps -> touchpad still
>   enabled, trackstick + buttons working
> - disabling in the bios + psmouse.proto=imps -> touchpad disabled,
>   trackstick + buttons working
> - enabled in the bios + psmouse.proto=imps -> touchpad barely usable,
>   trackstick + buttons working
> 
> That should cover all the cases :)
> 
Actually, one is missing: “touchpad enabled / without
psmouse.proto=imps”, but it doesn't really matter for me since I'm not
using the touchpad anyway.

But that also means if I want a disabled touchpad (without using xinput
disable) I'm forced to use psmouse.proto=imps. It does work fine but I
then lose the speed and sensitivity attributes (in
/sys/devices/platform/i8042/...) and the Trackpoint device itself is
gone from the input subsystem (everything goes to the touchpad one).

I find that a bit confusing, and think it'd be best if the touchpad
disabling could be handled even when IMPS/2 is not used, but maybe it's
impossible to do?

Sorry for the ~user-related questions.

Regards,
- -- 
Yves-Alexis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCgAGBQJVCv2tAAoJEG3bU/KmdcCl1KsIAJOH5Q2v/Dtp5R69Sgq3ERcU
VscKl3K4Mqv4U8mNU47PBgSRWBOlZ7OuOkyJbo/gBKaxwNP6mnctn8BWfu3bzXVA
ycSbUgpiws+EsZXkPL+ej7qtxWu0UamUKR9Aoeto6NDy/2KCzcBWCGtfgyVFvsL7
BxC9bPX2tGhgE+9tt+S+AW03aovSfmIipV7XCY3A5hB1lzpjvZwagAzY5PwgI9sj
8gsaDlHeb9l0KFtElVgU+aF2CM1Q07VWQbE6Jcims2LJgLcrOWraye50YP/s7WA4
dC+9n+yY4bm3Q1YyjKUK8Rgq7WzWJFk8O+mJlS81I3tc41Ihg/RlZkUKxg7rM4A=
=YqYu
-----END PGP SIGNATURE-----
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-03-19 16:49 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06 20:04 [PATCH v2 0/7] New Lenovos 2015 touchpads: party time! Benjamin Tissoires
2015-02-06 20:04 ` [PATCH v2 1/7] Input: synaptics - fix middle button on Lenovo 2015 products Benjamin Tissoires
2015-02-06 20:04 ` [PATCH v2 2/7] Input: synaptics - handle spurious release of trackstick buttons Benjamin Tissoires
2015-02-06 20:04 ` [PATCH v2 3/7] Input: synaptics - do not retrieve the board id on old firmwares Benjamin Tissoires
2015-02-06 20:04 ` [PATCH v2 4/7] Input: synaptics - retrieve the extended capabilities in query $10 Benjamin Tissoires
2015-02-06 20:04 ` [PATCH v2 5/7] Input: synaptics - remove TOPBUTTONPAD property for Lenovos 2015 Benjamin Tissoires
2015-02-06 20:04 ` [PATCH v2 6/7] Input: synaptics - re-route tracksticks buttons on the Lenovo 2015 series Benjamin Tissoires
2015-03-09  6:45   ` Dmitry Torokhov
2015-02-06 20:04 ` [PATCH v2 7/7] Input: synaptics - Remove X1 Carbon 3rd gen from the topbuttonpad list Benjamin Tissoires
2015-02-17  3:23 ` [PATCH v2 0/7] New Lenovos 2015 touchpads: party time! Benjamin Tissoires
2015-02-25 14:36   ` Benjamin Tissoires
2015-02-25 14:58     ` Hans de Goede
2015-03-09  6:46       ` Dmitry Torokhov
2015-03-09  8:24         ` Hans de Goede
2015-03-09 19:36           ` Benjamin Tissoires
2015-03-10  6:17             ` Steven Noonan
2015-03-10  7:23               ` Hans de Goede
2015-03-10 18:35                 ` Steven Noonan
2015-03-16 14:46             ` Benjamin Tissoires
2015-03-19 14:24 ` Yves-Alexis Perez
2015-03-19 14:46   ` Benjamin Tissoires
2015-03-19 15:25     ` Yves-Alexis Perez
2015-03-19 15:58       ` Benjamin Tissoires
2015-03-19 16:47         ` Yves-Alexis Perez [this message]
2015-03-19 17:06           ` Benjamin Tissoires
2015-03-19 17:43             ` Dmitry Torokhov
2015-03-19 18:29               ` Benjamin Tissoires
2015-03-20 13:59             ` Yves-Alexis Perez
2015-04-09 12:59         ` Yves-Alexis Perez
2015-04-09 13:56           ` Benjamin Tissoires

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=20150319164746.GA1648@balvenie \
    --to=corsac@debian.org \
    --cc=aduggan@synaptics.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.hutterer@who-t.net \
    /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).