From: Conor Dooley <conor@kernel.org>
To: Tomer Maimon <tmaimon77@gmail.com>
Cc: andrew@codeconstruct.com.au, wim@linux-watchdog.org,
linux@roeck-us.net, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, 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, tali.perry1@gmail.com,
venture@google.com, yuenn@google.com, benjaminfair@google.com,
corbet@lwn.net, skhan@linuxfoundation.org, joel@jms.id.au
Subject: Re: [PATCH v3 1/3] dt-bindings: watchdog: npcm: add GCR syscon property
Date: Sun, 5 Jul 2026 15:36:35 +0100 [thread overview]
Message-ID: <20260705-gruffly-curing-ae3ab1044a94@spud> (raw)
In-Reply-To: <20260705140100.1543486-2-tmaimon77@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1592 bytes --]
On Sun, Jul 05, 2026 at 05:00:58PM +0300, Tomer Maimon wrote:
> NPCM750 and NPCM845 latch watchdog reset indications in the SoC
> GCR block rather than in the watchdog block itself.
>
> Add the optional nuvoton,sysgcr phandle so watchdog nodes can
> reference the shared GCR reset-status registers that hold those
> latched watchdog reset indications.
>
> This is needed by the following reset-status support, which reads
> those latches and reports watchdog-caused resets through bootstatus.
>
> Signed-off-by: Tomer Maimon <tmaimon77@gmail.com>
Since the 450 doesn't support this, please make it conditional.
pw-bot: changes-requested
Thanks,
Conor.
> ---
> .../devicetree/bindings/watchdog/nuvoton,npcm750-wdt.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/watchdog/nuvoton,npcm750-wdt.yaml b/Documentation/devicetree/bindings/watchdog/nuvoton,npcm750-wdt.yaml
> index 7aa30f5b5c49..99c225f166db 100644
> --- a/Documentation/devicetree/bindings/watchdog/nuvoton,npcm750-wdt.yaml
> +++ b/Documentation/devicetree/bindings/watchdog/nuvoton,npcm750-wdt.yaml
> @@ -40,6 +40,12 @@ properties:
> clock-frequency:
> description: Frequency in Hz of the clock that drives the NPCM timer.
>
> + nuvoton,sysgcr:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description:
> + a phandle to access the GCR reset-status registers that latch
> + watchdog reset indications on NPCM750 and NPCM845.
> +
> required:
> - compatible
> - reg
> --
> 2.34.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-07-05 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-05 14:00 [PATCH v3 0/3] watchdog: npcm: Add reset status detection support Tomer Maimon
2026-07-05 14:00 ` [PATCH v3 1/3] dt-bindings: watchdog: npcm: add GCR syscon property Tomer Maimon
2026-07-05 14:36 ` Conor Dooley [this message]
2026-07-05 14:00 ` [PATCH v3 2/3] docs: watchdog: npcm: Add reset status description Tomer Maimon
2026-07-05 14:01 ` [PATCH v3 3/3] watchdog: npcm: add bootstatus support Tomer Maimon
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=20260705-gruffly-curing-ae3ab1044a94@spud \
--to=conor@kernel.org \
--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=tmaimon77@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