Linux Watchdog driver development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Komal Bajaj" <komal.bajaj@oss.qualcomm.com>
Cc: robh@kernel.org, conor+dt@kernel.org,
	linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: sm8750: Add watchdog node
Date: Tue, 29 Sep 2026 10:39:12 +0000	[thread overview]
Message-ID: <20260929103912.C22291F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260929-sm8750-watchdog-v1-2-ea06d5dc7e54@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt: incorrect node ordering in sm8750.dtsi
--

commit 807aba78b66c219c014d5a42b4b7964dbeb6b207
Author: Komal Bajaj <komal.bajaj@oss.qualcomm.com>

arm64: dts: qcom: sm8750: Add watchdog node
    
This commit adds a device tree node for the watchdog on the SM8750 SoC.

> diff --git a/arch/arm64/boot/dts/qcom/sm8750.dtsi b/arch/arm64/boot/dts/qcom/sm8750.dtsi
> index 8ed5fa4d24fcd..53125e5dc4cca 100644
> --- a/arch/arm64/boot/dts/qcom/sm8750.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm8750.dtsi
> @@ -6006,6 +6006,13 @@ cpucp_mbox: mailbox@16430000 {
>  			#mbox-cells = <1>;
>  		};
>  
> +		watchdog@16410000 {
> +			compatible = "qcom,apss-wdt-sm8750", "qcom,kpss-wdt";
> +			reg = <0x0 0x16410000 0x0 0x1000>;
> +			clocks = <&sleep_clk>;
> +			interrupts = <GIC_SPI 0 IRQ_TYPE_EDGE_RISING>;
> +		};
> +

[Severity: Low]
Does this placement break the ascending unit-address order convention for
Device Tree files?

The new watchdog@16410000 node is being placed immediately after the
mailbox@16430000 node. Should this node be moved above the mailbox node to
keep the children sorted numerically by their unit address?

>  		apps_rsc: rsc@16500000 {
>  			compatible = "qcom,rpmh-rsc";
>  			reg = <0x0 0x16500000 0x0 0x10000>,

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260929-sm8750-watchdog-v1-0-ea06d5dc7e54@oss.qualcomm.com?part=2

  reply	other threads:[~2026-09-29 10:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29 10:31 [PATCH 0/2] arm64: dts: qcom: sm8750: Add watchdog support Komal Bajaj
2026-09-29 10:31 ` [PATCH 1/2] dt-bindings: watchdog: qcom-wdt: Document SM8750 watchdog Komal Bajaj
2026-09-30 11:43   ` Krzysztof Kozlowski
2026-09-29 10:31 ` [PATCH 2/2] arm64: dts: qcom: sm8750: Add watchdog node Komal Bajaj
2026-09-29 10:39   ` sashiko-bot [this message]
2026-09-30 12:35     ` Komal Bajaj
2026-09-30 12:01   ` Konrad Dybcio

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