From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Guenter Roeck <linux@roeck-us.net>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-watchdog@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh@kernel.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>
Subject: [PATCH 0/2] watchdog: add Renesas Window Watchdog support
Date: Wed, 17 Sep 2025 20:56:47 +0200 [thread overview]
Message-ID: <20250917185651.12428-1-wsa+renesas@sang-engineering.com> (raw)
This Window Watchdog is a little peculiar because it can only be setup
once but we cannot find out if this write already happened. So,
configuration is delegated to the firmware/bootloader and the driver
will adapt to whatever is configured. The driver handles all bits
described in the datasheets. This is really all there is.
Tested on a SparrowHawk board (Renesas R-Car V4H).
Looking forward to comments!
Wolfram Sang (2):
dt-bindings: watchdog: Add Renesas WWDT
watchdog: renesas_wwdt: add driver
.../bindings/watchdog/renesas,wwdt.yaml | 78 +++++++++
drivers/watchdog/Kconfig | 8 +
drivers/watchdog/Makefile | 1 +
drivers/watchdog/renesas_wwdt.c | 156 ++++++++++++++++++
4 files changed, 243 insertions(+)
create mode 100644 Documentation/devicetree/bindings/watchdog/renesas,wwdt.yaml
create mode 100644 drivers/watchdog/renesas_wwdt.c
--
2.47.2
next reply other threads:[~2025-09-17 18:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 18:56 Wolfram Sang [this message]
2025-09-17 18:56 ` [PATCH 1/2] dt-bindings: watchdog: Add Renesas WWDT Wolfram Sang
2025-09-17 19:16 ` Conor Dooley
2025-09-17 18:56 ` [PATCH 2/2] watchdog: renesas_wwdt: add driver Wolfram Sang
2025-09-18 14:22 ` kernel test robot
2025-10-06 11:58 ` Geert Uytterhoeven
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=20250917185651.12428-1-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=magnus.damm@gmail.com \
--cc=robh@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).