linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Tissoires <benjamin.tissoires@redhat.com>
To: Masaki Ota <masaki.ota@jp.alps.com>,
	Damjan Georgievski <gdamjan@gmail.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: Trackpoint on Thinkpad X1 Carbon (5th gen)
Date: Tue, 6 Jun 2017 09:49:09 +0200	[thread overview]
Message-ID: <20170606074909.GU1293@mail.corp.redhat.com> (raw)
In-Reply-To: <KAWPR01MB1092B90F0C1C12D5E3C40DB5C7CA0@KAWPR01MB1092.jpnprd01.prod.outlook.com>

Hi,

On Jun 05 2017 or thereabouts, Masaki Ota wrote:
> Hi, Damjan,
> 
> Latest X1 Carbon system has two TrackPoint venders.
> One is Alps, the other is Elantech. ( Touchpad is only Synaptics.)
> 
> To detect the device, we can send "E1" command by using pass-through.
> The device response is as below.
> If Alps, E1 -> 02
> If Elantech, E1-> 01
> 
> It's a spec, but I have not checked it.

Thanks. This made me realize that we have a difference between the PS/2
handling of the touchpad and the RMI4 use: in the PS/2 protocol, we
mark the pass-through device as such by using SERIO_PS_PSTHRU.
While in RMI4, we mark it as if it was a platform device, meaning we
check on every protocol.

Damjan, would you mind trying the following change:
diff --git a/drivers/input/rmi4/rmi_f03.c b/drivers/input/rmi4/rmi_f03.c
index 77dad04..ad71a5e 100644
--- a/drivers/input/rmi4/rmi_f03.c
+++ b/drivers/input/rmi4/rmi_f03.c
@@ -146,7 +146,7 @@ static int rmi_f03_register_pt(struct f03_data *f03)
        if (!serio)
                return -ENOMEM;
 
-       serio->id.type = SERIO_8042;
+       serio->id.type = SERIO_PS_PSTHRU;
        serio->write = rmi_f03_pt_write;
        serio->port_data = f03;

---

If this gives equal results than when using synaptics_intertouch=0, then
I guess this will be a good candidate for an rc.

Cheers,
Benjamin

> 
> By the way, TrackPoint speed might be different between Alps and Elan.
> And Middle Button Click behavior without a driver is the same as Mouse middle click.
> 
> Best Regards,
> Masaki Ota
> -----Original Message-----
> From: Damjan Georgievski [mailto:gdamjan@gmail.com] 
> Sent: Friday, June 02, 2017 7:47 PM
> To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Cc: linux-input@vger.kernel.org; Benjamin Tissoires <benjamin.tissoires@redhat.com>; 太田 真喜 Masaki Ota <masaki.ota@jp.alps.com>
> Subject: Re: Trackpoint on Thinkpad X1 Carbon (5th gen)
> 
> On 30 May 2017 at 19:24, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> > On Tue, May 23, 2017 at 11:12 AM, Damjan Georgievski <gdamjan@gmail.com> wrote:
> >> On 19 May 2017 at 22:12, Damjan Georgievski <gdamjan@gmail.com> wrote:
> >>> Hi all,
> >>> the trackpoint on the  Thinkpad X1 Carbon (5th gen) (model 20HQ) is 
> >>> recognised as:
> >>> "ImPS/2 Generic Wheel Mouse" while typically it should be "TPPS/2 
> >>> IBM TrackPoint".
> >>
> >> the following patch[1] adds the X1 Carbon gen 5 to work with the 
> >> rmi4_smbus support, there are some issues though:
> >> - the touchpad _seems_ to be working a bit better (at least that's 
> >> what I feel like)
> >> - the trackpoint moves too fast
> >> - middle click scrolling is not enabled and can't be set with xinput
> >>
> >> Can I do someting to improve/test the trackpoint issues, before 
> >> submiting this for merging?
> >>
> >> ps.
> >> also, when this is aplied the touchpad and trackpoint are recognized 
> >> as
> >>> ⎜   ↳ AlpsPS/2 ALPS DualPoint Stick             id=12   [slave  pointer  (2)]
> >>> ⎜   ↳ AlpsPS/2 ALPS DualPoint TouchPad          id=14   [slave  pointer  (2)]
> >
> > This is surprising that device on F03 pass-through port managed to 
> > respond to ALPS queries...
> 
> 
> actually the touchpad seems to be recognized as
> ⎜   ↳ Synaptics TM3289-002                      id=12   [slave  pointer  (2)]
> 
> and the other two ALPS devices are the trackpoint and its buttons (which I beleive are connected to the touchpad)
> 
> 
> > Masaki, is there a chance to make ALPS detection more robust here as I 
> > do not believe we are dealing with ALPS device here.
> 
> 
> Is there anything else I can test?
> 
> 
> 
> --
> damjan

  reply	other threads:[~2017-06-06  7:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-19 20:12 Trackpoint on Thinkpad X1 Carbon (5th gen) Damjan Georgievski
2017-05-23 18:12 ` Damjan Georgievski
2017-05-30 17:24   ` Dmitry Torokhov
2017-06-02 10:46     ` Damjan Georgievski
2017-06-05  0:52       ` Masaki Ota
2017-06-06  7:49         ` Benjamin Tissoires [this message]
2017-06-06 17:28           ` Damjan Georgievski
2017-06-06 17:41           ` Dmitry Torokhov
2017-06-07  1:18             ` Masaki Ota
2017-06-07  6:34               ` Dmitry Torokhov
2017-06-07  6:36             ` Dmitry Torokhov

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=20170606074909.GU1293@mail.corp.redhat.com \
    --to=benjamin.tissoires@redhat.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=gdamjan@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=masaki.ota@jp.alps.com \
    /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).