From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Donohue Subject: Re: [REGRESSION] Touchpad failure after e7348396c6d5 ("Input: ALPS - fix V8+ protocol handling (73 03 28)") Date: Mon, 19 Jun 2017 14:43:15 -0400 Message-ID: <20170619184315.GF1855@TopQuark.net> References: <937d0082-5c51-e0b5-dcf9-efade5ecbde5@redhat.com> <20170603040349.GB16345@TopQuark.net> <75b84b97-5f36-a3be-bb4e-e43cd72d9921@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Masaki Ota Cc: Laura Abbott , Dmitry Torokhov , Pali Rohar , Nick Fletcher , "linux-input@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "scott.s.lowe@gmail.com" List-Id: linux-input@vger.kernel.org I get the same results as you - x_max and y_max affect cursor speed, and = x_res and y_res seem to have no effect. I can't seem to come up with any= values that cause intermittent cursor issues on one side of the touchpad= . Both max and res do get passed up to the X driver, and I do see reference= s to both max and resolution in xf86-input-evdev, although I haven't actu= ally traced it through to see if/where each value is actually consumed wi= th my setup. Maybe we should ask the user to try a few more tests? 1) Using the original code (without the modifications from bug 195215), a= dd the following before 'return 0' at the end of alps_update_device_area_= ss4_v2(), then run `dmesg | grep num-electrodes` after loading the alps k= ernel module to get the output. This should tell us what values the user= is actually reading from the hardware: psmouse_err(psmouse, "pitch %dx%d num-electrodes %dx%d physical size %dx%dmm res %dx%d max= %dx%d\n", x_pitch, y_pitch, num_x_electrode, num_y_electrode, x_phys / 10, y_phys / 10, priv->x_res, priv->y_res, priv->x_max, priv= ->y_max); 2) Use the old electrode count code but the new pitch code: if (IS_SS4PLUS_DEV(priv->dev_id)) { num_x_electrode =3D SS4_NUMSENSOR_XOFFSET + (otp[1][0] & 0x0F); num_y_electrode =3D SS4_NUMSENSOR_YOFFSET + ((otp[1][0] >> 4) & 0x0F); priv->x_max =3D (num_x_electrode - 1) * SS4_COUNT_PER_ELECTRODE; priv->y_max =3D (num_y_electrode - 1) * SS4_COUNT_PER_ELECTRODE; x_pitch =3D (otp[0][1] & 0x0F) + SS4PLUS_MIN_PITCH_MM; y_pitch =3D ((otp[0][1] >> 4) & 0x0F) + SS4PLUS_MIN_PITCH_MM; } else { 3) Use the new electrode count code but the old pitch code: if (IS_SS4PLUS_DEV(priv->dev_id)) { num_x_electrode =3D SS4PLUS_NUMSENSOR_XOFFSET + (otp[0][2] & 0x0F); num_y_electrode =3D SS4PLUS_NUMSENSOR_YOFFSET + ((otp[0][2] >> 4) & 0x0F); priv->x_max =3D (num_x_electrode - 1) * SS4PLUS_COUNT_PER_ELECTRODE; priv->y_max =3D (num_y_electrode - 1) * SS4PLUS_COUNT_PER_ELECTRODE; x_pitch =3D ((otp[1][2] >> 2) & 0x07) + SS4_MIN_PITCH_MM; y_pitch =3D ((otp[1][2] >> 5) & 0x07) + SS4_MIN_PITCH_MM; } else { On Thu, Jun 15, 2017 at 12:33:29AM +0000, Masaki Ota wrote: > Hi, Paul, Dmitry, >=20 > About Laura's test result, it seems like this issue has to do with x_ma= x, y_max, x_res, y_res. > This values are set as following code. > input_set_abs_params(dev1, ABS_MT_POSITION_X, 0, priv->x_max, 0, 0); > input_set_abs_params(dev1, ABS_MT_POSITION_Y, 0, priv->y_max, 0, 0); >=20 > input_abs_set_res(dev1, ABS_MT_POSITION_X, priv->x_res); > input_abs_set_res(dev1, ABS_MT_POSITION_Y, priv->y_res); >=20 > For testing this code, I assigned an abnormal value to x_max, y_max , a= nd it seems to effect only cursor speed. > About x_res, y_res , there is no effect, even if I set an abnormal valu= e.(need this code?) > I don't understand why these values have to do with this issue. >=20 > Can you guess the root cause of this issue? >=20 > Best Regards, > Masaki Ota > -----Original Message----- > From: Laura Abbott [mailto:labbott@redhat.com]=20 > Sent: Thursday, June 15, 2017 3:53 AM > To: =E5=A4=AA=E7=94=B0 =E7=9C=9F=E5=96=9C Masaki Ota ; Paul Donohue > Cc: Dmitry Torokhov ; Pali Rohar ; Nick Fletcher ; linux-input@vger.= kernel.org; linux-kernel@vger.kernel.org; scott.s.lowe@gmail.com > Subject: Re: [REGRESSION] Touchpad failure after e7348396c6d5 ("Input: = ALPS - fix V8+ protocol handling (73 03 28)") >=20 > On 06/11/2017 10:25 PM, Masaki Ota wrote: > > Hi, Laura, > >=20 > > Could you try to check below modification? > > https://bugzilla.kernel.org/show_bug.cgi?id=3D195215#c10 > >=20 > > This thread person said, the issue was fixed by this change. > > I guess it's a XY coordinate setting problem, though the code that be= fore the patch is applied also has a problem. > >=20 >=20 > With the previous patch plus the part you suggested: >=20 > "it appears as if this resolves all remaining touchpad issues. > Cursor movement works as expected, both on the left-hand and right-hand= sides of the touchpad, and I did not see any issues with two-finger scro= lling on either side of the touchpad. Behavior with this test build appea= red to be identical to 4.10.5, the last "official" kernel release to work= with my touchpad." >=20 > So it sounds like both parts together fix the issue. >=20 > Thanks, > Laura >=20 > > Best Regards, > > Masaki Ota > > -----Original Message----- > > From: Laura Abbott [mailto:labbott@redhat.com] > > Sent: Wednesday, June 07, 2017 1:59 AM > > To: Paul Donohue > > Cc: =E5=A4=AA=E7=94=B0 =E7=9C=9F=E5=96=9C Masaki Ota ; Dmitry Torokhov=20 > > ; Pali Rohar ; Nick=20 > > Fletcher ; linux-input@vger.kernel.org;=20 > > linux-kernel@vger.kernel.org; scott.s.lowe@gmail.com > > Subject: Re: [REGRESSION] Touchpad failure after e7348396c6d5 ("Input= :=20 > > ALPS - fix V8+ protocol handling (73 03 28)") > >=20 > > On 06/02/2017 09:03 PM, Paul Donohue wrote: > >> This might be related to > >> https://bugzilla.kernel.org/show_bug.cgi?id=3D195215 > >> > >> Could you have the user try this change?=20 > >> https://bugzilla.kernel.org/show_bug.cgi?id=3D195215#c12 > >> > >=20 > > https://bugzilla.redhat.com/show_bug.cgi?id=3D1447327#c13 > >=20 > > "Cursor movement seems to work, but there are intermittent two-finger= scrolling issues on the right-hand side of the touchpad. There are no is= sues with cursor movement or two-finger scrolling on the left-hand side o= f the touchpad." > >=20 > >> On Fri, Jun 02, 2017 at 10:54:52AM -0700, Laura Abbott wrote: > >>> Hi, > >>> > >>> Fedora got a bug report > >>> https://bugzilla.redhat.com/show_bug.cgi?id=3D1447327 > >>> of a touchpad failure on a Dell Latitude E7370. Testing showed that= =20 > >>> the bad commit was > >>> > >>> commit e7348396c6d51b57c95c6646c390cd078e038e19 > >>> Author: Masaki Ota > >>> Date: Fri Mar 17 14:10:57 2017 -0700 > >>> > >>> Input: ALPS - fix V8+ protocol handling (73 03 28) > >>> =20 > >>> Devices identified as E7=3D"73 03 28" use slightly modified ver= sion of V8 > >>> protocol, with lower count per electrode, different offsets, an= d different > >>> feature bits in OTP data. > >>> =20 > >>> Fixes: aeaa881f9b17 ("Input: ALPS - set DualPoint flag for 74 0= 3 28 devices") > >>> Signed-off-by: Masaki Ota > >>> Acked-by: Pali Rohar > >>> Tested-by: Paul Donohue > >>> Tested-by: Nick Fletcher > >>> Cc: stable@vger.kernel.org > >>> Signed-off-by: Dmitry Torokhov > >>> > >>> I suspect this particular model needs special handling as well? > >>> > >>> Thanks, > >>> Laura > >>> > >=20 >=20