From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: R Ha <rha051117@gmail.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: Fri, 10 Jan 2025 14:07:40 +0200 [thread overview]
Message-ID: <20250110120740.GH3713119@black.fi.intel.com> (raw)
In-Reply-To: <0151b609-98d9-402a-b553-c9af5b0eb51f@linux.intel.com>
On Fri, Jan 10, 2025 at 01:45:03PM +0200, Jarkko Nikula wrote:
> On 1/10/25 1:26 PM, Mika Westerberg wrote:
> > Hi,
> >
> > On Fri, Jan 10, 2025 at 02:31:26AM -0600, R Ha wrote:
> > > Hi,
> > >
> > > Sounds like a good idea. I'm a little worried I'm missing something,
> > > so I think being able to check my earlier answers will help as well.
> > > I'm sending the entire output as attachments, but let me know if it's
> > > better to upload them somewhere and paste the link instead. Some of
> > > the ssdt* files are missing, but they're empty files so Gmail won't
> > > let me attach them.
> >
> > Thanks for sharing! Okay checked now dsdt.dsl (the other files are not
> > relevant here) and what I can tell the device is supposed to be run at 400
> > kHz. I suspect this is what Windows is doing as well, there is nothing that
> > indicates otherwise.
> >
> > And since this is a standard I2C HID device it should just work (as it does
> > not require any vendor specific driver even in Windows).
> >
> > Only thing I can think of that affects this is the LCNT/HCNT and SDA hold
> > values of the I2C designware controller (and maybe the input clock) but
> > there is nothing in the ACPI tables that set these so it could be that the
> > Windows driver uses different values for those and that explains why it
> > works better there.
> >
> > @Jarkko, do you have any input here? If we cannot figure a better way then
> > I don't see other option than to add this quirk.
>
> Unfortunately I don't have idea.
Okay thanks anyway! Then I don't see any other option than adding that
quirk.
@R Ha, can you then submit a new version of the patch with the latest
details in the changelog?
next prev parent reply other threads:[~2025-01-10 12:07 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 [this message]
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
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=20250110120740.GH3713119@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox