From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4E44B33D6D6; Fri, 23 Jan 2026 06:53:55 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.14 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769151239; cv=none; b=nffUHA97bWUWWsKPjQLe4svwQw5F2meUL62FFM+wY5nD8IUMFVvlcltY3EYliMVbZiu4MjsWjF+7XBypAaHibGK7hnLYPaau7j9hr6lZUyLdcutpLjqe7HgN8aN9vtZI9laax8aH0RYoESLVb4uhWUNV+MTKDXCFFGXZnXpD5OY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769151239; c=relaxed/simple; bh=42gUiI1ZqYMbUsEspGleDV/f+8xy3ciRajpf+AzMI1k=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=V82Pjn4q41mVrWDQejNUM8XTnfFLXLJs/i9SFAZ1Kl1wzeGloiEUCBl8uEhtc9gFB9awY4qI/72TWSAaDjjWJbbvwMp2uChIQnQdzBC5nkPT59XjSXxiytXXoUpCYCrC93m1bYy477OakPxRPj2ZnlpGh2Ui5dUqYQ3bjYKGG9U= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=pass smtp.mailfrom=linux.intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=ZNik+zHF; arc=none smtp.client-ip=192.198.163.14 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="ZNik+zHF" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1769151236; x=1800687236; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=42gUiI1ZqYMbUsEspGleDV/f+8xy3ciRajpf+AzMI1k=; b=ZNik+zHFV1oeSnyDtxmJDvOK2SvHJGG1fzgiCF2MsNYht3HvG7FhYMSq 1Z6NRoFP7Gsn2+dZkfHQqoULHByxMEbMgKWdFgr0UBc8ONA4C90qV7mSI sLYMQCSbM9zC6+z0oHewoVfIhN+6O0LN0V9zLownnvbMh7JP75APqCVg1 w4JZByufXKYlZF+r/DZ0dKyWUEYG042hNDGvW4SC0WI77iubzAmlV/7JO O0VtHC9IT/1ma/YWIOgVuJqYVv0eF2ZORXVV2IXQ/ld5ZLkGCaXzb4j45 myk4dSICorKMv+8aqygmnAq2hg0Zd9tj2pAXP+g96Zow4CTZa7T/mUGuO A==; X-CSE-ConnectionGUID: XT9gKCHGRQ65EtMXxAa4Aw== X-CSE-MsgGUID: cC0qo8dASbGzinfMliupaQ== X-IronPort-AV: E=McAfee;i="6800,10657,11679"; a="70462645" X-IronPort-AV: E=Sophos;i="6.21,248,1763452800"; d="scan'208";a="70462645" Received: from orviesa006.jf.intel.com ([10.64.159.146]) by fmvoesa108.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Jan 2026 22:53:54 -0800 X-CSE-ConnectionGUID: 11HnK7FxSCWEVttt57MoJw== X-CSE-MsgGUID: b8zPJSN7StCmBtbv1A3NsQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.21,247,1763452800"; d="scan'208";a="206066158" Received: from rvuia-mobl.ger.corp.intel.com (HELO localhost) ([10.245.244.112]) by orviesa006-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Jan 2026 22:53:52 -0800 Date: Fri, 23 Jan 2026 08:53:49 +0200 From: Andy Shevchenko To: correctmost Cc: Mika Westerberg , 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 Message-ID: References: <20260121135803.GM2275908@black.igk.intel.com> <20260121150256.GN2275908@black.igk.intel.com> <20260122110021.GO2275908@black.igk.intel.com> Precedence: bulk X-Mailing-List: linux-i2c@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - c/o Alberga Business Park, 6 krs, Bertel Jungin Aukio 5, 02600 Espoo On Thu, Jan 22, 2026 at 05:29:38PM -0500, correctmost wrote: > On Thu, Jan 22, 2026, at 6:00 AM, Mika Westerberg wrote: > > On Wed, Jan 21, 2026 at 05:19:17PM +0200, Andy Shevchenko wrote: > >> > Well I mean if touchpads actually worked prior this idma64 commit and now > >> > they don't isn't that a regression? > >> > >> I don't think so, because commit did the right thing and just revealed an issue > >> that was rather hidden. Reverting is not an option. > > > > I now looked at both working and non-working /proc/interrupts and when it > > is working there is no interrupt flood at all: > > > > 27: 0 0 0 0 2277 0 > > 0 0 0 0 0 0 > > IR-IO-APIC 27-fasteoi idma64.0, i2c_designware.0 > > > > This makes me think that perhaps the toucpad is powered off and that causes > > the issue until I2C HID probes and resets it. I looked at the ACPI tables > > but I did not (yet) find anything that stands out. > > > > I wonder if it was tried to put i2c-designware*.ko and i2c-hid.ko into the > > initramfs, and does work it around? I would expect so. > > I don't see an i2c-designware module loaded when my touchpad works: It's most likely built-in. This is the requirement when kernel wants to support some of the (old) Intel hardware. If you see it in `cat /proc/interrupts`, or in the output of `lspci -nk`, it's there. > $ grep -i i2c /proc/modules > i2c_i801 40960 0 - Live 0x0000000000000000 > i2c_smbus 20480 1 i2c_i801, Live 0x0000000000000000 > i2c_mux 16384 1 i2c_i801, Live 0x0000000000000000 > i2c_hid_acpi 12288 0 - Live 0x0000000000000000 > i2c_hid 45056 1 i2c_hid_acpi, Live 0x0000000000000000 > i2c_algo_bit 24576 2 xe,i915, Live 0x0000000000000000 > > I tried adding all of the following modules to my initramfs image and I still > encountered the touchpad failure: > > drivers/dma/idma64.ko.zst > drivers/hid/i2c-hid/i2c-hid-acpi.ko.zst > drivers/hid/i2c-hid/i2c-hid.ko.zst > drivers/i2c/i2c-mux.ko.zst > drivers/i2c/i2c-smbus.ko.zst > drivers/i2c/busses/i2c-i801.ko.zst > drivers/mfd/intel-lpss.ko.zst > drivers/mfd/intel-lpss-pci.ko.zst > > (The drivers/i2c/algos/i2c-algo-bit.ko.zst module was already present in > the working image, so I didn't have to add it.) -- With Best Regards, Andy Shevchenko