From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Yuqi Xu <xuyuqiabc@gmail.com>
Cc: westeri@kernel.org, andi.shyti@kernel.org,
linux-i2c@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: acpi: Add ELAN0662 to i2c_acpi_force_100khz_device_ids
Date: Fri, 18 Sep 2026 07:56:53 +0200 [thread overview]
Message-ID: <20260918055653.GD106095@black.igk.intel.com> (raw)
In-Reply-To: <20260918054109.23550-1-xuyuqiabc@gmail.com>
On Fri, Sep 18, 2026 at 01:41:09PM +0800, Yuqi Xu wrote:
> The ELAN0662 touchpad (04F3:317C) in the Lenovo ThinkBook 14 G4+ ARA
> (21D0) intermittently stutters and drops touches. libinput discards
> invalid touch coordinates and logs (rate limited to five messages per
> 24 hours):
>
> libinput error: event6 - ELAN0662:00 04F3:317C Touchpad: kernel
> bug: Touch jump detected and discarded.
>
> The ACPI DSDT describes the touchpad's I2cSerialBus resource on an
> AMDI0010 controller with a connection speed of 0x00061A80 (400 kHz),
> and the kernel does not lower it for this device, so the touchpad runs
> at 400 kHz. This is the same issue previously fixed for ELAN06FA and
> ELAN0678.
>
> Forcing the bus to 100 kHz was tested with a DSDT override on the
> affected machine, and the kernel confirmed the override:
>
> ACPI: Table Upgrade: override [DSDT-LENOVO-CB-01]
>
> Before the change libinput discarded three touch jumps within about a
> minute of touchpad use; after the change no touch jumps were logged
> during more than an hour of normal use. The patch itself was not build
> tested; the behaviour was validated through the ACPI table override
> above.
>
> Assisted-by: DeepSeek:deepseek-v4.1-flash
> Signed-off-by: Yuqi Xu <xuyuqiabc@gmail.com>
Acked-by: Mika Westerberg (Intel) <westeri@kernel.org>
prev parent reply other threads:[~2026-09-18 5:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 5:41 Yuqi Xu
2026-09-18 5:56 ` Mika Westerberg [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=20260918055653.GD106095@black.igk.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andi.shyti@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=westeri@kernel.org \
--cc=xuyuqiabc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®