From: Marek Vasut <marek.vasut@mailbox.org>
To: smelamud@redhat.com, Tom Rini <trini@konsulko.com>,
Nobuhiro Iwamatsu <iwamatsu@nigauri.org>,
Marek Vasut <marek.vasut+renesas@mailbox.org>,
Lukasz Majewski <lukma@denx.de>,
Sean Anderson <seanga2@gmail.com>, Stefan Roese <sr@denx.de>,
Mattijs Korpershoek <mkorpershoek@kernel.org>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH v2] renesas: Renesas R-Car Gen4 watchdog driver
Date: Fri, 30 May 2025 04:17:41 +0200 [thread overview]
Message-ID: <032c25da-e093-4f44-9cd9-bbcf2c2c2156@mailbox.org> (raw)
In-Reply-To: <20250530-us-renesas-watchdog-v2-1-b0d8f96c64dc@redhat.com>
On 5/30/25 12:58 AM, Shmuel Melamud via B4 Relay wrote:
> From: Shmuel Melamud <smelamud@redhat.com>
>
> Add support of Renesas R-Car Gen4 watchdog timer. Timeouts up to
> 8184.0s are supported (CKS1 register is not involved). The watchdog
> uses the clock type CLK_TYPE_GEN4_MDSEL, so handling of this constant
> is added to gen3_clk_get_rate64() function.
>
> The timeout is set in
> dts/upstream/src/arm64/renesas/r8a779f0-spider-cpu.dtsi section &rwdt.
>
> This patch was tested on real Renesas R8A779F0 hardware. If the watchdog
> driver is enabled at the build time, the watchdog timer is initialized
> when U-Boot starts. Under normal circumstances, U-Boot loads the kernel,
> it starts systemd and systemd continues to pet the watchdog. If systemd
> is not started before the timeout expires, the watchdog resets the
> board.
>
> Signed-off-by: Shmuel Leib Melamud <smelamud@redhat.com>
> ---
> drivers/clk/renesas/clk-rcar-gen3.c | 4 +-
> drivers/watchdog/Kconfig | 8 ++
> drivers/watchdog/Makefile | 1 +
> drivers/watchdog/renesas_wdt.c | 172 ++++++++++++++++++++++++++++++++++++
> 4 files changed, 184 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/clk/renesas/clk-rcar-gen3.c b/drivers/clk/renesas/clk-rcar-gen3.c
> index 375cc4a4930873ad0d5509c19ad04a0ea5545aa0..5745acf4023c9114f6fa13b5e4baa306c5b57d33 100644
> --- a/drivers/clk/renesas/clk-rcar-gen3.c
> +++ b/drivers/clk/renesas/clk-rcar-gen3.c
> @@ -68,7 +68,7 @@ static int gen3_clk_get_parent(struct gen3_clk_priv *priv, struct clk *clk,
> if (ret)
> return ret;
>
> - if (core->type == CLK_TYPE_GEN3_MDSEL) {
> + if (core->type == CLK_TYPE_GEN3_MDSEL || core->type == CLK_TYPE_GEN4_MDSEL) {
> shift = priv->cpg_mode & BIT(core->offset) ? 0 : 16;
> parent->dev = clk->dev;
> parent->id = core->parent >> shift;
> @@ -318,6 +318,8 @@ static u64 gen3_clk_get_rate64(struct clk *clk)
> "FIXED");
>
> case CLK_TYPE_GEN3_MDSEL:
> + fallthrough;
> + case CLK_TYPE_GEN4_MDSEL:
> shift = priv->cpg_mode & BIT(core->offset) ? 0 : 16;
> div = (core->div >> shift) & 0xffff;
> rate = gen3_clk_get_rate64(&parent) / div;
Clock driver change should be in separate patch.
I'll try to review the watchdog driver itself in the next few days.
Thanks !
next prev parent reply other threads:[~2025-05-30 2:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 22:58 [PATCH v2] renesas: Renesas R-Car Gen4 watchdog driver Shmuel Melamud via B4 Relay
2025-05-30 2:17 ` Marek Vasut [this message]
2025-05-30 9:38 ` Mattijs Korpershoek
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=032c25da-e093-4f44-9cd9-bbcf2c2c2156@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=iwamatsu@nigauri.org \
--cc=lukma@denx.de \
--cc=marek.vasut+renesas@mailbox.org \
--cc=mkorpershoek@kernel.org \
--cc=seanga2@gmail.com \
--cc=smelamud@redhat.com \
--cc=sr@denx.de \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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