From: Linghui Wu <linghui.wu@oss.qualcomm.com>
To: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Abel Vesa <abelvesa@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bibek Kumar Patro <bibek.patro@oss.qualcomm.com>,
Komal Bajaj <komal.bajaj@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Linghui Wu <linghui.wu@oss.qualcomm.com>
Subject: [PATCH] arm64: dts: qcom: shikra: map WCSS firmware stream in EL2
Date: Wed, 28 Oct 2026 18:42:26 +0800 [thread overview]
Message-ID: <20261028104226.1075335-1-linghui.wu@oss.qualcomm.com> (raw)
In-Reply-To: <20260918-shikra-el2-v1-1-07bb072baa31@oss.qualcomm.com>
When Shikra runs Linux directly at EL2, the hypervisor does not
configure the IOMMU stream used by the WCSS firmware. Without a
wifi-firmware child node, ath10k assumes that TrustZone manages this
stream and skips creating the firmware IOMMU domain and identity
mapping the WLAN MSA region.
The resulting WCSS access to the WLAN MSA causes a non-secure SMMU
global fault for stream ID 0x1a2, followed by a system NoC error and
secure watchdog reset.
Describe the WCSS firmware stream so ath10k can attach it to a firmware
IOMMU domain and map the WLAN MSA for firmware access.
Tested on Shikra KVM/EL2. Wi-Fi initializes normally and the SMMU/NoC
fault and secure watchdog reset are no longer observed.
Signed-off-by: Linghui Wu <linghui.wu@oss.qualcomm.com>
---
arch/arm64/boot/dts/qcom/shikra-el2.dtso | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/shikra-el2.dtso b/arch/arm64/boot/dts/qcom/shikra-el2.dtso
index d2f3186bd47d..a0f7c4a635ad 100644
--- a/arch/arm64/boot/dts/qcom/shikra-el2.dtso
+++ b/arch/arm64/boot/dts/qcom/shikra-el2.dtso
@@ -21,3 +21,9 @@ &remoteproc_lpaicp {
<&apps_smmu 0x0366 0x0000>,
<&apps_smmu 0x00e7 0x0000>;
};
+
+&wifi {
+ wifi-firmware {
+ iommus = <&apps_smmu 0x01a2 0x0001>;
+ };
+};
--
2.43.0
next prev parent reply other threads:[~2026-10-28 10:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 12:34 [PATCH] arm64: dts: qcom: shikra: Add EL2 overlay for remoteproc SMMU mappings Komal Bajaj
2026-09-21 8:11 ` Abel Vesa
2026-09-30 12:02 ` Komal Bajaj
2026-10-28 10:42 ` Linghui Wu [this message]
2026-10-28 11:15 ` [PATCH] arm64: dts: qcom: shikra: map WCSS firmware stream in EL2 Linghui Wu
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=20261028104226.1075335-1-linghui.wu@oss.qualcomm.com \
--to=linghui.wu@oss.qualcomm.com \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=bibek.patro@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=komal.bajaj@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®