From: sashiko-bot@kernel.org
To: "Pinkesh Vaghela" <pinkesh.vaghela@einfochips.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v3 8/8] riscv: dts: eswin: add watchdog support
Date: Tue, 04 Aug 2026 11:34:19 +0000 [thread overview]
Message-ID: <20260804113419.EF11F1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260804104431.1391839-9-pinkesh.vaghela@einfochips.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Incorrect timer reference clock mapping for watchdog nodes
--
--- Patch [8]: [PATCH v3 8/8] riscv: dts: eswin: add watchdog support ---
commit bfe09d553ee566b62eb6947526013fd32a57d405
Author: Pritesh Patel <pritesh.patel@einfochips.com>
riscv: dts: eswin: add watchdog support
This commit adds watchdog nodes for the ESWIN EIC7700 SoC and enables
them for the HiFive Premier P550 board.
[ ... ]
> diff --git a/arch/riscv/boot/dts/eswin/eic7700.dtsi b/arch/riscv/boot/dts/eswin/eic7700.dtsi
> index c13432d145042..f873e9eeb9290 100644
> --- a/arch/riscv/boot/dts/eswin/eic7700.dtsi
> +++ b/arch/riscv/boot/dts/eswin/eic7700.dtsi
> @@ -265,6 +265,46 @@ syscon: syscon@50440000 {
> };
> };
>
> + wdt0: watchdog@50800000 {
> + compatible = "snps,dw-wdt";
> + reg = <0x0 0x50800000 0x0 0x4000>;
> + interrupts = <87>;
> + clocks = <&clk EIC7700_CLK_GATE_LSP_WDT0_PCLK>;
> + clock-names = "tclk";
[Severity: High]
Will this cause the watchdog to calculate timeouts incorrectly or freeze
entirely?
The snps,dw-wdt driver uses the clock named tclk to determine the frequency
for timeout calculations. Here it is mapped to the APB interface clock
(EIC7700_CLK_GATE_LSP_WDT0_PCLK).
Since the ESWIN EIC7700 clock driver defines a separate watchdog reference
clock (EIC7700_CLK_GATE_NOC_WDREF), providing the faster APB clock frequency
to the driver might cause it to calculate extremely large tick counts. This
would result in physical timeouts taking much longer than requested.
Additionally, if EIC7700_CLK_GATE_NOC_WDREF is not referenced here, could
the common clock framework's clk_disable_unused late initcall gate it and
completely freeze the watchdog counter?
This same clock mapping pattern appears in the wdt1, wdt2, and wdt3 nodes
introduced below.
> + resets = <&reset EIC7700_RESET_WDT0>;
> + status = "disabled";
> + };
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260804104431.1391839-1-pinkesh.vaghela@einfochips.com?part=8
next prev parent reply other threads:[~2026-08-04 11:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 10:44 [PATCH v3 0/8] riscv: eswin: eic7700: Add support for clocks, resets, pinctrl, HSP bus, I2C and watchdog Pinkesh Vaghela
2026-08-04 10:44 ` Pinkesh Vaghela
2026-08-04 10:44 ` [PATCH v3 1/8] riscv: dts: eswin: add reset generator for EIC7700 SoC Pinkesh Vaghela
2026-08-04 10:44 ` Pinkesh Vaghela
2026-08-04 10:44 ` [PATCH v3 2/8] riscv: dts: eswin: add clock " Pinkesh Vaghela
2026-08-04 10:44 ` Pinkesh Vaghela
2026-08-04 10:44 ` [PATCH v3 3/8] riscv: dts: eswin: eic7700: add pinctrl support Pinkesh Vaghela
2026-08-04 10:44 ` Pinkesh Vaghela
2026-08-04 10:44 ` [PATCH v3 4/8] dt-bindings: mfd: syscon: add ESWIN EIC7700 compatible Pinkesh Vaghela
2026-08-04 10:44 ` Pinkesh Vaghela
2026-08-04 11:02 ` sashiko-bot
2026-08-04 13:26 ` Pinkesh Vaghela
2026-08-12 8:14 ` (subset) " Lee Jones
2026-08-12 8:14 ` Lee Jones
2026-08-04 10:44 ` [PATCH v3 5/8] riscv: dts: eswin: add hsp bus node Pinkesh Vaghela
2026-08-04 10:44 ` Pinkesh Vaghela
2026-08-04 11:12 ` sashiko-bot
2026-08-04 13:07 ` Pinkesh Vaghela
2026-08-04 10:44 ` [PATCH v3 6/8] dt-bindings: i2c: dw: add ESWIN EIC7700 SoC I2C controller Pinkesh Vaghela
2026-08-04 10:44 ` Pinkesh Vaghela
2026-08-04 10:44 ` [PATCH v3 7/8] riscv: dts: eswin: add I2C controller support Pinkesh Vaghela
2026-08-04 10:44 ` Pinkesh Vaghela
2026-08-04 11:22 ` sashiko-bot
2026-08-04 13:19 ` Pinkesh Vaghela
2026-08-04 10:44 ` [PATCH v3 8/8] riscv: dts: eswin: add watchdog support Pinkesh Vaghela
2026-08-04 10:44 ` Pinkesh Vaghela
2026-08-04 11:34 ` sashiko-bot [this message]
2026-08-04 13:03 ` Pinkesh Vaghela
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=20260804113419.EF11F1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=pinkesh.vaghela@einfochips.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.