From: Baolu Lu <baolu.lu@linux.intel.com>
To: "Aditya Garg" <gargaditya08@live.com>,
"Berkel Jörg" <joerg.berkel@bfh.ch>,
linux-input@vger.kernel.org
Cc: dmitry.torokhov@gmail.com, stable@vger.kernel.org,
regressions@lists.linux.dev, linux-spi@vger.kernel.org,
lukas@wunner.de, David Woodhouse <dwmw2@infradead.org>,
iommu@lists.linux.dev, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: [REGRESSION] applespi from 6.12 onwards
Date: Thu, 8 May 2025 10:15:31 +0800 [thread overview]
Message-ID: <122a1f90-ddd9-4e74-96d1-57e21e580ae2@linux.intel.com> (raw)
In-Reply-To: <PN3PR01MB9597D8E327CC7910673849D3B888A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM>
On 5/8/25 01:07, Aditya Garg wrote:
> Keyboard and touchpad stopped working on several Apple Macbooks from the year 2017 using kernel 6.12.xx . Until now I could only find this discussion affirming the bug on Debian and Fedora:https://github.com/Dunedan/mbp-2016-linux/issues/202
>
> On siduction I also tried the more recent kernels 6.14.5 and mainline 6.15-rc4 (from Ubuntu) and the issue persisted with my testdevice MacBookPro14,1 -- see the relevant output:
>
> kernel: platform pxa2xx-spi.3: Adding to iommu group 20
> kernel: input: Apple SPI Keyboard as /devices/pci0000:00/0000:00:1e.3/pxa2xx-spi.3/spi_master/spi2/spi-APP000D:00/
> input/input0
> kernel: DMAR: DRHD: handling fault status reg 3
> kernel: DMAR: [DMA Read NO_PASID] Request device [00:1e.3] fault addr 0xffffa000 [fault reason 0x06] PTE Read access is not set
> kernel: DMAR: DRHD: handling fault status reg 3
> kernel: DMAR: [DMA Read NO_PASID] Request device [00:1e.3] fault addr 0xffffa000 [fault reason 0x06] PTE Read access is not set
> kernel: applespispi-APP000D:00: Error writing to device: 01 0e 00 00
> kernel: DMAR: DRHD: handling fault status reg 3
> kernel: DMAR: [DMA Read NO_PASID] Request device [00:1e.3] fault addr 0xffffa000 [fault reason 0x06] PTE Read access is not set
> kernel: DMAR: DRHD: handling fault status reg 3
> kernel: applespispi-APP000D:00: Error writing to device: 01 0e 00 00
It appears that all DMA faults are related to a fixed address,
0xffffa000. Is this address something special?
Also what does below message mean from a SPI driver's perspective?
"applespispi-APP000D:00: Error writing to device: 01 0e 00 00"
I am asking this because the IOMMU fault messages are about DMA Reads
(device raised memory read), while above message complains failing to
write to device.
Thanks,
baolu
next prev parent reply other threads:[~2025-05-08 2:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 7:18 [REGRESSION] applespi from 6.12 onwards Berkel Jörg
2025-05-07 16:31 ` Aditya Garg
2025-05-07 20:24 ` Berkel Jörg
2025-05-07 17:07 ` Aditya Garg
2025-05-08 2:15 ` Baolu Lu [this message]
2025-05-08 6:22 ` Dmitry Torokhov
2025-05-08 11:00 ` Aditya Garg
2025-05-08 11:29 ` Robin Murphy
2025-05-08 12:54 ` Aditya Garg
2025-05-09 15:23 ` Berkel Jörg
2025-05-10 9:57 ` Aditya Garg
2025-05-11 13:31 ` kobarity
2025-05-12 5:12 ` Baolu Lu
2025-05-12 12:16 ` kobarity
2025-05-13 1:37 ` Baolu Lu
2025-05-13 12:08 ` kobarity
2025-05-14 3:39 ` Baolu Lu
2025-05-09 2:47 ` Baolu Lu
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=122a1f90-ddd9-4e74-96d1-57e21e580ae2@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=gargaditya08@live.com \
--cc=iommu@lists.linux.dev \
--cc=joerg.berkel@bfh.ch \
--cc=joro@8bytes.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=regressions@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=stable@vger.kernel.org \
--cc=will@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).