From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Nick Green <n.grn@outlook.com>
Cc: Dmitry Mikushin <dmitry@kernelgen.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: [REPORT] synaptics_intertouch on ThinkPad T14 Gen 2 (LEN2072)
Date: Fri, 13 Nov 2026 08:05:30 -0800 [thread overview]
Message-ID: <b51b774b36066fb9aea14fdcf192c3b1@gmail.com> (raw)
In-Reply-To: <CY8PR02MB9252B5E325192960631C286CE7AB2@CY8PR02MB9252.namprd02.prod.outlook.com>
Hi Nick,
On Sat, Aug 29, 2026 at 08:44:23PM +0000, Nick Green wrote:
> Following up on my previous report regarding synaptics_intertouch on the ThinkPad T14 Gen 2 (PNP: LEN2072).
>
> After further daily-use testing, please DO NOT add LEN2072 to the smbus_pnp_ids whitelist.
>
> Key findings:
> 1. Under psmouse.synaptics_intertouch=1 (RMI4/SMBus), the touchpad exhibits intermittent tap-to-click failures during natural use.
> 2. Low-level event debugging via 'libinput measure touchpad-pressure' confirmed that missed taps produce zero evdev events at the kernel level—momentary tap interrupts are being dropped by the SMBus controller before reaching userspace, while continuous swiping and pointer motion transmit normally.
Dmitry Mikushin (CCed) recently tracked down a performance issue with
Synaptics TM3471 (LEN2072) over SMBus where rmi_f12 was reading the
entire 79-byte F12 data packet on every attention interrupt (requiring
three SMBus block reads and taking ~17.4 ms per frame, which capped the
report rate at ~43 Hz), even though only the first 32 bytes (Data1) are
used.
Could you please test his patch series (now in the input next branch)
that limits the F12 read to Data1 and enables SMBus for LEN2072, and
let us know if it resolves the missed taps on your T14 Gen 2:
https://lore.kernel.org/linux-input/20261026142648.2567233-1-dmitry@kernelgen.org/
Thanks.
--
Dmitry
prev parent reply other threads:[~2026-11-13 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 20:44 [REPORT] synaptics_intertouch on ThinkPad T14 Gen 2 (LEN2072) Nick Green
2026-11-13 16:05 ` Dmitry Torokhov [this message]
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=b51b774b36066fb9aea14fdcf192c3b1@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=dmitry@kernelgen.org \
--cc=linux-input@vger.kernel.org \
--cc=n.grn@outlook.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