public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Herve Codina (Schneider Electric)" <herve.codina@bootlin.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>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	linux-clk@vger.kernel.org,
	Pascal Eberhard <pascal.eberhard@se.com>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH 3/5] dt-bindings: watchdog: renesas,rzn1-wdt: Document the reset line
Date: Tue, 10 Mar 2026 18:38:50 +0100	[thread overview]
Message-ID: <392ededd-ee73-4afa-88b4-b15fe1dc3457@kernel.org> (raw)
In-Reply-To: <20260310173249.161354-4-herve.codina@bootlin.com>

On 10/03/2026 18:32, Herve Codina (Schneider Electric) wrote:
> Watchdogs available in the RZ/N1 SoC can use their specific hardware
> reset line to reset the system on watchdog timeout.
> 
> This line is not documented in the current binding.
> 
> Fill this lack and describe this per watchdog reset line.
> 
> Signed-off-by: Herve Codina (Schneider Electric) <herve.codina@bootlin.com>
> ---
>  .../bindings/watchdog/renesas,rzn1-wdt.yaml   | 22 +++++++++++++++++++
>  .../dt-bindings/watchdog/renesas,rzn1-wdt.h   | 16 ++++++++++++++
>  2 files changed, 38 insertions(+)
>  create mode 100644 include/dt-bindings/watchdog/renesas,rzn1-wdt.h
> 
> diff --git a/Documentation/devicetree/bindings/watchdog/renesas,rzn1-wdt.yaml b/Documentation/devicetree/bindings/watchdog/renesas,rzn1-wdt.yaml
> index 7e3ee533cd56..40a9a4ebc716 100644
> --- a/Documentation/devicetree/bindings/watchdog/renesas,rzn1-wdt.yaml
> +++ b/Documentation/devicetree/bindings/watchdog/renesas,rzn1-wdt.yaml
> @@ -26,6 +26,26 @@ properties:
>  
>    timeout-sec: true
>  
> +  renesas,reset-line:
> +    $ref: /schemas/types.yaml#/definitions/uint32
> +    enum: [0, 1]
> +    description: |
> +      The watchdog reset line (dt-bindings/watchdog/renesas,rzn1-wdt.h defines
> +      these values). A wachdog timeout asserts this reset line to perform a
> +      hardware system reset. Two watchdogs are present in the RZ/N1 SoC and
> +      each of them has a dedicated reset line.
> +
> +        - 0: RZN1_WDT_A7_0
> +          This reset line can be asserted only by the A7 0 watchdog. This
> +          watchdog is the one mapped at 0x40008000 on RZ/N1 SoCs.
> +
> +        - 1: RZN1_WDT_A7_1
> +          This reset line can be asserted only by the A7 1 watchdog. This
> +          watchdog is the one mapped at 0x40009000 on RZ/N1 SoCs.
> +
> +      If the renesas,reset-line property is not present, the watchdog timeout
> +      only triggers an interrupt.

I don't understand. You have two watchdogs (0x40008000 and 0x40009000)
so why you would tell each of them that they can reset line associated
with them? Can a watchdog reset other watchdog's line? No, thus code like:

watchdog@40008000 {
	renesas,reset-line = <RZN1_WDT_A7_1>;
};

makes no sense and thus is pointless to specify in DT.

What's more, if reset line is always wired (and how could it be since it
is fully within the soc), why would this be board-level property?



> +
>  required:
>    - compatible
>    - reg
> @@ -41,10 +61,12 @@ examples:
>    - |
>      #include <dt-bindings/clock/r9a06g032-sysctrl.h>
>      #include <dt-bindings/interrupt-controller/arm-gic.h>
> +    #include <dt-bindings/watchdog/renesas,rzn1-wdt.h>
>  
>      watchdog@40008000 {
>              compatible = "renesas,r9a06g032-wdt", "renesas,rzn1-wdt";
>              reg = <0x40008000 0x1000>;
>              interrupts = <GIC_SPI 73 IRQ_TYPE_EDGE_RISING>;
>              clocks = <&sysctrl R9A06G032_CLK_WATCHDOG>;
> +            renesas,reset-line = <RZN1_WDT_A7_0>;
>      };
> diff --git a/include/dt-bindings/watchdog/renesas,rzn1-wdt.h b/include/dt-bindings/watchdog/renesas,rzn1-wdt.h
> new file mode 100644
> index 000000000000..fe534aff0609
> --- /dev/null
> +++ b/include/dt-bindings/watchdog/renesas,rzn1-wdt.h
> @@ -0,0 +1,16 @@
> +/* SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) */
> +/*
> + * RZ/N1 watchdog reset lines
> + *
> + * Copyright (C) 2026 Bootlin
> + *
> + * Herve Codina <herve.codina@bootlin.com>
> + */
> +
> +#ifndef __DT_BINDINGS_RZN1_WDT_H__
> +#define __DT_BINDINGS_RZN1_WDT_H__
> +
> +#define RZN1_WDT_A7_0		0
> +#define RZN1_WDT_A7_1		1

I also see little value of the binding, but probably because I don't
understand the point of this patch.


Best regards,
Krzysztof

  reply	other threads:[~2026-03-10 17:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10 17:32 [PATCH 0/5] watchdog: rzn1: Add support for direct hardware reset Herve Codina (Schneider Electric)
2026-03-10 17:32 ` [PATCH 1/5] watchdog: rzn1: Fix reverse xmas tree declaration Herve Codina (Schneider Electric)
2026-03-10 17:32 ` [PATCH 2/5] watchdog: rzn1: Use dev_err_probe() Herve Codina (Schneider Electric)
2026-03-10 17:32 ` [PATCH 3/5] dt-bindings: watchdog: renesas,rzn1-wdt: Document the reset line Herve Codina (Schneider Electric)
2026-03-10 17:38   ` Krzysztof Kozlowski [this message]
2026-03-10 18:12     ` Herve Codina
2026-03-10 20:14       ` Krzysztof Kozlowski
2026-03-10 17:32 ` [PATCH 4/5] clk: renesas: r9a06g032: Introduce a helper to set rsten register Herve Codina (Schneider Electric)
2026-03-10 17:32 ` [PATCH 5/5] watchdog: rzn1: Add support for direct hardware reset Herve Codina (Schneider Electric)
2026-03-11  2:12   ` kernel test robot
2026-03-11  6:07   ` kernel test robot
2026-03-10 21:53 ` [PATCH 0/5] " Wolfram Sang
2026-03-11 15:09   ` Herve Codina
2026-03-11 15:27     ` 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=392ededd-ee73-4afa-88b4-b15fe1dc3457@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=herve.codina@bootlin.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.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=miquel.raynal@bootlin.com \
    --cc=mturquette@baylibre.com \
    --cc=pascal.eberhard@se.com \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=thomas.petazzoni@bootlin.com \
    --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