All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Abhijeeth Babu <babu.jeeth@gmail.com>
Cc: Mika Westerberg <westeri@kernel.org>,
	Andi Shyti <andi.shyti@kernel.org>,
	linux-i2c@vger.kernel.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: acpi: Force ELAN1300 touchpads to 100 kHz
Date: Thu, 18 Jun 2026 08:09:16 +0200	[thread overview]
Message-ID: <20260618060916.GI2990@black.igk.intel.com> (raw)
In-Reply-To: <20260617192611.125513-1-babu.jeeth@gmail.com>

On Thu, Jun 18, 2026 at 12:56:11AM +0530, Abhijeeth Babu wrote:
> The ELAN1300 touchpad with HID ID 04F3:3104 on the ASUS VivoBook
> X513UA_KM513UA exhibits severe pointer jumps and erratic movement when
> the I2C bus operates at 400 kHz.
> 
> The system DSDT describes the touchpad using an I2cSerialBusV2 resource
> with a speed of 0x00061A80, corresponding to 400 kHz, on the
> AMDI0010:03 controller.
> 
> At this speed, libinput repeatedly reports:
> 
> kernel bug: Touch jump detected and discarded
> 
> Add ELAN1300 to i2c_acpi_force_100khz_device_ids so that it operates at
> 100 kHz.
> 
> Before the change, nine touch-jump events were recorded, with additional
> messages suppressed by libinput's rate limiter. With the bus forced to
> 100 kHz, no touch-jump events have been observed and the touchpad operates
> normally.
> 
> The affected system uses BIOS X513UA.319 dated 2023-05-09.
> 
> Signed-off-by: Abhijeeth Babu <babu.jeeth@gmail.com>

Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>

      reply	other threads:[~2026-06-18  6:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-17 19:26 [PATCH] i2c: acpi: Force ELAN1300 touchpads to 100 kHz Abhijeeth Babu
2026-06-18  6:09 ` 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=20260618060916.GI2990@black.igk.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=andi.shyti@kernel.org \
    --cc=babu.jeeth@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=westeri@kernel.org \
    /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.