From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Rob Clark <robin.clark@oss.qualcomm.com>,
Dmitry Baryshkov <lumag@kernel.org>,
freedreno@lists.freedesktop.org,
Akhil P Oommen <akhilpo@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: purwa: Fix GPU IOMMU property
Date: Thu, 2 Jul 2026 18:40:23 -0500 [thread overview]
Message-ID: <178303563649.359079.274555099812261712.b4-ty@kernel.org> (raw)
In-Reply-To: <20260410-purwa-gpu-dt-fix-v1-1-4637892156cf@oss.qualcomm.com>
On Fri, 10 Apr 2026 02:38:51 +0530, Akhil P Oommen wrote:
> Purwa's GPU does not support SID 1, which is typically used for
> LPAC-related traffic. Remove SID 1 from the GPU node's iommus property to
> accurately describe the hardware. This fixes the splat below, seen with
> some versions of Gunyah hypervisor:
>
> Internal error: synchronous external abort: 0000000096000010 [#1] SMP
> CPU: 0 UID: 0 PID: 80 Comm: kworker/u33:2 Tainted: G M
> Tainted: [M]=MACHINE_CHECK
> Hardware name: Qualcomm Technologies, Inc. Purwa IoT EVK (DT)
> Workqueue: events_unbound deferred_probe_work_func
> pstate: 21400005 (nzCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--)
> pc : arm_smmu_write_s2cr+0x9c/0xbc
> lr : arm_smmu_master_install_s2crs+0x78/0xa4
> sp : ffff80008039b570
> x29: ffff80008039b570 x28: 0000000000000000 x27: ffffaddd62f1ab78
> x26: ffff00080a4ff280 x25: 0000000000000018 x24: ffff00080b896480
> x23: ffff00080ba9b7a0 x22: ffff00080bb05160 x21: 0000000000000000
> x20: 0000000000000000 x19: 0000000000000001 x18: 00000000ffffffff
> x17: 0000000000000000 x16: 0000000000000000 x15: ffff80008039b1d0
> x14: ffff80010039b37d x13: 00746c7561662d74 x12: 0000000000000000
> x11: ffff00080b7fbd98 x10: ffffffffffffffc0 x9 : ffffffffffffffff
> x8 : 0000000000000228 x7 : 0000000000000e87 x6 : 0000000000000000
> x5 : 0000000000000000 x4 : ffff00080a4ff280 x3 : 0000000000000000
> x2 : ffff800082a40c04 x1 : 0000000000000000 x0 : ffff800082a40000
> Call trace:
> arm_smmu_write_s2cr+0x9c/0xbc (P)
> arm_smmu_master_install_s2crs+0x78/0xa4
> arm_smmu_attach_dev+0xb0/0x1d8
> __iommu_device_set_domain+0x84/0x11c
> __iommu_group_set_domain_internal+0x60/0x120
> __iommu_attach_group+0x88/0x9c
> iommu_attach_device+0x6c/0xa0
> msm_iommu_new.part.0+0x84/0xe4 [msm]
> msm_iommu_gpu_new+0x3c/0x104 [msm]
> adreno_iommu_create_vm+0x24/0xc8 [msm]
> a6xx_create_vm+0x48/0x78 [msm]
> msm_gpu_init+0x2d8/0x508 [msm]
> adreno_gpu_init+0x208/0x324 [msm]
> a6xx_gpu_init+0x604/0x8cc [msm]
> adreno_bind+0xb4/0x124 [msm]
> component_bind_all+0x114/0x23c
> msm_drm_init+0x1b0/0x1ec [msm]
> msm_drm_bind+0x30/0x3c [msm]
> try_to_bring_up_aggregate_device+0x164/0x1d0
> __component_add+0xa4/0x16c
> component_add+0x14/0x20
> msm_dp_display_probe_tail+0x4c/0xac [msm]
> msm_dp_auxbus_done_probe+0x14/0x20 [msm]
> dp_aux_ep_probe+0x4c/0xf4 [drm_dp_aux_bus]
> really_probe+0xbc/0x29c
> __driver_probe_device+0x78/0x12c
> driver_probe_device+0x3c/0x15c
> __device_attach_driver+0xb8/0x134
> bus_for_each_drv+0x88/0xe8
> __device_attach+0xa0/0x190
> device_initial_probe+0x50/0x54
> bus_probe_device+0x38/0xa4
> deferred_probe_work_func+0x88/0xc0
> process_one_work+0x148/0x28c
> worker_thread+0x2cc/0x3d4
> kthread+0x12c/0x204
> ret_from_fork+0x10/0x20
> ---[ end trace 0000000000000000 ]---
>
> [...]
Applied, thanks!
[1/1] arm64: dts: qcom: purwa: Fix GPU IOMMU property
commit: 4cd774c1feb3f720265c512174c5c3312eca1be2
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2026-07-02 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 21:08 Akhil P Oommen
2026-04-10 8:37 ` Konrad Dybcio
2026-07-02 23:40 ` Bjorn Andersson [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=178303563649.359079.274555099812261712.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=akhilpo@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=freedreno@lists.freedesktop.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=robh@kernel.org \
--cc=robin.clark@oss.qualcomm.com \
/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
all inboxes | Powered by JetHome®