From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Eduardo Henrique Teixeira <ehstbr@gmail.com>
Cc: Dmitry Mikushin <dmitry@kernelgen.org>,
linux-input@vger.kernel.org, lovekeshsolanki00@gmail.com
Subject: Re: [BUG] ThinkPad T490 Synaptics TM3471-020 input lag and missed taps with SMBus/RMI4
Date: Fri, 13 Nov 2026 08:08:44 -0800 [thread overview]
Message-ID: <563ab45500cc33d06b7973075635d0dc@gmail.com> (raw)
In-Reply-To: <CAASp5sxs8o0rAe38Q4YZqK+F6st6TvxKSOR2RoKY9b1-gQCuow@mail.gmail.com>
Hi Eduardo,
On Fri, Oct 30, 2026 at 06:10:50PM -0700, Eduardo Henrique Teixeira wrote:
> I would like to report a possible issue with Synaptics InterTouch
> (SMBus/RMI4) on the Lenovo ThinkPad T490.
>
> Hardware:
>
> - Model: Lenovo ThinkPad T490 (20N3S5DU1N)
> - Touchpad: Synaptics TM3471-020
> - Firmware ID: 3972349
> - BIOS: 1.85
> - Distribution: Ubuntu
> - Kernel: 7.3.0-10-generic
>
> Symptoms:
>
> The touchpad exhibits noticeable delays when detecting finger contact,
> sometimes perceived as approximately 200–500 ms before pointer movement
> begins.
>
> Short taps frequently fail to register as mouse clicks. Longer touches are
> more likely to be recognized.
Dmitry Mikushin (CCed) recently fixed a performance bottleneck on
Synaptics TM3471 over SMBus where rmi_f12 was reading the entire
79-byte F12 data packet on every attention interrupt (requiring three
SMBus block reads and ~17.4 ms per frame, capping the report rate at
~43 Hz), even though only the first 32 bytes (Data1) are used.
Could you please test his two rmi_f12 patches (now in the input next
branch) that limit the F12 read to Data1 (~7.3 ms, ~65 Hz) and see if
they resolve the input lag and missed taps on your T490:
https://lore.kernel.org/linux-input/20261026142648.2567233-2-dmitry@kernelgen.org/
https://lore.kernel.org/linux-input/20261026142648.2567233-3-dmitry@kernelgen.org/
Thanks.
--
Dmitry
next prev parent reply other threads:[~2026-11-13 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAASp5sxs8o0rAe38Q4YZqK+F6st6TvxKSOR2RoKY9b1-gQCuow@mail.gmail.com>
2026-11-01 15:35 ` [BUG] ThinkPad T490 Synaptics TM3471-020 input lag and missed taps with SMBus/RMI4 Lovekesh Solanki
2026-11-13 16:08 ` Dmitry Torokhov [this message]
[not found] <CAASp5sxDHbnSyaRZE4D2BrkZU2XTuLU9R+3mZ0=K00NK+gWMug@mail.gmail.com>
2026-11-03 11:14 ` Lovekesh Solanki
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=563ab45500cc33d06b7973075635d0dc@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=dmitry@kernelgen.org \
--cc=ehstbr@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=lovekeshsolanki00@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.