From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Odoben <odoben@flipperpa.ws>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Niels Franke <nielsfranke@gmail.com>,
westeri@kernel.org, linux-i2c@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: acpi: Add ELAN0678 to i2c_acpi_force_100khz_device_ids
Date: Wed, 13 May 2026 06:55:20 +0200 [thread overview]
Message-ID: <20260513045520.GF84797@black.igk.intel.com> (raw)
In-Reply-To: <1453fe0d-230c-4655-93ad-3f685b8ab713@flipperpa.ws>
Hi,
On Tue, May 12, 2026 at 11:36:26PM +0200, Odoben wrote:
> Hi,
>
> I have what appears to be the same issue on a ThinkPad X13 Gen 2 with
> Intel i5-1145G7, but with ACPI HID ELAN0676 instead of ELAN0678.
>
> The touchpad is:
>
> ELAN0676:00 04F3:3195 Touchpad
>
> libinput reports:
>
> Id: i2c:04f3:3195
>
> dmesg shows:
>
> i2c_designware.0 -> i2c-ELAN0676:00 -> hid-multitouch
>
> The ACPI table contains:
>
> Package (0x06)
> {
> 0x04F3,
> 0x3195,
> 0x15,
> One,
> One,
> "ELAN0676"
> }
>
> and the surrounding firmware logic maps the fifth field to speed:
>
> Local5 == Zero -> SPED = 0x000186A0 = 100 kHz
> Local5 == One -> SPED = 0x00061A80 = 400 kHz
>
> So this machine also configures the 04F3:3195 ELAN touchpad at 400 kHz. The
> symptom is very frequent rubbery/sluggish pointer movement, consistent with
> the excessive smoothing described for ELAN0678.
>
> Would it make sense to include ELAN0676 in the
> same i2c_acpi_force_100khz_device_ids quirk?
Did you try 100Hz and it made the problem go away? In that case yes it
makes sense to add the quirk.
prev parent reply other threads:[~2026-05-13 4:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-18 5:37 [PATCH] i2c: acpi: Add ELAN0678 to i2c_acpi_force_100khz_device_ids Niels Franke
2026-04-20 8:37 ` Mika Westerberg
2026-05-04 9:19 ` Wolfram Sang
2026-05-12 21:36 ` Odoben
2026-05-13 4:50 ` Wolfram Sang
2026-05-13 4:55 ` 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=20260513045520.GF84797@black.igk.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nielsfranke@gmail.com \
--cc=odoben@flipperpa.ws \
--cc=westeri@kernel.org \
--cc=wsa+renesas@sang-engineering.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