From mboxrd@z Thu Jan 1 00:00:00 1970 From: Juanito Subject: Re: ALPS touchpad ot correctly recognized: GlidePoint vs DualPoint Date: Mon, 5 Feb 2018 12:19:48 +0100 Message-ID: <712c2657-5cf6-5fa0-1358-82bece1c02f8@posteo.net> References: <201709080848.53286@pali> <52f87b68-8a6b-1d9c-f341-1e488ff43441@posteo.net> <201709091036.06899@pali> <20170909181218.GA29107@dtor-ws> <7d5d4e88-b6d2-ce7b-a529-18f2b131fa7f@posteo.net> <20180204181605.eknruesqvvnncrqd@pali> <20180204202118.fmyhcqmteyu6jnit@pali> <131d0bb6-4861-95a0-3963-790c91cb3912@posteo.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="BJD6UkIaBtfx5QasDlMOfIF5oHLvDB7JB" Return-path: Received: from mout01.posteo.de ([185.67.36.65]:56274 "EHLO mout01.posteo.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751705AbeBELUE (ORCPT ); Mon, 5 Feb 2018 06:20:04 -0500 Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id 0976A20DDB for ; Mon, 5 Feb 2018 12:20:02 +0100 (CET) In-Reply-To: <131d0bb6-4861-95a0-3963-790c91cb3912@posteo.net> Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: =?UTF-8?Q?Pali_Roh=c3=a1r?= Cc: Masaki Ota , Dmitry Torokhov , "linux-input@vger.kernel.org" , Paul Donohue This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --BJD6UkIaBtfx5QasDlMOfIF5oHLvDB7JB Content-Type: multipart/mixed; boundary="46TWHWU2wXm0l2bSWQT1LjwcBNEO9i7K1"; protected-headers="v1" From: Juanito To: =?UTF-8?Q?Pali_Roh=c3=a1r?= Cc: Masaki Ota , Dmitry Torokhov , "linux-input@vger.kernel.org" , Paul Donohue Message-ID: <712c2657-5cf6-5fa0-1358-82bece1c02f8@posteo.net> Subject: Re: ALPS touchpad ot correctly recognized: GlidePoint vs DualPoint References: <201709080848.53286@pali> <52f87b68-8a6b-1d9c-f341-1e488ff43441@posteo.net> <201709091036.06899@pali> <20170909181218.GA29107@dtor-ws> <7d5d4e88-b6d2-ce7b-a529-18f2b131fa7f@posteo.net> <20180204181605.eknruesqvvnncrqd@pali> <20180204202118.fmyhcqmteyu6jnit@pali> <131d0bb6-4861-95a0-3963-790c91cb3912@posteo.net> In-Reply-To: <131d0bb6-4861-95a0-3963-790c91cb3912@posteo.net> --46TWHWU2wXm0l2bSWQT1LjwcBNEO9i7K1 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 02/05/2018 08:48 AM, Juanito wrote: > On 02/04/2018 09:21 PM, Pali Roh=C3=A1r wrote: >> On Sunday 04 February 2018 20:39:06 Juanito wrote: >>> On 02/04/2018 07:16 PM, Pali Roh=C3=A1r wrote: >>>> On Monday 11 September 2017 13:26:30 Juanito wrote: >>>>> Hi Masaki Ota, >>>>> >>>>> Thanks! >>>>> >>>>> On 11.09.2017 04:38, Masaki Ota wrote: >>>>>> Hi, Juanito, >>>>>> >>>>>> In my information, ALPS Touchpad is used on Thinkpad E series and = L series. >>>>>> I don't know the device that is ALPS Touchpad + other vendor Track= Stick. >>>>>> But Lenovo might use ALPS Touchpad on such a combination. >>>>>> >>>>> >>>>> Well, that is probably my fault, as it is not the original touchpad= that >>>>> was delievered with the laptop. I bought the touchpad (that include= d >>>>> the three buttons) separately because I didn't like the clickpad th= at >>>>> came with my laptop. >>>> >>>> Hi Juanito, >>>> >>> >>> Hi Pali, >>> >>>> if you are still want to play with your touchpad hardware, I have a = good >>>> news for your. >>>> >>> >>> Yeah! I'd love to get it to work! It's just I've been "working" on so= me >>> other projects and my last kernel builds didn't work at all so I gave= up >>> and never got back to it. >>> >>> Thank you very much for that! >>> >>>> It looks like that at least ALPS rushmore touchpads allow to receive= RAW >>>> PS/2 packets from trackstick to host kernel, without modifying them = by >>>> touchpad. Plus I was able to tell ALPS touchpad to start "mixing" th= ose >>>> RAW trackstick PS/2 packets with native touchpad packets. >>>> >>>> On my configuration trackstick in RAW PS/2 mode by default talks wit= h >>>> standard bare 3 byte PS/2 protocol and touchpad in 6 byte ALPS proto= col. >>>> alps.c/psmouse.ko is already able to process and parse such mixed >>>> packets. And trackstick can be switched to some extended 4 byte >>>> protocol... >>>> >>>> All this happen when passthrough mode is enabled. >>>> >>>> From my understanding it seems that in normal mode, touchpad and >>>> trackstick communicate with that 4 byte protocol and touchpad conver= ts >>>> it into 6 byte ALPS protocol and then send to kernel. >>>> >>>> On thinkpads trackstick communicate with TPPS/2 protcol and above 4 >>>> byte. So in my opinion ALPS touchpad by default cannot understand it= =2E >>>> But you should be able to enter passthrough mode and then you would >>>> receive that TPPS/2 in alps kernel code. >>>> >>> >>> I don't really understand what you mean. Do I "just" have to set it t= o >>> passthrough mode? How exactly can I do that? >> >> Look at function alps_passthrough_mode_v3(). And try to call it after >> touchpad is initialized. >> >=20 > Cool, I'll give this a try! >=20 >> You can also look which alps_command_mode_write_reg() functions are >> called for your touchpad and maybe try to figure out what those the >> registers can enabled/disable. >> >> On http://www.cirque.com/gen4-dev-resources you can find document name= d >> GP-AN- 130823 INTERFACING TO GEN4 OVER I2C (PDF) which contains >> some description of those registers (in section 7). >> >> Register C2C8, bit 0 has description "PS2AuxControl.CommandPassThruEna= bled" >> >> If trackstick is not detected, it seems you can "force" enable it by >> setting bit 7 "PS2AuxControl.AuxDevicePresent" in same register. >> >>> Again, thank you very much! >> >> Have you tried to read from that register which Masaki Ota talked in >> previous emails? >> >=20 > I tried but I just didn't manage to get it to work, at all and gave up > (I really am a newbie in this whole kernel world). Maybe a fresh start > helps here. > Oh, oh! Currently, my touchpad is just being recognized as a PS/2 Generic Mouse. On both debian stretch kernel (4.9.0-5-amd64) and on a 4.15.0+ compiled by me. I'll try to see if I can find out why this is happening. Do have any idea why this might be the case (it used to be recognized as ALPS)? Cheers, Juanito --46TWHWU2wXm0l2bSWQT1LjwcBNEO9i7K1-- --BJD6UkIaBtfx5QasDlMOfIF5oHLvDB7JB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEQQcjO70/bl99Yhbk4tnJgO9QcV4FAlp4Pd4ACgkQ4tnJgO9Q cV5tHQ//YoZLKD3f8y/CqEasMGNt43Wam7RPXlSj4ElHIM0nK9y6hEDktZXUxsbE nAxuElw0Pjc+jYyb0pKixu1gpCrzfEsxWZzv7rqJYNi0Qw+jKVGLyPeE90OLzySQ i+NwRhAk+Kh7LE2MMLFG2/pi5xJcoMhIuDQVVmRJ/lLFngA+qOkpbm1Dik7pY50k 16jkSmKSpoT2DVuTlItr6DP1NgxbHUAICSAZmYIpAwoqac/t9XBbxr7S77b6i/A9 KdBU/2802NmRm2IlZ6nzyr0E8wkDSrqY0XrabT3VYpbHrgF/+k6UHtwZQItbm6n3 djtLmW+Cvq19GT8Npil3XUo6INy4oy7wzen0CyD+5nu6UpYykxaSTufOMhHuk/J+ NdalEd42awscjDwJJ7mBGarPFdPhPRNzRrAtW7om5fS0HfIKMbRCxI2SlKOzQoVG o1xT1P5ngdjzWR5fxTsbx9w7Xv18qqjgOwPlBVq/UlqCgtjxYTvXiuaiYqPfJsJP UqD0t1BYO3s75ETfAUCavl0aM/iDl6firufBGzESfLSl+1dLn7RYjv1acWbhxytQ UMGCFr7XHDZeASjldTuibuVYtjr08RSPh0RPRDC4lneUacf21HqkMVte4hu0WobD /2AJjzHii3OaakMOAOXGdSl93rs0E1WKg9a9Y7b6e91m9qe+cl8= =Txtc -----END PGP SIGNATURE----- --BJD6UkIaBtfx5QasDlMOfIF5oHLvDB7JB--