From: CL Wang <cl634@andestech.com>
To: <cl634@andestech.com>, <wim@linux-watchdog.org>,
<linux@roeck-us.net>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-watchdog@vger.kernel.org>, <tim609@andestech.com>
Subject: [PATCH 0/3] watchdog: Add support for Andes ATCWDT200
Date: Wed, 7 Jan 2026 22:50:54 +0800 [thread overview]
Message-ID: <20260107145058.213334-1-cl634@andestech.com> (raw)
This series adds support for the Andes ATCWDT200 watchdog timer.
The driver integrates with the Linux watchdog framework and supports:
- Basic watchdog operations (start, stop, ping, set_timeout).
- Programmable reset and interrupt intervals.
- Automatic detection of the supported interrupt timer bit-width.
- System reset via the watchdog restart handler.
CL Wang (3):
dt-bindings: watchdog: Add support for Andes ATCWDT200
watchdog: atcwdt200: Add driver for Andes ATCWDT200
MAINTAINERS: Add entry for Andes ATCWDT200
.../watchdog/andestech,ae350-wdt.yaml | 48 ++
MAINTAINERS | 6 +
drivers/watchdog/Kconfig | 9 +
drivers/watchdog/Makefile | 1 +
drivers/watchdog/atcwdt200_wdt.c | 596 ++++++++++++++++++
5 files changed, 660 insertions(+)
create mode 100644 Documentation/devicetree/bindings/watchdog/andestech,ae350-wdt.yaml
create mode 100644 drivers/watchdog/atcwdt200_wdt.c
--
2.34.1
next reply other threads:[~2026-01-07 15:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 14:50 CL Wang [this message]
2026-01-07 14:50 ` [PATCH 1/3] dt-bindings: " CL Wang
2026-01-07 15:44 ` Krzysztof Kozlowski
2026-01-09 9:35 ` CL Wang
2026-01-07 16:23 ` Rob Herring (Arm)
2026-01-12 6:59 ` CL Wang
2026-01-07 14:50 ` [PATCH 2/3] watchdog: atcwdt200: Add driver " CL Wang
2026-01-07 15:46 ` Krzysztof Kozlowski
2026-01-12 7:05 ` CL Wang
2026-01-07 14:50 ` [PATCH 3/3] MAINTAINERS: Add entry " CL Wang
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=20260107145058.213334-1-cl634@andestech.com \
--to=cl634@andestech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh@kernel.org \
--cc=tim609@andestech.com \
--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®