From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: wim@linux-watchdog.org
Cc: linux@roeck-us.net, linux-watchdog@vger.kernel.org,
linux-kernel@vger.kernel.org, S32@nxp.com,
ghennadi.procopciuc@nxp.com, thomas.fossati@linaro.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, alexandru-catalin.ionita@nxp.com
Subject: [PATCH v4 0/2] Add the NXP S32 Watchdog
Date: Thu, 10 Apr 2025 10:26:12 +0200 [thread overview]
Message-ID: <20250410082616.1855860-1-daniel.lezcano@linaro.org> (raw)
The NXP S32 watchdog, referenced in the documentation as the Software
Watchdog Timer is actually a hardware watchdog. The system has one
watchdog per core but an assertation does not directly reset the
system as this behavior relies on a particular setup and another
component which is not part of these changes. However the first
watchdog on the system, tied with the Cortex-M4 #0 is a particular
case where it will reset the system directly. This is enough for the
watchdog purpose on Linux.
The watchdog relies on the default timeout described in the device
tree but if another timeout is needed at boot time, it can be changed
with the module parameter.
If the kernel has to service the watchdog in place of the userspace,
it can specify the 'early-enable' option at boot time.
And finally, if starting the watchdog has no wayback then the option
'nowayout' can be also specified in the boot option.
Changelog:
- v4:
- Update the watchdog timeout when the callback is called (Alexandru-Catalin Ionita)
- Fix the clocks bindings to have all the clocks described (Krzysztof Kozlowski)
- v3:
- Add the clocks for the module and the register (Ghennadi Procopciuc)
- Use the clock name from the driver
- Removed Review-by tag from Krzysztof Kozlowski as the bindings changed
- v2:
- Removed debugfs code as considered pointless for a such simple
driver (Arnd Bergmann)
- Replaced __raw_readl / __raw_writel by readl and writel (Arnd Bergmann)
- Reordered alphabetically the headers (Guenter Roeck)
- Enclosed macro parameter into parenthesis (Guenter Roeck)
- Fixed checkpatch reported errors (Guenter Roeck)
- Clarified a ping on a stopped timer does not affect it (Guenter Roeck)
- Used wdt_is_running() to save an extra IO (Guenter Roeck)
- Fixed a misleading comment about starting the watchdog at boot time (Guenter Roeck)
- Replaced allocation size sizeof(struct ...) by sizeof(*var) (Krzysztof Kozlowski)
- Drop old way of describing the module and use table module device (Krzysztof Kozlowski)
- Replaced additionalProperties by unevaluatedProperties (Rob Herring)
- Removed the DT bindings description as it is obvious (Ghennadi Procopciuc)
- Fixed DT bindings compatible string (Krzysztof Kozlowski)
- v1: initial posting
Daniel Lezcano (2):
dt-bindings: watchdog: Add NXP Software Watchdog Timer
watchdog: Add the Watchdog Timer for the NXP S32 platform
.../bindings/watchdog/nxp,s32g2-swt.yaml | 54 +++
drivers/watchdog/Kconfig | 9 +
drivers/watchdog/Makefile | 1 +
drivers/watchdog/s32g_wdt.c | 315 ++++++++++++++++++
4 files changed, 379 insertions(+)
create mode 100644 Documentation/devicetree/bindings/watchdog/nxp,s32g2-swt.yaml
create mode 100644 drivers/watchdog/s32g_wdt.c
--
2.43.0
next reply other threads:[~2025-04-10 8:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 8:26 Daniel Lezcano [this message]
2025-04-10 8:26 ` [PATCH v4 1/2] dt-bindings: watchdog: Add NXP Software Watchdog Timer Daniel Lezcano
2025-04-11 16:27 ` Rob Herring (Arm)
2025-04-12 3:23 ` Guenter Roeck
2025-04-24 14:12 ` Daniel Lezcano
2025-04-10 8:26 ` [PATCH v4 2/2] watchdog: Add the Watchdog Timer for the NXP S32 platform Daniel Lezcano
2025-04-12 3:22 ` Guenter Roeck
2025-04-14 9:07 ` Alexandru-Catalin Ionita
2025-05-14 15:30 ` [PATCH v4 0/2] Add the NXP S32 Watchdog Daniel Lezcano
2025-05-14 18:09 ` Guenter Roeck
2025-05-28 13:17 ` Daniel Lezcano
2025-05-28 19:24 ` Wim Van Sebroeck
2025-05-29 17:56 ` Daniel Lezcano
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=20250410082616.1855860-1-daniel.lezcano@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=S32@nxp.com \
--cc=alexandru-catalin.ionita@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ghennadi.procopciuc@nxp.com \
--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=thomas.fossati@linaro.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).