From: huaqian.li@siemens.com
To: wim@linux-watchdog.org, linux@roeck-us.net, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org
Cc: huaqianlee@gmail.com, nm@ti.com, vigneshr@ti.com,
kristo@kernel.org, linux-watchdog@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, jan.kiszka@siemens.com,
baocheng.su@siemens.com, Li Hua Qian <huaqian.li@siemens.com>
Subject: [PATCH v3 1/3] dt-bindings: watchdog: ti,rti-wdt: Add support for WDIOF_CARDRESET
Date: Thu, 13 Jul 2023 17:51:25 +0800 [thread overview]
Message-ID: <20230713095127.1230109-2-huaqian.li@siemens.com> (raw)
In-Reply-To: <20230713095127.1230109-1-huaqian.li@siemens.com>
From: Li Hua Qian <huaqian.li@siemens.com>
TI RTI (Real Time Interrupt) Watchdog doesn't support to record the
watchdog cause. Add a reserved memory to know the last reboot was caused
by the watchdog card. In the reserved memory, some specific info will be
saved to indicate whether the watchdog reset was triggered in last
boot.
Signed-off-by: Li Hua Qian <huaqian.li@siemens.com>
---
.../devicetree/bindings/watchdog/ti,rti-wdt.yaml | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/Documentation/devicetree/bindings/watchdog/ti,rti-wdt.yaml b/Documentation/devicetree/bindings/watchdog/ti,rti-wdt.yaml
index fc553211e42d..8c16fd3929ec 100644
--- a/Documentation/devicetree/bindings/watchdog/ti,rti-wdt.yaml
+++ b/Documentation/devicetree/bindings/watchdog/ti,rti-wdt.yaml
@@ -34,6 +34,18 @@ properties:
power-domains:
maxItems: 1
+ memory-region:
+ maxItems: 1
+ description:
+ Contains the watchdog reserved memory. It is optional.
+ In the reserved memory, the specified values, which are
+ PON_REASON_SOF_NUM(0xBBBBCCCC), PON_REASON_MAGIC_NUM(0xDDDDDDDD),
+ and PON_REASON_EOF_NUM(0xCCCCBBBB), are pre-stored at the first
+ 3 * 4 bytes to tell that last boot was caused by watchdog reset.
+ Once the PON reason is captured by driver(rti_wdt.c), the driver
+ is supposed to wipe the whole memory region.
+
+
required:
- compatible
- reg
--
2.34.1
next prev parent reply other threads:[~2023-07-13 9:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 9:51 [PATCH v3 0/3] Add support for WDIOF_CARDRESET on TI AM65x huaqian.li
2023-07-13 9:51 ` huaqian.li [this message]
2023-07-13 9:59 ` [PATCH v3 1/3] dt-bindings: watchdog: ti,rti-wdt: Add support for WDIOF_CARDRESET Krzysztof Kozlowski
2023-07-13 9:51 ` [PATCH v3 2/3] arm64: dts: ti: Add reserved memory for watchdog huaqian.li
2023-07-14 22:52 ` Nishanth Menon
2023-07-14 23:27 ` Guenter Roeck
2023-07-15 5:25 ` Nishanth Menon
2024-01-08 8:16 ` Li, Hua Qian
2024-01-08 17:22 ` Nishanth Menon
2023-07-13 9:51 ` [PATCH v3 3/3] watchdog:rit_wdt: Add support for WDIOF_CARDRESET huaqian.li
2023-07-13 17:19 ` Guenter Roeck
2023-07-13 17:21 ` [PATCH v3 0/3] Add support for WDIOF_CARDRESET on TI AM65x Guenter Roeck
2023-07-14 7:00 ` Li, Hua Qian
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=20230713095127.1230109-2-huaqian.li@siemens.com \
--to=huaqian.li@siemens.com \
--cc=baocheng.su@siemens.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=huaqianlee@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).