Re: [PATCH] arm64: dts: qcom: shikra: Mark RPM message RAM as no-memory-wc
From: Mukesh Ojha
Date: Tue Nov 17 2026 - 11:20:20 EST
On Tue, Nov 17, 2026 at 01:35:50PM +0530, Vishnu Santhosh wrote:
> The RPM message RAM is shared with other subsystems, and parts of it
> are not accessible to the APSS. It is expected to be mapped as Device
> memory.
>
> The "mmio-sram" compatible makes the SRAM driver map the region as
> write-combined (Normal Non-cacheable) memory instead, which allows
> speculative reads into the protected parts and results in XPU
> violations.
>
> Add no-memory-wc so the region is mapped as Device memory.
>
> Fixes: 66664b5701da ("arm64: dts: qcom: Introduce Shikra SoC base dtsi")
> Signed-off-by: Vishnu Santhosh <vishnu.santhosh@xxxxxxxxxxxxxxxx>
Why only for Shikra ?
> ---
> A similar issue was fixed for the Tegra SYSRAM in commit 61192a9d8a63
> ("arm64: tegra: Mark BPMP channels as no-memory-wc"):
> https://lore.kernel.org/all/20220622132300.1746201-2-cyndis@xxxxxxxx/
> ---
> arch/arm64/boot/dts/qcom/shikra.dtsi | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/shikra.dtsi b/arch/arm64/boot/dts/qcom/shikra.dtsi
> index 2623e139196f6398c57b616879a37f84b83d59ac..597aaf490519e605d50e24c090bbfb1e47b1f28c 100644
> --- a/arch/arm64/boot/dts/qcom/shikra.dtsi
> +++ b/arch/arm64/boot/dts/qcom/shikra.dtsi
> @@ -1347,6 +1347,8 @@ rpm_msg_ram: sram@45f0000 {
> compatible = "qcom,rpm-msg-ram", "mmio-sram";
> reg = <0x0 0x045f0000 0x0 0x7000>;
>
> + no-memory-wc;
> +
> #address-cells = <1>;
> #size-cells = <1>;
> ranges = <0x0 0x0 0x045f0000 0x7000>;
>
> ---
> base-commit: 666539eecdf4db623f5e3c3e55cf9f2dfad24aa4
> change-id: 20261117-rpm-memory-non-wc-c93a6ff3e432
>
> Best regards,
> --
> Vishnu Santhosh <vishnu.santhosh@xxxxxxxxxxxxxxxx>
>
--
-Mukesh Ojha