mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@kernel.org>
To: prinn.dev@pm.me
Cc: Mika Westerberg <westeri@kernel.org>,
	linux-i2c@vger.kernel.org,  linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: acpi: Force ASUE140D touchpads to 100 kHz
Date: Tue, 6 Oct 2026 15:44:11 +0200	[thread overview]
Message-ID: <asT6nqQMz13beDyW@zenone.zhora.eu> (raw)
In-Reply-To: <20261004-i2c-acpi-asue140d-100khz-v1-1-cc2dbad00470@pm.me>

Hi Harinn,

next time, please...

On Sun, Oct 04, 2026 at 05:59:53PM +0700, Harinn via B4 Relay wrote:
> From: Harinn <prinn.dev@pm.me>
> 
> The ASUE140D touchpad on the ASUS Zenbook UX3404VC (BIOS UX3404VC.303)
> starts lagging shortly after boot when the bus runs at the 400 kHz the
> DSDT asks for, and only recovers after rebinding i2c-hid. Forcing
> 100 kHz fixes it.
> 
> Signed-off-by: Harinn <prinn.dev@pm.me>

... try to use your full name and ...

> ---
>  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 8f3bdd50186e..e5b27375af31 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.
>  	 */
> +	{ "ASUE140D", 0 },

... develop your patches on top of the -next branch or i2c/i2c.
Your patch has a little conflict I had to fix.

I pushed your patch in i2c/i2c.

Thanks,
Andi

>  	{ "DLL0945", 0 },
>  	{ "ELAN0678", 0 },
>  	{ "ELAN06FA", 0 },

  parent reply	other threads:[~2026-10-06 13:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-04 10:59 Harinn via B4 Relay
2026-10-04 12:04 ` Mika Westerberg
2026-10-06 13:44 ` Andi Shyti [this message]
2026-10-14 15:46   ` James Heppell

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=asT6nqQMz13beDyW@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=prinn.dev@pm.me \
    --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 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®