From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: R Ha <rha051117@gmail.com>
Cc: Jarkko Nikula <jarkko.nikula@linux.intel.com>,
wsa+renesas@sang-engineering.com, linux-i2c@vger.kernel.org,
linux-acpi@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH 1/1] Force ELAN06FA touchpad I2C bus freq to 100KHz
Date: Mon, 13 Jan 2025 08:49:47 +0200 [thread overview]
Message-ID: <20250113064947.GK3713119@black.fi.intel.com> (raw)
In-Reply-To: <CACHtJB-mXYAkmPLT1bV-wZR-3SGfS8R8Wo3i2qUio8a7AmcZtw@mail.gmail.com>
On Sat, Jan 11, 2025 at 10:05:23AM -0600, R Ha wrote:
> Hi,
>
> I updated the description, please let me know if it's covered everything.
Thanks, I commented few things there.
> Just as a question, because the touchpad works well at both 100KHz and
> 1000KHz, is it better to force it to 100KHz or 1000KHz? I was
> considering that the Microsoft docs [1] specified that the frequency
> should be "no less than 400KHz", but didn't change it for now because
> the touchpad feels the same at 100KHz and 1000KHz, including for
> gestures.
>
> Is it possible that there will be any sort of compatibility issues if
> the speed is set to 1000KHz? From what I can tell, the only other
> device on I2C1 is the "Intel Smart Sound" related device, but I'm not
> exactly sure what that does or whether it will work at 1000KHz. The
> sound output itself seems to be unaffected regardless of the
> frequency, though I don't think the other device is directly related
> to sound output.
I would say 100kHz is safer, all the devices should support it even the
older ones.
next prev parent reply other threads:[~2025-01-13 6:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 5:16 [PATCH 0/1] Force I2C bus freq to 100KHz for ELAN06FA touchpad Randolph Ha
2025-01-03 5:16 ` [PATCH 1/1] Force ELAN06FA touchpad I2C bus freq to 100KHz Randolph Ha
2025-01-03 9:33 ` Mika Westerberg
2025-01-03 23:46 ` R Ha
2025-01-05 8:33 ` Mika Westerberg
2025-01-06 1:28 ` [PATCH] " Randolph Ha
2025-01-06 9:00 ` [PATCH 1/1] " R Ha
2025-01-07 7:27 ` Mika Westerberg
2025-01-07 12:16 ` R Ha
2025-01-08 5:51 ` Mika Westerberg
2025-01-08 9:29 ` R Ha
2025-01-09 11:19 ` Mika Westerberg
2025-01-10 8:31 ` R Ha
2025-01-10 11:26 ` Mika Westerberg
2025-01-10 11:45 ` Jarkko Nikula
2025-01-10 12:07 ` Mika Westerberg
2025-01-11 15:57 ` [PATCH] " Randolph Ha
2025-01-13 6:48 ` Mika Westerberg
2025-01-13 19:52 ` Randolph Ha
2025-01-14 11:58 ` Wolfram Sang
2025-01-15 19:39 ` R Ha
2025-01-11 16:05 ` [PATCH 1/1] " R Ha
2025-01-13 6:49 ` Mika Westerberg [this message]
2025-01-06 9:08 ` R Ha
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=20250113064947.GK3713119@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=rha051117@gmail.com \
--cc=trivial@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 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.