From: sashiko-bot@kernel.org
To: Prabhakar <prabhakar.csengg@gmail.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org,
wsa+renesas@sang-engineering.com, linux-watchdog@vger.kernel.org
Subject: Re: [PATCH RFC v2 5/9] dt-bindings: watchdog: renesas,r9a09g057-wdt: Add SYS syscon support
Date: Thu, 02 Jul 2026 12:38:34 +0000 [thread overview]
Message-ID: <20260702123836.3F6801F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260702123112.161160-6-prabhakar.mahadev-lad.rj@bp.renesas.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The deprecation warning message instructs users to pass a register offset via 'renesas,sys', contradicting the schema which restricts it to an IP instance index.
--
commit dd09e9278d1657dcf283ff0886c7ec9901f648a4
Author: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
dt-bindings: watchdog: renesas,r9a09g057-wdt: Add SYS syscon support
This commit introduces a renesas,sys phandle-array property to allow the WDT
driver to access its control register via the system controller. It also
deprecates the second reg entry in favor of this new approach.
> diff --git a/Documentation/devicetree/bindings/watchdog/renesas,r9a09g057-wdt.yaml b/Documentation/devicetree/bindings/watchdog/renesas,r9a09g057-wdt.yaml
> --- a/Documentation/devicetree/bindings/watchdog/renesas,r9a09g057-wdt.yaml
> +++ b/Documentation/devicetree/bindings/watchdog/renesas,r9a09g057-wdt.yaml
> @@ -48,6 +48,17 @@ properties:
> resets:
> maxItems: 1
>
> + renesas,sys:
> + description:
> + System controller registers control the start/stop of the WDT, and halt debug.
> + $ref: /schemas/types.yaml#/definitions/phandle-array
> + items:
> + - items:
> + - description: phandle to system controller
> + - description: watchdog IP instance index
> + minimum: 0
> + maximum: 5
> +
[ ... ]
> + else:
> + properties:
> + reg:
> + description: Deprecated. Use renesas,sys to pass the offset
> + of WDTDCR register instead.
[Severity: Low]
Is this deprecation message accurate regarding passing an offset?
Looking at the renesas,sys property definition added above, it expects a
watchdog IP instance index with a maximum value of 5, rather than a register
offset.
Could this description mislead device tree authors into providing a raw
register offset instead of an index, leading to schema validation failures?
> + minItems: 2
> + deprecated: true
>
> additionalProperties: false
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260702123112.161160-1-prabhakar.mahadev-lad.rj@bp.renesas.com?part=5
next prev parent reply other threads:[~2026-07-02 12:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 12:31 [PATCH RFC v2 0/9] Add System Controller support for RZ/T2H and RZ/N2H SoCs Prabhakar
2026-07-02 12:31 ` [PATCH RFC v2 1/9] dt-bindings: clock: renesas,cpg-mssr: Support RZ/T2H system controllers Prabhakar
2026-07-02 12:38 ` sashiko-bot
2026-07-02 12:31 ` [PATCH RFC v2 2/9] clk: renesas: r9a09g077: Add SYSC regmap support Prabhakar
2026-07-02 12:48 ` sashiko-bot
2026-07-02 12:31 ` [PATCH RFC v2 3/9] arm64: dts: renesas: r9a09g077: Add system controller child nodes Prabhakar
2026-07-02 12:31 ` [PATCH RFC v2 4/9] arm64: dts: renesas: r9a09g087: " Prabhakar
2026-07-02 12:31 ` [PATCH RFC v2 5/9] dt-bindings: watchdog: renesas,r9a09g057-wdt: Add SYS syscon support Prabhakar
2026-07-02 12:38 ` sashiko-bot [this message]
2026-07-02 12:31 ` [PATCH RFC v2 6/9] watchdog: rzv2h: Refactor WDTDCR start/stop handling Prabhakar
2026-07-02 12:31 ` [PATCH RFC v2 7/9] watchdog: rzv2h: Add syscon support for RZ/T2H and RZ/N2H WDT control register Prabhakar
2026-07-02 12:42 ` sashiko-bot
2026-07-02 13:27 ` Guenter Roeck
2026-07-02 15:12 ` Lad, Prabhakar
2026-07-02 12:31 ` [PATCH RFC v2 8/9] arm64: dts: renesas: r9a09g077: Use SYS syscon for WDTDCR access Prabhakar
2026-07-02 12:44 ` sashiko-bot
2026-07-02 12:31 ` [PATCH RFC v2 9/9] arm64: dts: renesas: r9a09g087: " Prabhakar
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=20260702123836.3F6801F000E9@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=prabhakar.csengg@gmail.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wsa+renesas@sang-engineering.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