From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Aditya Garg <gargaditya08@live.com>
Cc: agski33 <agski33@proton.me>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
dmaengine@vger.kernel.org,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Vinod Koul" <vkoul@kernel.org>,
"Benjamin Tissoires" <bentiss@kernel.org>
Subject: Re: [REGRESSION] Re: ELAN1206 Touchpad Bugzilla 219799
Date: Tue, 3 Jun 2025 11:33:53 +0300 [thread overview]
Message-ID: <aD6zcaMAK_r0Bei6@smile.fi.intel.com> (raw)
In-Reply-To: <PN3PR01MB9597F96188E061EB0B7ACBD6B862A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM>
On Mon, Jun 02, 2025 at 11:37:21PM +0530, Aditya Garg wrote:
> On 02-06-2025 11:35 pm, Aditya Garg wrote:
> > On 28-05-2025 07:44 pm, agski33 wrote:
...
> >> I am currently experiencing the issue that was previously reported in the
> >> following BugZilla
> >> entry: https://bugzilla.kernel.org/show_bug.cgi?id=219799. I noticed that
> >> the bug was marked as NEEDINFO so I attempted to fill in the relevant
> >> information.
> >>
> >> From my testing, it seems like IDMA transfers relating to the touchpad
> >> input are taking too long and causing timeouts within hid-multitouch.
Is touchpad interface is I²C?
> >> I contacted ASUS in an attempt to obtain information relating to the
> >> workings of the touchpad that may assist with this issue, however I
> >> believe it is unlikely that I will be able to obtain anything useful from
> >> them.
> >>
> >> I am wondering if anyone has any additional suggestions for next debugging
> >> steps or things that I may try - would be happy to provide any additional
> >> information or do additional debugging etc.
> >>
> >> System Details:
> >> Device: ASUS Q528EH with ELAN1206 Touchpad
> >> Kernel versions: 6.9-rc6 is where the issue starts, persists through all
> >> kernel versions after including latest.
> >> Symptoms: Touchpad cursor will not move.
> >> Additional Observations: Something of potential interest that I noticed
> >> was that it appeared the touchpad is sending data byte by byte when doing
> >> an IDMA transfer, not sure if that is normal or not.
> >>
> >> Any suggestions for next steps are appreciated! Thank you in advance for your time and input.
> >
> > Looking at https://bugzilla.kernel.org/show_bug.cgi?id=219799#c2, dd4478d63b6a2b6891fcc1800eb26ce3f1ead1d4
> > seems to be the patch causing regression.
>
> My bad, its 9140ce47872bfd89fca888c2f992faa51d20c2bc, the mailing list link is correct though.
It doesn't matter, the patch is technically correct — we do not serve the
spurious (not ours) interrupts.
> > https://lore.kernel.org/lkml/20240321120453.1360138-1-andriy.shevchenko@linux.intel.com/
> >
> > Ccing relevant folks here.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2025-06-03 8:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 14:14 ELAN1206 Touchpad Bugzilla 219799 agski33
2025-06-02 18:05 ` [REGRESSION] " Aditya Garg
2025-06-02 18:07 ` Aditya Garg
2025-06-03 8:33 ` Andy Shevchenko [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=aD6zcaMAK_r0Bei6@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=agski33@proton.me \
--cc=bentiss@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=gargaditya08@live.com \
--cc=hkallweit1@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).