From: Biju Das <biju.das.jz@bp.renesas.com>
To: geert <geert@linux-m68k.org>, biju.das.au <biju.das.au@gmail.com>
Cc: 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" <linux-watchdog@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: RE: [PATCH] dt-bindings: watchdog: renesas,wdt: Document RZ/G3L support
Date: Tue, 5 May 2026 08:06:53 +0000 [thread overview]
Message-ID: <TY3PR01MB11346B5F06CA491FCC4330D99863E2@TY3PR01MB11346.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CAMuHMdVfGA6yie7FJ1p5Vo8pzYfT7JaapVKKs89zDajyjoYdyw@mail.gmail.com>
Hi Geert,
Thanks for the feedback.
> -----Original Message-----
> From: Geert Uytterhoeven <geert@linux-m68k.org>
> Sent: 05 May 2026 08:32
> Subject: Re: [PATCH] dt-bindings: watchdog: renesas,wdt: Document RZ/G3L support
>
> Hi Biju,
>
> On Fri, 6 Feb 2026 at 12:22, Biju <biju.das.au@gmail.com> wrote:
> > From: Biju Das <biju.das.jz@bp.renesas.com>
> >
> > Document the support for the watchdog IP available on RZ/G3L SoC. The
> > watchdog IP available on RZ/G3L SoC is identical to the one found on
> > RZ/G2L SoC.
> >
> > Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
>
> Thanks for your patch!
>
> > ---
> > a/Documentation/devicetree/bindings/watchdog/renesas,rzg2l-wdt.yaml
> > +++ b/Documentation/devicetree/bindings/watchdog/renesas,rzg2l-wdt.yam
> > +++ l
> > @@ -18,6 +18,7 @@ properties:
> > - renesas,r9a07g044-wdt # RZ/G2{L,LC}
> > - renesas,r9a07g054-wdt # RZ/V2L
> > - renesas,r9a08g045-wdt # RZ/G3S
> > + - renesas,r9a08g046-wdt # RZ/G3L
> > - const: renesas,rzg2l-wdt
> >
> > - items:
>
> However, there seems to be a small difference in the formulas for the timeout register value on the
> various SoCs:
>
> RZ/G2L, RZ/G2UL, and RZ/V2L:
>
> WDTTIME setting value = \frac{WDT cycle}{(WDTn_CLK (n = 0,1,2) cycle × 1024 × 1024) − 1}
>
> RZ/G3S and RZ/G3E:
>
> WDTTIME setting value = \frac{WDT cycle}{(WDTn_CLK (n = 0,1,2) cycle × 1024 × 1024} − 1
>
> I.e. on the former, the "- 1" offset is inside the denominator, while on the former, it is outside the
> fraction. I assume this is just a typo in the documentation, and both formulas are supposed to be
> identical, so
I agree it is a typo on RZ/G2L, RZ/G2UL, and RZ/V2L hardware manual, I will report this issue to
Documentation team.
as
Watchdog timer cycle = WDTn_CLK (n = 0, 1, 2) cycle × 1024 × 1024 × (WDTTIME setting value + 1)
To get min/max value 43.69/178956.97 msec with 24 MHz mentioned on all DoCs,
WDT min Cycle = 1024 * 1024 * (0 + 1) / (24 * 10^6) = 0.043690 = 43.69 msec
WDT max cycle = 1024 * 1024 * (0xfff + 1) / (24 * 10^6) = 178956.97 msec
Cheers,
Biju
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But when I'm talking to
> journalists I just say "programmer" or something like that.
> -- Linus Torvalds
prev parent reply other threads:[~2026-05-05 8:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 11:22 Biju
2026-02-23 17:12 ` Rob Herring (Arm)
2026-05-05 6:04 ` Biju Das
2026-05-05 7:31 ` Geert Uytterhoeven
2026-05-05 8:06 ` Biju Das [this message]
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=TY3PR01MB11346B5F06CA491FCC4330D99863E2@TY3PR01MB11346.jpnprd01.prod.outlook.com \
--to=biju.das.jz@bp.renesas.com \
--cc=biju.das.au@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=krzk+dt@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=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@kernel.org \
--cc=wim@linux-watchdog.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
all inboxes | Powered by JetHome®