From: Guenter Roeck <linux@roeck-us.net>
To: Prabhakar <prabhakar.csengg@gmail.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Magnus Damm <magnus.damm@gmail.com>
Cc: linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Biju Das <biju.das.jz@bp.renesas.com>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH v3 4/6] watchdog: rzv2h: Add support for configurable count clock source
Date: Fri, 5 Sep 2025 08:01:19 -0700 [thread overview]
Message-ID: <ddf53f4e-98d9-4f3b-b80b-715361a4cb42@roeck-us.net> (raw)
In-Reply-To: <20250804195723.3963524-5-prabhakar.mahadev-lad.rj@bp.renesas.com>
On 8/4/25 12:57, Prabhakar wrote:
> From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
>
> Add support for selecting the count clock source used by the watchdog
> timer. The RZ/V2H(P) SoC uses the LOCO as the count source, whereas on
> RZ/T2H and RZ/N2H SoCs, the count source is the peripheral clock (PCLKL).
>
> Introduce a `count_source` field in the SoC-specific data structure and
> refactor the clock rate selection logic accordingly. This prepares the
> driver for supporting the RZ/T2H and RZ/N2H SoCs, which differ in their
> watchdog clocking architecture from RZ/V2H(P).
>
> Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> Reviewed-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
next prev parent reply other threads:[~2025-09-05 15:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 19:57 [PATCH v3 0/6] Add watchdog driver support for RZ/T2H and RZ/N2H SoCs Prabhakar
2025-08-04 19:57 ` [PATCH v3 1/6] dt-bindings: watchdog: renesas,wdt: Add support for RZ/T2H and RZ/N2H Prabhakar
2025-08-18 10:00 ` Geert Uytterhoeven
2025-08-18 13:30 ` Lad, Prabhakar
2025-09-05 15:00 ` Guenter Roeck
2025-08-04 19:57 ` [PATCH v3 2/6] watchdog: rzv2h: Obtain clock-divider and timeout values from OF match data Prabhakar
2025-09-05 14:59 ` Guenter Roeck
2025-08-04 19:57 ` [PATCH v3 3/6] watchdog: rzv2h: Make "oscclk" and reset controller optional Prabhakar
2025-09-05 14:59 ` Guenter Roeck
2025-08-04 19:57 ` [PATCH v3 4/6] watchdog: rzv2h: Add support for configurable count clock source Prabhakar
2025-09-05 15:01 ` Guenter Roeck [this message]
2025-08-04 19:57 ` [PATCH v3 5/6] watchdog: rzv2h: Add support for RZ/T2H Prabhakar
2025-09-05 15:01 ` Guenter Roeck
2025-08-04 19:57 ` [PATCH v3 6/6] watchdog: rzv2h: Improve error strings and add newlines Prabhakar
2025-09-05 15:02 ` Guenter Roeck
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=ddf53f4e-98d9-4f3b-b80b-715361a4cb42@roeck-us.net \
--to=linux@roeck-us.net \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--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=magnus.damm@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=prabhakar.csengg@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
all inboxes | Powered by JetHome®