From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: correctmost <cmlists@sent.com>,
dmaengine@vger.kernel.org, regressions@lists.linux.dev,
vkoul@kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [REGRESSION][BISECTED] Lenovo IdeaPad touchpad does not work when idma64 is present in initramfs
Date: Tue, 27 Jan 2026 17:09:18 +0200 [thread overview]
Message-ID: <aXjVHocwkflAnKw2@smile.fi.intel.com> (raw)
In-Reply-To: <20260127144357.GL2275908@black.igk.intel.com>
On Tue, Jan 27, 2026 at 03:43:57PM +0100, Mika Westerberg wrote:
> On Tue, Jan 27, 2026 at 05:56:37AM -0500, correctmost wrote:
...
> > > Okay can you set CONFIG_INTEL_IDMA64=n in .config? That should prevent it
> > > from loading. Keep the rest as it was.
> >
> > That change makes the IRQ message go away and the touchpad seems to work
> > fine in my desktop environment (log attached).
> >
> > These are the config changes that I tested with:
> > - CONFIG_I2C_DESIGNWARE_CORE=m
> > - CONFIG_I2C_DESIGNWARE_PLATFORM=m
> > - CONFIG_INTEL_IDMA64=n
>
> Okay thanks it looks good to me too.
>
> I tried to go through the datasheets again but could not figure why the
> LPSS I2C IP would keep the interrupt asserted.
We can try to dig something internally, but it's another story.
> However, I think we can
> hack^Hwork this around by simply not creating the IDMA64 device at all for
> I2C. This should be fine to do because I2C is really not using DMA in the
> first place so this is kind of just wasting "memory". So something like
> below.
>
> Please re-enable CONFIG_INTEL_IDMA64=m and the rest and try if this makes
> it work without the irq splat. And if it does please try with the
> "original" arch setup and see if that works too (keeping the patch applied
> of course).
>
> Andy, what's your thoughts on this?
Fun fact, that I was thinking about the similar approach as in "don't enumerate
DMA for I²C LPSS controllers" a few hours ago (and for the record, sometime ago
but I don't remember why that time).
So I'm fine, but we need to put also a big comment with the reference to this
discussion or so.
...
Btw, do we have an i2c alert interrupt here? Might be it's somehow related?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-01-27 15:09 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 17:57 [REGRESSION][BISECTED] Lenovo IdeaPad touchpad does not work when idma64 is present in initramfs correctmost
2026-01-12 14:35 ` Andy Shevchenko
2026-01-12 16:52 ` Andy Shevchenko
2026-01-15 22:50 ` correctmost
2026-01-16 10:03 ` Andy Shevchenko
2026-01-16 10:35 ` Andy Shevchenko
2026-01-17 0:25 ` correctmost
2026-01-19 10:39 ` Andy Shevchenko
2026-01-19 10:49 ` Andy Shevchenko
2026-01-20 9:33 ` Andy Shevchenko
2026-01-21 4:56 ` correctmost
2026-01-21 9:13 ` Andy Shevchenko
2026-01-21 13:58 ` Mika Westerberg
2026-01-21 14:54 ` Andy Shevchenko
2026-01-21 15:02 ` Mika Westerberg
2026-01-21 15:19 ` Andy Shevchenko
2026-01-22 11:00 ` Mika Westerberg
2026-01-22 22:29 ` correctmost
2026-01-23 6:36 ` Mika Westerberg
2026-01-25 3:38 ` correctmost
2026-01-26 13:53 ` Mika Westerberg
2026-01-27 6:52 ` correctmost
2026-01-27 8:42 ` Mika Westerberg
2026-01-27 10:11 ` correctmost
2026-01-27 10:19 ` Mika Westerberg
2026-01-27 10:56 ` correctmost
2026-01-27 14:43 ` Mika Westerberg
2026-01-27 15:09 ` Andy Shevchenko [this message]
2026-01-28 3:06 ` correctmost
2026-01-23 6:53 ` Andy Shevchenko
2026-01-28 9:34 ` Andy Shevchenko
2026-01-28 10:21 ` correctmost
2026-01-28 12:31 ` Mika Westerberg
2026-01-29 4:54 ` correctmost
2026-01-29 6:58 ` Mika Westerberg
2026-01-29 7:20 ` correctmost
2026-01-29 11:56 ` Mika Westerberg
2026-01-29 13:06 ` correctmost
2026-01-30 7:26 ` Mika Westerberg
2026-01-30 8:18 ` correctmost
2026-02-02 7:51 ` Mika Westerberg
2026-02-02 8:38 ` correctmost
2026-02-02 10:22 ` Mika Westerberg
2026-02-02 11:16 ` correctmost
2026-02-03 10:04 ` Mika Westerberg
2026-02-03 12:39 ` correctmost
2026-02-04 12:31 ` Mika Westerberg
2026-02-04 13:11 ` correctmost
2026-02-04 13:19 ` Andy Shevchenko
2026-02-04 14:01 ` correctmost
2026-02-04 15:12 ` correctmost
2026-02-04 15:34 ` Mika Westerberg
2026-02-04 15:53 ` correctmost
2026-02-05 10:31 ` Mika Westerberg
2026-02-14 20:17 ` correctmost
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=aXjVHocwkflAnKw2@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=cmlists@sent.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=regressions@lists.linux.dev \
--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 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.