Linux ACPI
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@kernel.org>
To: YuXin Xiao <xiaoyueyoqwq@gmail.com>
Cc: westeri@kernel.org, linux-i2c@vger.kernel.org,
	 linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] i2c: acpi: Add DELL0A86 to i2c_acpi_force_100khz_device_ids
Date: Wed, 26 Aug 2026 16:09:05 +0200	[thread overview]
Message-ID: <ao7yggBh5-MiEIDm@zenone.zhora.eu> (raw)
In-Reply-To: <20260824181559.146133-1-xiaoyueyoqwq@gmail.com>

Hi YuXin,

Please, next time don't send successive versions as in reply-to.

On Tue, Aug 25, 2026 at 02:15:59AM +0800, YuXin Xiao wrote:
> The ELAN 04F3:3185 touchpad exposed as DELL0A86 on the Dell Inspiron
> 13 5310 intermittently exhibits excessive smoothing when the I2C bus
> runs at 400 kHz. During an affected period pointer movement becomes
> severely sluggish and sticky for tens of seconds.
> 
> The ACPI firmware configures the touchpad bus for 400 kHz. Add DELL0A86
> to i2c_acpi_force_100khz_device_ids so that the bus runs at 100 kHz, as
> is already done for other touchpads exhibiting the same excessive
> smoothing problem.
> 
> With the quirk applied, the kernel reports that the firmware requested
> 400 kHz and that the bus is forced to 100 kHz. The problem did not recur
> during extended heavy use, including an S4 hibernate/resume cycle.
> 
> An independent 2021 report from another Dell Inspiron 13 5310 user
> describes the same intermittent sticky behavior and identifies the same
> DELL0A86 / 04F3:3185 touchpad.
> 
> Link: https://www.reddit.com/r/linuxquestions/comments/nsso5b/help_needed_with_sticky_touchpad_spoiling_brand/
> 
> Assisted-by: Codex:ChatGPT-5.6-Sol
> Assisted-by: OpenCode:Ox Alpha (x-preview-f-free)
> 

Please don't leave a blank line in between tags.

> Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> Signed-off-by: YuXin Xiao <xiaoyueyoqwq@gmail.com>
> ---
> Changes in v4:
> - Add an independent public report for the same model, device, and symptom.
> - No code changes.

Please, don't omit the rest of the changelog. I want to see v2,
v3 and v4.

Anyway, I merged your patch in i2c/i2c.

Thanks,
Andi

>  drivers/i2c/i2c-core-acpi.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/i2c/i2c-core-acpi.c b/drivers/i2c/i2c-core-acpi.c
> index 8f3bdd5..3af0e05 100644
> --- a/drivers/i2c/i2c-core-acpi.c
> +++ b/drivers/i2c/i2c-core-acpi.c
> @@ -371,6 +371,7 @@ static const struct acpi_device_id i2c_acpi_force_100khz_device_ids[] = {
>  	 * the device works without issues on Windows at what is expected to be
>  	 * a 400KHz frequency. The root cause of the issue is not known.
>  	 */
> +	{ "DELL0A86", 0 },
>  	{ "DLL0945", 0 },
>  	{ "ELAN0678", 0 },
>  	{ "ELAN06FA", 0 },
> -- 
> 2.53.0
> 

      reply	other threads:[~2026-08-26 14:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-23 11:56 [PATCH] i2c: acpi: Add DELL0A86 to i2c_acpi_force_100khz_device_ids xiaoyueyoqwq
2026-08-23 12:33 ` [PATCH v2] " xiaoyueyoqwq
2026-08-24 10:22   ` Mika Westerberg
2026-08-24 15:00     ` Andy Shevchenko
2026-08-27  6:22     ` Andy Shevchenko
2026-08-27  7:46       ` xiaoyueyoqwq
2026-08-24 11:18   ` [PATCH v3] " YuXin Xiao
2026-08-24 18:15     ` [PATCH v4] " YuXin Xiao
2026-08-26 14:09       ` Andi Shyti [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=ao7yggBh5-MiEIDm@zenone.zhora.eu \
    --to=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=xiaoyueyoqwq@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