Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Chuanhong Guo" <gch981213@gmail.com>
Cc: linux-watchdog@vger.kernel.org, conor+dt@kernel.org,
	robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: reset: mediatek: add MT7629 TOPRGU reset indices
Date: Sat, 26 Sep 2026 11:22:17 +0000	[thread overview]
Message-ID: <20260926112217.A8EEE1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260926-b4-mt7629-toprgu-v1-1-c124bf9ac273@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: watchdog: mediatek: missing #reset-cells constraint
--

commit 8696685eaee46e4451438ad7ac853addff28818b
Author: Chuanhong Guo <gch981213@gmail.com>

dt-bindings: reset: mediatek: add MT7629 TOPRGU reset indices

This commit defines all seven reset IDs documented in the MT7629 TOPRGU
SWSYSRST register. It uses their register bit positions as the reset IDs.

> diff --git a/include/dt-bindings/reset/mt7629-resets.h b/include/dt-bindings/reset/mt7629-resets.h
> index 6bb85734f68d8..828919eee2982 100644
> --- a/include/dt-bindings/reset/mt7629-resets.h
> +++ b/include/dt-bindings/reset/mt7629-resets.h
> @@ -53,6 +53,15 @@
>  #define MT7629_PCIE0_USER_RST			30
>  #define MT7629_PCIE0_PIPE_RST			31
>  
> +/* TOPRGU resets */
> +#define MT7629_TOPRGU_INFRA_SW_RST		0
> +#define MT7629_TOPRGU_ETHDMA_SW_RST		1
> +#define MT7629_TOPRGU_DDRPHY_SW_RST		6
> +#define MT7629_TOPRGU_INFRA_AO_SW_RST		8
> +#define MT7629_TOPRGU_CONN_SW_RST		9
> +#define MT7629_TOPRGU_APMIXED_SW_RST		10
> +#define MT7629_TOPRGU_CONN_MCU_SW_RST		12

[Severity: Low]
Since this patch introduces reset provider capabilities for MT7629, does
Documentation/devicetree/bindings/watchdog/mediatek,mtk-wdt.yaml also need
to be updated in this commit to require #reset-cells for mediatek,mt7629-wdt?

Incomplete device tree nodes lacking the #reset-cells property for the MT7629
watchdog will silently pass schema validation, violating the subsystem rule
that providers must enforce their required properties.

I note this is corrected later in Patch 3 of the series so there is no
runtime impact, but static validation via dt_binding_check will be incomplete
at this specific commit.

> +
>  /* SSUSB Subsystem resets */
>  #define MT7629_SSUSB_PHY_PWR_RST		3
>  #define MT7629_SSUSB_MAC_PWR_RST		4

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260926-b4-mt7629-toprgu-v1-0-c124bf9ac273@gmail.com?part=1

  reply	other threads:[~2026-09-26 11:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-26 11:13 [PATCH 0/3] Add MT7629 TOPRGU reset support Chuanhong Guo
2026-09-26 11:13 ` [PATCH 1/3] dt-bindings: reset: mediatek: add MT7629 TOPRGU reset indices Chuanhong Guo
2026-09-26 11:22   ` sashiko-bot [this message]
2026-09-29  8:44   ` Krzysztof Kozlowski
2026-10-01  3:44     ` Chuanhong Guo
2026-10-01  5:33       ` Krzysztof Kozlowski
2026-09-26 11:14 ` [PATCH 2/3] watchdog: mediatek: add MT7629 reset controller support Chuanhong Guo
2026-09-26 11:14 ` [PATCH 3/3] ARM: dts: mediatek: expose the MT7629 TOPRGU reset controller Chuanhong Guo

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=20260926112217.A8EEE1F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gch981213@gmail.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