From: Conor Dooley <conor@kernel.org>
To: Rong Zhang <rongrong@oss.cipunited.com>
Cc: Keguang Zhang <keguang.zhang@gmail.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>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Rong Zhang <i@rong.moe>, Yao Zi <me@ziyao.cc>,
Icenowy Zheng <uwu@icenowy.me>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
linux-mips@vger.kernel.org, linux-watchdog@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] MIPS: Loongson64: Add watchdog node for LS7A PCH
Date: Wed, 11 Nov 2026 17:43:09 +0000 [thread overview]
Message-ID: <20261111-unlucky-parrot-eb416eb0c794@spud> (raw)
In-Reply-To: <20261110-mips-ls7a-wdt-v1-3-968bb85122e6@oss.cipunited.com>
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
On Tue, Nov 10, 2026 at 03:02:32PM +0800, Rong Zhang wrote:
> The Loongson-7A has a watchdog. With proper support added to the
> loongson1_wdt driver, wire it up by adding a watchdog node to
> ls7a-pch.dtsi.
>
> Tested on Loongson-LS3A4000-7A1000-NUC-SE and Lenovo KaiTian M530Z.
>
> Signed-off-by: Rong Zhang <rongrong@oss.cipunited.com>
> ---
> arch/mips/boot/dts/loongson/ls7a-pch.dtsi | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/arch/mips/boot/dts/loongson/ls7a-pch.dtsi b/arch/mips/boot/dts/loongson/ls7a-pch.dtsi
> index f304f99946f1..770c96e9b908 100644
> --- a/arch/mips/boot/dts/loongson/ls7a-pch.dtsi
> +++ b/arch/mips/boot/dts/loongson/ls7a-pch.dtsi
> @@ -67,6 +67,12 @@ ls7a_uart3: serial@10080300 {
> no-loopback-test;
> };
>
> + watchdog: watchdog@100d0030 {
> + compatible = "loongson,ls7a-wdt";
> + reg = <0 0x100d0030 0 0xc>;
The style here is weird, usually we like to have the whole property in
hex BTW.
> + clock-frequency = <50000000>;
> + };
> +
> rtc0: rtc@100d0100 {
> compatible = "loongson,ls7a-rtc";
> reg = <0 0x100d0100 0 0x78>;
>
> --
> 2.55.0
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-11-11 17:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 7:02 [PATCH 0/4] watchdog: loongson1: Add Loongson-7A watchdog support Rong Zhang
2026-11-10 7:02 ` [PATCH 1/4] dt-bindings: watchdog: loongson,ls1x-wdt: Add ls7a-wdt compatible Rong Zhang
2026-11-10 18:58 ` Conor Dooley
2026-11-11 3:17 ` Rong Zhang
2026-11-11 17:45 ` Conor Dooley
2026-11-10 7:02 ` [PATCH 2/4] watchdog: loongson1: Add Loongson-7A watchdog support Rong Zhang
2026-11-10 7:47 ` Guenter Roeck
2026-11-10 7:59 ` Rong Zhang
2026-11-10 7:02 ` [PATCH 3/4] MIPS: Loongson64: Add watchdog node for LS7A PCH Rong Zhang
2026-11-11 17:43 ` Conor Dooley [this message]
2026-11-10 7:02 ` [PATCH 4/4] MIPS: loongson3_defconfig: Enable LOONGSON1_WDT by default Rong Zhang
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=20261111-unlucky-parrot-eb416eb0c794@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=i@rong.moe \
--cc=jiaxun.yang@flygoat.com \
--cc=keguang.zhang@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=me@ziyao.cc \
--cc=robh@kernel.org \
--cc=rongrong@oss.cipunited.com \
--cc=tsbogend@alpha.franken.de \
--cc=uwu@icenowy.me \
--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®