From: sashiko-bot@kernel.org
To: "Stanislav Zaikin" <zstaseg@gmail.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org,
krzk+dt@kernel.org
Subject: Re: [PATCH v6 2/3] arm64: dts: qcom: Add Xiaomi 12 Lite 5G (taoyao) DTS
Date: Sat, 16 May 2026 09:36:17 +0000 [thread overview]
Message-ID: <20260516093618.787C1C2BCF5@smtp.kernel.org> (raw)
In-Reply-To: <20260516090853.2873223-3-zstaseg@gmail.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The ramoops memory region is entirely consumed by `pmsg-size`, silently breaking kernel crash dumps.
- [Low] Device Tree unit address mismatch in the `rmtfs_mem` reserved memory node.
--
commit cc4a7cf1d691d4d94cb9b845a5a49075f69a93ff
Author: Stanislav Zaikin <zstaseg@gmail.com>
arm64: dts: qcom: Add Xiaomi 12 Lite 5G (taoyao) DTS
This commit adds device tree support for the Xiaomi 12 Lite 5G handset,
enabling features such as display, touchscreen, UFS, power/volume buttons,
and remoteprocs.
> diff --git a/arch/arm64/boot/dts/qcom/sm7325-xiaomi-taoyao.dts b/arch/arm64/boot/dts/qcom/sm7325-xiaomi-taoyao.dts
> new file mode 100644
> index 0000000000000..eb83da4b836e1
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/sm7325-xiaomi-taoyao.dts
[ ... ]
> + ramoops@a9000000 {
> + compatible = "ramoops";
> + reg = <0x0 0xa9000000 0x0 0x200000>;
> + pmsg-size = <0x200000>;
Does this configuration leave any room for kernel crash dumps?
The node defines a memory region of exactly 2MB, but pmsg-size consumes the
entire 0x200000 bytes. Because pmsg-size consumes all available space, zero
space remains for record-size (which defaults to 0). Will the pstore/ramoops
driver be able to store kernel dmesg during panics or oops with this setup?
> + mem-type = <2>;
> + };
[ ... ]
> + rmtfs_mem: rmtfs@ef500000 {
> + compatible = "qcom,rmtfs-mem";
> + reg = <0x0 0xe7d00000 0x0 0x280000>;
Is this unit address intentionally mismatched with the reg property?
The node is named rmtfs@ef500000, but its reg property specifies a base
address of 0xe7d00000. Can this structural syntax violation trigger a
simple_bus_reg dtc compiler warning?
> + no-map;
> +
> + qcom,client-id = <1>;
> + qcom,vmid = <QCOM_SCM_VMID_MSS_MSA>,
> + <QCOM_SCM_VMID_NAV>;
> + };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260516090853.2873223-1-zstaseg@gmail.com?part=2
next prev parent reply other threads:[~2026-05-16 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-16 9:08 [PATCH v6 0/3] Add Xiaomi 12 Lite 5G (taoyao) device tree Stanislav Zaikin
2026-05-16 9:08 ` [PATCH v6 1/3] dt-bindings: arm: qcom: Add SM7325 Xiaomi 12 Lite 5G (taoyao) Stanislav Zaikin
2026-05-16 9:08 ` [PATCH v6 2/3] arm64: dts: qcom: Add Xiaomi 12 Lite 5G (taoyao) DTS Stanislav Zaikin
2026-05-16 9:36 ` sashiko-bot [this message]
2026-05-16 9:08 ` [PATCH v6 3/3] arm64: dts: qcom: sm7325: Move common IPA properties Stanislav Zaikin
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=20260516093618.787C1C2BCF5@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=zstaseg@gmail.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