Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Kathiravan Thirumoorthy" <kathiravan.thirumoorthy@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 4/5] arm64: dts: qcom: ipq9574: add support to get watchdog bootstatus from IMEM
Date: Thu, 01 Oct 2026 15:18:33 +0000	[thread overview]
Message-ID: <20261001151834.31DED1F00898@smtp.kernel.org> (raw)
In-Reply-To: <20261001-imem_restart_reason-v1-4-79f516906010@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dts: unit address vs reg mismatch in restartreason-sram node
--

commit 4b33adc218a1891c7f1ef39e3eac2b1ba37f9136
Author: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>

arm64: dts: qcom: ipq9574: add support to get watchdog bootstatus from IMEM

This commit adds the "sram" property to the watchdog device node to enable
retrieval of the system restart reason from IMEM, and creates the required
SRAM child node to map the restart reason memory region.

> diff --git a/arch/arm64/boot/dts/qcom/ipq9574.dtsi b/arch/arm64/boot/dts/qcom/ipq9574.dtsi
> index f7cc6f274ca91..2156911876cca 100644
> --- a/arch/arm64/boot/dts/qcom/ipq9574.dtsi
> +++ b/arch/arm64/boot/dts/qcom/ipq9574.dtsi
> @@ -760,8 +760,16 @@ usb_0_qmpphy: phy@7d000 {
>  		sram@8600000 {
>  			compatible = "qcom,ipq9574-imem", "mmio-sram";
>  			reg = <0x08600000 0x8000>;
> +			ranges = <0 0x08600000 0x8000>;
>  
>  			no-memory-wc;
> +
> +			#address-cells = <1>;
> +			#size-cells = <1>;
> +
> +			restart_reason: restartreason-sram@7b0 {
> +				reg = <0x7a4 0x4>;
> +			};

[Severity: Low]
Does the unit address in the node name (@7b0) need to match the first address
specified in the reg property (0x7a4)? A mismatch here typically triggers a
unit_address_vs_reg warning from the device tree compiler during the build.

Should the node name be updated to restartreason-sram@7a4, or does the reg
property need to be corrected to 0x7b0?

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261001-imem_restart_reason-v1-0-79f516906010@oss.qualcomm.com?part=4

  reply	other threads:[~2026-10-01 15:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 15:11 [PATCH 0/5] Add support for reporting boot status on Qualcomm IPQ9574 and IPQ5332 Kathiravan Thirumoorthy
2026-10-01 15:11 ` [PATCH 1/5] dt-bindings: sram: Document IMEM found in Qualcomm's " Kathiravan Thirumoorthy
2026-10-01 15:18   ` sashiko-bot
2026-10-02  9:41   ` Krzysztof Kozlowski
2026-10-02 13:03     ` Kathiravan Thirumoorthy
2026-10-01 15:11 ` [PATCH 2/5] arm64: dts: qcom: ipq9574: add the IMEM node Kathiravan Thirumoorthy
2026-10-01 15:11 ` [PATCH 3/5] arm64: dts: qcom: ipq5332: " Kathiravan Thirumoorthy
2026-10-01 15:20   ` sashiko-bot
2026-10-01 15:11 ` [PATCH 4/5] arm64: dts: qcom: ipq9574: add support to get watchdog bootstatus from IMEM Kathiravan Thirumoorthy
2026-10-01 15:18   ` sashiko-bot [this message]
2026-10-01 15:11 ` [PATCH 5/5] arm64: dts: qcom: ipq5332: " Kathiravan Thirumoorthy
2026-10-01 15:16   ` sashiko-bot

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=20261001151834.31DED1F00898@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kathiravan.thirumoorthy@oss.qualcomm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox