From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 45DEFC6FD18 for ; Wed, 29 Mar 2023 08:18:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230458AbjC2ISS (ORCPT ); Wed, 29 Mar 2023 04:18:18 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45770 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230459AbjC2IRj (ORCPT ); Wed, 29 Mar 2023 04:17:39 -0400 Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 536F64EF6; Wed, 29 Mar 2023 01:16:45 -0700 (PDT) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id D888A211BD; Wed, 29 Mar 2023 08:16:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1680077803; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type; bh=1CxvA6Vec2L3ljY2X5FIZQTvJH82AAb0kajv763yrcc=; b=iW/MznSzsWE386N5pghSZ9N24vlV3O2Mzd2+JGsHI/7viBN7PwsLjG1TQ1uuW8RhV0/Ag2 AqzK77izsDMztUVk3h+kx6+RgSd3VUDnzeWW8+N9t0umiuugo8aPxdgdOmlxo8sgtY78r/ WpigR4Lx1TYL1YfAY+jNcopnxJG85Og= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1680077803; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type; bh=1CxvA6Vec2L3ljY2X5FIZQTvJH82AAb0kajv763yrcc=; b=r+w23MQVpKc7HUx4vW1661I/fjvgrOSw4BHDHDlQD0ElHJSdAnhuxg5xvf+E3RIoJ0G7dT TfhfKSZ8ZAuGpsCQ== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id B552C139D3; Wed, 29 Mar 2023 08:16:43 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id +yR9K+vzI2QoXAAAMHmgww (envelope-from ); Wed, 29 Mar 2023 08:16:43 +0000 Date: Wed, 29 Mar 2023 10:16:43 +0200 Message-ID: <87h6u4otuc.wl-tiwai@suse.de> From: Takashi Iwai To: Pali =?ISO-8859-1?Q?Roh=E1r?= , Dmitry Torokhov Cc: regressions@lists.linux.dev, linux-input@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [REGRESSION] wrong coord from Thinkpad TrackPoint since 6.2 kernel User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.2 Mule/6.0 MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-input@vger.kernel.org Hi, we've received a bug report about Thinkpad TrackPoint (ALPS DualPoint Stick) on 6.2 kernel: https://bugzilla.opensuse.org/show_bug.cgi?id=1209805 The device reports the wrong values as the movements, e.g. sometimes a value such as 255, 254 or -255 is returned while usually it should be a smaller value like -1 or 2. The evtest on 6.2.x kernel shows the wrong values like: Event: time 1680037542.898747, type 2 (EV_REL), code 0 (REL_X), value 255 Event: time 1680037542.898747, -------------- SYN_REPORT ------------ Event: time 1680037543.145196, type 2 (EV_REL), code 0 (REL_X), value 1 Event: time 1680037543.145196, -------------- SYN_REPORT ------------ Event: time 1680037543.175087, type 2 (EV_REL), code 1 (REL_Y), value -255 Event: time 1680037543.175087, -------------- SYN_REPORT ------------ Event: time 1680037543.185421, type 2 (EV_REL), code 0 (REL_X), value 1 Event: time 1680037543.185421, type 2 (EV_REL), code 1 (REL_Y), value -255 Event: time 1680037543.185421, -------------- SYN_REPORT ------------ while 6.1.x kernel shows the correct values like: Event: time 1680037386.318058, type 2 (EV_REL), code 0 (REL_X), value -1 Event: time 1680037386.318058, type 2 (EV_REL), code 1 (REL_Y), value -1 Event: time 1680037386.318058, -------------- SYN_REPORT ------------ Event: time 1680037386.328087, type 2 (EV_REL), code 0 (REL_X), value -1 Event: time 1680037386.328087, type 2 (EV_REL), code 1 (REL_Y), value -1 Event: time 1680037386.328087, -------------- SYN_REPORT ------------ Event: time 1680037386.338046, type 2 (EV_REL), code 0 (REL_X), value -1 Event: time 1680037386.338046, type 2 (EV_REL), code 1 (REL_Y), value -2 Event: time 1680037386.338046, -------------- SYN_REPORT ------------ I couldn't see any relevant changes in alps.c between those versions, so this is likely a breakage in a lower layer. Could you guys take a look? Thanks! Takashi