From: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-renesas-soc@vger.kernel.org,
Biju Das <biju.das.jz@bp.renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/4] dt-bindings: watchdog: factor out RZ/N1 watchdog
Date: Thu, 2 Oct 2025 11:02:52 +0100 [thread overview]
Message-ID: <CA+V-a8uw3jzkWbvD6dVUu1KjVpVRM=sBh6tS2ditGueOxeQi2w@mail.gmail.com> (raw)
In-Reply-To: <20250926112218.28723-3-wsa+renesas@sang-engineering.com>
Hi Wolfram,
Thank you for the patch.
On Fri, Sep 26, 2025 at 12:22 PM Wolfram Sang
<wsa+renesas@sang-engineering.com> wrote:
>
> Renesas created different watchdog IPs but they are all handled in the
> same binding documentation. This leads to a lot of conditional handling
> which makes it unnecessarily hard to add new items. Factor out the RZ/N1
> watchdog to make handling easier.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
> .../bindings/watchdog/renesas,rzn1-wdt.yaml | 49 +++++++++++++++++++
> .../bindings/watchdog/renesas,wdt.yaml | 6 ---
> 2 files changed, 49 insertions(+), 6 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/watchdog/renesas,rzn1-wdt.yaml
>
> diff --git a/Documentation/devicetree/bindings/watchdog/renesas,rzn1-wdt.yaml b/Documentation/devicetree/bindings/watchdog/renesas,rzn1-wdt.yaml
> new file mode 100644
> index 000000000000..01eab6cc1110
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/watchdog/renesas,rzn1-wdt.yaml
> @@ -0,0 +1,49 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/watchdog/renesas,rzn1-wdt.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Renesas RZ/N1 Watchdog Timer (WDT) Controller
> +
> +maintainers:
> + - Wolfram Sang <wsa+renesas@sang-engineering.com>
> +
> +properties:
> + compatible:
> + items:
> + - enum:
> + - renesas,r9a06g032-wdt # RZ/N1D
We could make this const instead. But if the DT maintainers are OK we
can leave it as is.
> + - const: renesas,rzn1-wdt # RZ/N1
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - clocks
> +
> +allOf:
> + - $ref: watchdog.yaml#
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/r9a06g032-sysctrl.h>
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> +
> + wdt0: watchdog@40008000 {
we can get rid of the label, rest LGTM.
Reviewed-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Cheers,
Prabhakar
> + compatible = "renesas,r9a06g032-wdt", "renesas,rzn1-wdt";
> + reg = <0x40008000 0x1000>;
> + interrupts = <GIC_SPI 73 IRQ_TYPE_EDGE_RISING>;
> + clocks = <&sysctrl R9A06G032_CLK_WATCHDOG>;
> + };
> diff --git a/Documentation/devicetree/bindings/watchdog/renesas,wdt.yaml b/Documentation/devicetree/bindings/watchdog/renesas,wdt.yaml
> index 8a25e0c6271f..12ba07781763 100644
> --- a/Documentation/devicetree/bindings/watchdog/renesas,wdt.yaml
> +++ b/Documentation/devicetree/bindings/watchdog/renesas,wdt.yaml
> @@ -13,11 +13,6 @@ maintainers:
> properties:
> compatible:
> oneOf:
> - - items:
> - - enum:
> - - renesas,r9a06g032-wdt # RZ/N1D
> - - const: renesas,rzn1-wdt # RZ/N1
> -
> - items:
> - enum:
> - renesas,r9a07g043-wdt # RZ/G2UL and RZ/Five
> @@ -134,7 +129,6 @@ allOf:
> contains:
> enum:
> - renesas,r9a09g077-wdt
> - - renesas,rzn1-wdt
> then:
> required:
> - power-domains
> --
> 2.47.2
>
>
next prev parent reply other threads:[~2025-10-02 10:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 11:22 [PATCH 0/4] dt-bindings: watchdog: factor out RZ watchdogs Wolfram Sang
2025-09-26 11:22 ` [PATCH 1/4] dt-bindings: watchdog: factor out RZ/A watchdog Wolfram Sang
2025-10-02 2:30 ` Guenter Roeck
2025-10-02 9:53 ` Lad, Prabhakar
2025-09-26 11:22 ` [PATCH 2/4] dt-bindings: watchdog: factor out RZ/N1 watchdog Wolfram Sang
2025-10-02 2:30 ` Guenter Roeck
2025-10-02 10:02 ` Lad, Prabhakar [this message]
2025-09-26 11:22 ` [PATCH 3/4] dt-bindings: watchdog: factor out RZ/G2L watchdog Wolfram Sang
2025-10-02 2:31 ` Guenter Roeck
2025-10-02 10:13 ` Lad, Prabhakar
2025-09-26 11:22 ` [PATCH 4/4] dt-bindings: watchdog: factor out RZ/V2H(P) watchdog Wolfram Sang
2025-10-02 2:31 ` Guenter Roeck
2025-10-02 10:33 ` Lad, Prabhakar
2025-10-02 11:49 ` Wolfram Sang
2025-10-02 19:56 ` Guenter Roeck
2025-10-02 2:23 ` [PATCH 0/4] dt-bindings: watchdog: factor out RZ watchdogs Rob Herring
2025-10-02 7:46 ` Wolfram Sang
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='CA+V-a8uw3jzkWbvD6dVUu1KjVpVRM=sBh6tS2ditGueOxeQi2w@mail.gmail.com' \
--to=prabhakar.csengg@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=magnus.damm@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@kernel.org \
--cc=wim@linux-watchdog.org \
--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;
as well as URLs for NNTP newsgroup(s).