From: sashiko-bot@kernel.org
To: "David Heidelberg" <david@ixit.cz>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 2/2] arm64: dts: qcom: add Xiaomi Mi 8 (dipper)
Date: Tue, 15 Sep 2026 14:45:09 +0000 [thread overview]
Message-ID: <20260915144510.223A61F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260915-dipper-v2-2-cbade54919ee@ixit.cz>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] arm64: dts: qcom: missing TrustZone reserved memory redefinition
--
commit 02ae202c9e4a6dda959a1b0bd255a44620dacac8
Author: David Heidelberg <david@ixit.cz>
arm64: dts: qcom: add Xiaomi Mi 8 (dipper)
Initial submission for one member of the prime Xiaomi Mi 8 family.
Mi 8 Pro (equuleus) and Mi 8 Explorer (ursa) are nearly identical.
Known differences are battery capacity and fingerprint sensor placement.
> diff --git a/arch/arm64/boot/dts/qcom/sdm845-xiaomi-dipper-common.dtsi b/arch/arm64/boot/dts/qcom/sdm845-xiaomi-dipper-common.dtsi
> new file mode 100644
> index 0000000000000..eb4243e7f2c07
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/sdm845-xiaomi-dipper-common.dtsi
> @@ -0,0 +1,607 @@
[ ... ]
> +/delete-node/ &slpi_mem;
> +/delete-node/ &spss_mem;
> +/delete-node/ &tz_mem;
> +/delete-node/ &venus_mem;
> +/delete-node/ &wlan_msa_mem;
[ ... ]
> + reserved-memory {
> + /*
> + * It seems like reserving the old rmtfs_mem region is
> + * also needed to prevent random crashes
> + */
> + old-rmtfs@88f00000 {
> + reg = <0 0x88f00000 0 0x200000>;
> + no-map;
> + };
> +
[Severity: High]
Does this code accidentally leave TrustZone memory unreserved?
By explicitly deleting the default tz_mem node with /delete-node/ &tz_mem; at
the top of the file but failing to redefine it here in the reserved-memory
block with device-specific sizes, Linux will map the TrustZone memory space
as general-purpose System RAM.
When the buddy allocator hands out pages from this unreserved TrustZone
memory range, the system will experience random hard crashes (Synchronous
Aborts or Secure Watchdog Bites/XPU violations) when the kernel allocates
and accesses it.
The workaround of reserving old-rmtfs at 0x88f00000 to mask random crashes
appears to be a direct symptom of this missing reservation, since that memory
region falls within the unreserved TrustZone space.
> + adsp_mem: adsp@8c500000 {
> + reg = <0 0x8c500000 0 0x1e00000>;
> + no-map;
> + };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260915-dipper-v2-0-cbade54919ee@ixit.cz?part=2
prev parent reply other threads:[~2026-09-15 14:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 14:32 [PATCH v2 0/2] Introduce support for Xiaomi Mi 8 David Heidelberg via B4 Relay
2026-09-15 14:32 ` David Heidelberg
2026-09-15 14:32 ` [PATCH v2 1/2] dt-bindings: arm: qcom: Add Xiaomi Mi 8 family compatibles David Heidelberg via B4 Relay
2026-09-15 14:32 ` David Heidelberg
2026-09-17 10:21 ` Krzysztof Kozlowski
2026-09-17 10:25 ` David Heidelberg
2026-09-18 8:40 ` Krzysztof Kozlowski
2026-09-15 14:32 ` [PATCH v2 2/2] arm64: dts: qcom: add Xiaomi Mi 8 (dipper) David Heidelberg via B4 Relay
2026-09-15 14:32 ` David Heidelberg
2026-09-15 14:45 ` sashiko-bot [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=20260915144510.223A61F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.