From: sashiko-bot@kernel.org
To: "Erikas Bitovtas" <xerikasxx@gmail.com>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH RESEND v3 3/3] arm64: dts: qcom: sm7125-samsung: add initial device tree
Date: Thu, 10 Sep 2026 12:40:56 +0000 [thread overview]
Message-ID: <20260910124057.6E0481F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260910-sm7125-samsung-v3-3-c467bea0fb9c@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The `rmtfs_mem` and `framebuffer` nodes violate unit address conventions, causing dtc compiler warnings.
--
commit f4aab33141cc83eeb5caf4d1bd15dc706240103e
Author: Erikas Bitovtas <xerikasxx@gmail.com>
arm64: dts: qcom: sm7125-samsung: add initial device tree
Samsung Galaxy A52/A72 are devices released on atoll (SM7125) platform
in 2021. Add initial device tree for SM7125 Samsung platform with
support for various peripherals.
> diff --git a/arch/arm64/boot/dts/qcom/sm7125-samsung-a52q.dts b/arch/arm64/boot/dts/qcom/sm7125-samsung-a52q.dts
> index 0000000000000..ecba5be8164ea
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/sm7125-samsung-a52q.dts
[ ... ]
> +&rmtfs_mem {
> + reg = <0x0 0xf4f00000 0x0 0x202000>;
> +};
[Severity: Low]
Does this reg assignment cause a dtc compiler warning? The reg property is
assigned here without updating the node name to include the unit address
@f4f00000.
> diff --git a/arch/arm64/boot/dts/qcom/sm7125-samsung-common.dtsi b/arch/arm64/boot/dts/qcom/sm7125-samsung-common.dtsi
> index 0000000000000..b8863e111bc4f
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/sm7125-samsung-common.dtsi
[ ... ]
> + ranges;
> +
> + framebuffer@9c000000 {
> + compatible = "simple-framebuffer";
> + memory-region = <&cont_splash_mem>;
[Severity: Low]
Should this node name have a unit address? The unit address @9c000000 is
present in the node name without a corresponding reg property, which usually
triggers a unit_address_vs_reg warning from the device tree compiler.
> + width = <1080>;
[ ... ]
> + pstore_mem: ramoops@b4600000 {
> + compatible = "ramoops";
> + reg = <0x0 0xb4600000 0x0 0x100000>;
> + record-size = <0x40000>;
> + console-size = <0x40000>;
> + ftrace-size = <0x40000>;
> + pmsg-size = <0x40000>;
> + };
> +
> + rmtfs_mem: memory {
> + compatible = "qcom,rmtfs-mem";
> + qcom,use-guard-pages;
[Severity: Low]
Should this node name include a unit address? This node is defined here as
memory without a unit address, but it receives a reg property in the
board-specific DTS files. This typically generates a unit_address_vs_reg dtc
warning during the build.
> + no-map;
> +
> + qcom,client-id = <1>;
> + qcom,vmid = <QCOM_SCM_VMID_MSS_MSA>;
> + };
> + };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260910-sm7125-samsung-v3-0-c467bea0fb9c@gmail.com?part=3
prev parent reply other threads:[~2026-09-10 12:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 12:27 [PATCH RESEND v3 0/3] arm64: dts: qcom: sm7125-samsung: add initial device tree for SM7125 Samsung platform Erikas Bitovtas
2026-09-10 12:27 ` [PATCH RESEND v3 1/3] dt-bindings: arm: qcom: Document Samsung Galaxy A52/A72 Erikas Bitovtas
2026-09-10 12:27 ` [PATCH RESEND v3 2/3] firmware: qcom: tzmem: disable SHM bridge for SM7125 platform Erikas Bitovtas
2026-09-10 12:27 ` [PATCH RESEND v3 3/3] arm64: dts: qcom: sm7125-samsung: add initial device tree Erikas Bitovtas
2026-09-10 12:40 ` 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=20260910124057.6E0481F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=xerikasxx@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