From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: "fangzhong.zhou" <myth5@myth5.com>
Cc: linux-acpi@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, westeri@kernel.org
Subject: Re: [PATCH v1] i2c: Force DLL0945 touchpad i2c freq to 100khz
Date: Sun, 3 Aug 2025 22:39:42 +0200 [thread overview]
Message-ID: <aI_JDslnEsGEOz0W@shikoro> (raw)
In-Reply-To: <20250802231554.9920-1-myth5@myth5.com>
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
On Sun, Aug 03, 2025 at 07:15:54AM +0800, fangzhong.zhou wrote:
> This patch fixes an issue where the touchpad cursor movement becomes
> slow on the Dell Precision 5560. Force the touchpad freq to 100khz
> as a workaround.
>
> Tested on Dell Precision 5560 with 6.14 to 6.14.6. Cursor movement
> is now smooth and responsive.
>
> Changes in v1:
> - No code changes from first commit.
The "Changes" section should go below "---". I fixed it.
>
> Signed-off-by: fangzhong.zhou <myth5@myth5.com>
> ---
> 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 d2499f302..5b424637b 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[] = {
> * a 400KHz frequency. The root cause of the issue is not known.
> */
> { "ELAN06FA", 0 },
> + { "DLL0945", 0 },
I moved it up to keep alphabetical sorting.
With these changes:
Applied to for-next (for 6.17 mergewindow), thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2025-08-03 20:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 5:28 [PATCH] i2c: Force DLL0945 touchpad i2c freq to 100khz fangzhong.zhou
2025-07-28 8:59 ` Wolfram Sang
2025-08-01 14:54 ` fangzhong.zhou
2025-08-02 23:15 ` [PATCH v1] " fangzhong.zhou
2025-08-03 20:39 ` Wolfram Sang [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=aI_JDslnEsGEOz0W@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=myth5@myth5.com \
--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.