From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: correctmost <cmlists@sent.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.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 11:19:12 +0100 [thread overview]
Message-ID: <20260127101912.GJ2275908@black.igk.intel.com> (raw)
In-Reply-To: <b285137a-06bc-43c2-ab24-b3bacf8592ec@app.fastmail.com>
On Tue, Jan 27, 2026 at 05:11:48AM -0500, correctmost wrote:
> On Tue, Jan 27, 2026, at 3:42 AM, Mika Westerberg wrote:
> > On Tue, Jan 27, 2026 at 01:52:01AM -0500, correctmost wrote:
> >> On Mon, Jan 26, 2026, at 8:53 AM, Mika Westerberg wrote:
> >> > On Sat, Jan 24, 2026 at 10:38:14PM -0500, correctmost wrote:
> >> >> I am seeing mixed results with those i2c config changes, depending on which modules are included in the initramfs image.
> >> >>
> >> >> Build info for both tests:
> >> >> - Commit c072629f05d7
> >> >> - CONFIG_I2C_DESIGNWARE_CORE=m
> >> >> - CONFIG_I2C_DESIGNWARE_PLATFORM=m
> >> >>
> >> >> --> Test 1 - Various i2c modules absent from initramfs
> >> >>
> >> >> Modules:
> >> >> - drivers/dma/idma64.ko.zst present in initramfs
> >> >> - drivers/hid/i2c-hid/{i2c-hid-acpi.ko.zst,i2c-hid.ko.zst} absent from initramfs
> >> >> - drivers/i2c/busses/{i2c-designware-core.ko.zst,i2c-designware-platform.ko.zst,i2c-i801.ko.zst} absent from initramfs
> >> >> - drivers/i2c/{i2c-mux.ko.zst,i2c-smbus.ko.zst} absent from initramfs
> >> >>
> >> >> Result: The touchpad works, but there are still IRQ #27 messages:
> >> >
> >> > And the touchpad is working fine after boot too?
> >>
> >> Yep, the touchpad seems to work fine in my desktop environment after booting and logging in.
> >
> > Can you do one more experiment?
> >
> > Add "modprobe.blacklist=idma64" in the command line too (keep everything
> > else as they are now). Does the touchpad still work and do you still get
> > the warning? Please share full dmesg.
>
> Test 1 - modprobe.blacklist=idma64
>
> The IRQ warning is present and the touchpad still works, but I think that's because the idma64 module is still loaded (the full log is attached):
>
> intel-lpss 0000:00:15.0: enabling device (0004 -> 0006)
> idma64 idma64.0: Found Intel integrated DMA 64-bit
> intel-lpss 0000:00:15.3: enabling device (0004 -> 0006)
> idma64 idma64.1: Found Intel integrated DMA 64-bit
Okay can you set CONFIG_INTEL_IDMA64=n in .config? That should prevent it
from loading. Keep the rest as it was.
next prev parent reply other threads:[~2026-01-27 10:19 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 [this message]
2026-01-27 10:56 ` correctmost
2026-01-27 14:43 ` Mika Westerberg
2026-01-27 15:09 ` Andy Shevchenko
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=20260127101912.GJ2275908@black.igk.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=cmlists@sent.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox