From: Tomer Maimon <tmaimon77@gmail.com>
To: andrew@codeconstruct.com.au, wim@linux-watchdog.org,
linux@roeck-us.net, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org
Cc: openbmc@lists.ozlabs.org, linux-watchdog@vger.kernel.org,
linux-doc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, avifishman70@gmail.com,
tmaimon77@gmail.com, tali.perry1@gmail.com, venture@google.com,
yuenn@google.com, benjaminfair@google.com, corbet@lwn.net,
skhan@linuxfoundation.org, joel@jms.id.au
Subject: [PATCH v4 0/3] watchdog: npcm: Add reset status detection support
Date: Mon, 6 Jul 2026 17:48:25 +0300 [thread overview]
Message-ID: <20260706144828.3517631-1-tmaimon77@gmail.com> (raw)
This series documents and implements reset indication reporting for the
NPCM watchdog driver on NPCM7xx and NPCM8xx systems, and documents the
optional GCR syscon property used by that support.
Patch 1 updates the watchdog binding to allow the optional
``nuvoton,sysgcr`` property used for reset-cause reporting.
Patch 2 adds watchdog documentation that describes the bootstatus
mapping.
Patch 3 reads the SoC reset indication bits and maps them into the
existing watchdog bootstatus flags for NPCM750 and NPCM845, while
leaving WPCM450 unchanged.
Addressed comments from:
- Conor Dooley: https://patchwork.ozlabs.org/project/openbmc/patch/20260705140100.1543486-2-tmaimon77@gmail.com/
Changes since version 3:
- make GCR syscon-property conditional.
Changes since version 2:
- reword patch 1 to explain the hardware reason for the GCR phandle and
why it is needed for the reset-status support, per Krzysztof's review
- cache NPCM750 reset status in SCRPAD2 so later watchdog probes can
report the same boot-time state
Changes since version 1:
- Modify reset detection handle in the watchodg.
- reword patch 1 to use the GCR syscon-property wording from the
applied NPCM reset binding update and drop the optional property from
the binding example.
- reword the patch subjects and commit message bodies to match current
kernel dt-bindings, docs, and watchdog style.
Tomer Maimon (3):
dt-bindings: watchdog: npcm: add GCR syscon property
docs: watchdog: npcm: Add reset status description
watchdog: npcm: add bootstatus support
.../watchdog/nuvoton,npcm750-wdt.yaml | 14 ++
Documentation/watchdog/index.rst | 1 +
Documentation/watchdog/npcm_wdt.rst | 71 ++++++
drivers/watchdog/npcm_wdt.c | 217 +++++++++++++++++-
4 files changed, 301 insertions(+), 2 deletions(-)
create mode 100644 Documentation/watchdog/npcm_wdt.rst
--
2.34.1
next reply other threads:[~2026-07-06 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 14:48 Tomer Maimon [this message]
2026-07-06 14:48 ` [PATCH v4 1/3] dt-bindings: watchdog: npcm: add GCR syscon property Tomer Maimon
2026-07-06 16:57 ` Conor Dooley
2026-07-06 14:48 ` [PATCH v4 2/3] docs: watchdog: npcm: Add reset status description Tomer Maimon
2026-07-06 14:52 ` sashiko-bot
2026-07-06 14:48 ` [PATCH v4 3/3] watchdog: npcm: add bootstatus support Tomer Maimon
2026-07-06 15:00 ` sashiko-bot
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=20260706144828.3517631-1-tmaimon77@gmail.com \
--to=tmaimon77@gmail.com \
--cc=andrew@codeconstruct.com.au \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=openbmc@lists.ozlabs.org \
--cc=robh@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tali.perry1@gmail.com \
--cc=venture@google.com \
--cc=wim@linux-watchdog.org \
--cc=yuenn@google.com \
/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