From: Benjamin Kelenyi <benjamin@wendy.sh>
To: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Vinayak Katoch <vinayak.katoch@oss.qualcomm.com>,
Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Christopher Obbard <chris.obbard@oss.qualcomm.com>,
Abel Vesa <abel.vesa@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Benjamin Kelenyi <benjamin@wendy.sh>
Subject: [PATCH] arm64: dts: qcom: agatti: Make the ADSP remote heap no-map
Date: Thu, 1 Oct 2026 11:52:47 +0300 [thread overview]
Message-ID: <20261001085247.1897991-1-benjamin@wendy.sh> (raw)
The ADSP remote heap is declared as a reusable CMA pool. The ADSP has no
IOMMU, so fastrpc hands the whole region to the DSP with
qcom_scm_assign_mem() when it probes, while CMA keeps lending the pool's
pages to movable allocations. Once memory runs low the kernel touches a
page the DSP now owns, and the board resets without an oops.
On an Arduino UNO Q (QRB2210, 4 GB), writing and reading back 3.5 GB
through the page cache resets the board within seconds. With fastrpc
blacklisted, or with the heap declared no-map, the same test passes
repeatedly.
Declare the heap no-map, so the kernel never uses it, as the other
platforms' remote heaps are.
Fixes: 3fbf3b85bf86 ("arm64: dts: qcom: agatti: Add memory-region for audio PD")
Link: https://lore.kernel.org/all/20260908070331.2189A1F00A3A@smtp.kernel.org/
Signed-off-by: Benjamin Kelenyi <benjamin@wendy.sh>
---
arch/arm64/boot/dts/qcom/agatti.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/qcom/agatti.dtsi b/arch/arm64/boot/dts/qcom/agatti.dtsi
index d9f4cbf..3ff97ea 100644
--- a/arch/arm64/boot/dts/qcom/agatti.dtsi
+++ b/arch/arm64/boot/dts/qcom/agatti.dtsi
@@ -385,7 +385,7 @@
adsp_rpc_remote_heap_mem: adsp-rpc-remote-heap {
compatible = "shared-dma-pool";
alloc-ranges = <0x0 0x0 0x1 0x0>;
- reusable;
+ no-map;
alignment = <0x0 0x400000>;
size = <0x0 0x800000>;
};
--
2.43.0
reply other threads:[~2026-10-01 8:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261001085247.1897991-1-benjamin@wendy.sh \
--to=benjamin@wendy.sh \
--cc=abel.vesa@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=chris.obbard@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=ekansh.gupta@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 \
--cc=vinayak.katoch@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