Linux Watchdog driver development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Zakariya Hadrami" <zkh@mailbox.org>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org,
	linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v5 3/4] ARM: dts: mediatek: mt8127: Add watchdog support
Date: Thu, 10 Sep 2026 13:36:04 +0000	[thread overview]
Message-ID: <20260910133604.A1E861F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260910-mt8127-amazon-ford-basic-v5-3-3cb9eeaffd5c@mailbox.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The watchdog node is disabled by default in the SoC .dtsi, which is a device tree anti-pattern for internal IPs without board-specific dependencies.
--

commit 00ce16ebfa121cfaa7d2f6798bebf7e7aabf4c90
Author: Zakariya Hadrami <zkh@mailbox.org>

ARM: dts: mediatek: mt8127: Add watchdog support

This commit adds the watchdog node for MT8127 and explicitly disables it by
default in the SoC dtsi.

> diff --git a/arch/arm/boot/dts/mediatek/mt8127.dtsi b/arch/arm/boot/dts/mediatek/mt8127.dtsi
> index bd61ec7e70c0c..9bdf55d2da479 100644
> --- a/arch/arm/boot/dts/mediatek/mt8127.dtsi
> +++ b/arch/arm/boot/dts/mediatek/mt8127.dtsi
> @@ -99,6 +99,13 @@ soc {
>  		compatible = "simple-bus";
>  		ranges;
>  
> +		watchdog: watchdog@10007000 {
> +			compatible = "mediatek,mt8127-wdt", "mediatek,mt6589-wdt";
> +			reg = <0 0x10007000 0 0x100>;
> +			interrupts = <GIC_SPI 88 IRQ_TYPE_LEVEL_LOW>;
> +			status = "disabled";

[Severity: Low]
Is it necessary to disable this watchdog by default?

The watchdog timer is a core internal IP of the SoC that does not require
board-specific configuration. Standard device tree practice is to omit
status = "disabled" for internal IPs in the SoC .dtsi file.

The commit message states "disable it by default as it was not present
initially". Will this require every board file inheriting this .dtsi to
redundantly set status = "okay"?

> +		};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260910-mt8127-amazon-ford-basic-v5-0-3cb9eeaffd5c@mailbox.org?part=3

  reply	other threads:[~2026-09-10 13:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10 13:29 [PATCH v5 0/4] ARM: Basic support for Amazon ford tablet (MT8127) Zakariya Hadrami via B4 Relay
2026-09-10 13:29 ` [PATCH v5 1/4] dt-bindings: watchdog: mediatek: Add MT8127 Zakariya Hadrami via B4 Relay
2026-09-11  3:37   ` Guenter Roeck
2026-09-10 13:29 ` [PATCH v5 2/4] dt-bindings: arm: mediatek: Add MT8127 Amazon ford Zakariya Hadrami via B4 Relay
2026-09-10 13:29 ` [PATCH v5 3/4] ARM: dts: mediatek: mt8127: Add watchdog support Zakariya Hadrami via B4 Relay
2026-09-10 13:36   ` sashiko-bot [this message]
2026-09-10 15:43     ` Zakariya Hadrami
2026-09-10 13:29 ` [PATCH v5 4/4] ARM: dts: mediatek: Add basic support for Amazon ford board Zakariya Hadrami via B4 Relay
2026-09-10 14:41 ` (subset) [PATCH v5 0/4] ARM: Basic support for Amazon ford tablet (MT8127) AngeloGioacchino Del Regno

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=20260910133604.A1E861F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=zkh@mailbox.org \
    /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