From: Wang Qing <wangqing@vivo.com>
To: Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Wang Qing <wangqing@vivo.com>
Subject: [PATCH V6 2/2] doc: mtk-wdt: support pre-timeout when the bark irq is available
Date: Thu, 22 Apr 2021 10:45:32 +0800 [thread overview]
Message-ID: <1619059532-17805-3-git-send-email-wangqing@vivo.com> (raw)
In-Reply-To: <1619059532-17805-1-git-send-email-wangqing@vivo.com>
Add description of pre-timeout in mtk-wdt.
Signed-off-by: Wang Qing <wangqing@vivo.com>
---
Documentation/devicetree/bindings/watchdog/mtk-wdt.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/watchdog/mtk-wdt.txt b/Documentation/devicetree/bindings/watchdog/mtk-wdt.txt
index e36ba60..ae57d6c
--- a/Documentation/devicetree/bindings/watchdog/mtk-wdt.txt
+++ b/Documentation/devicetree/bindings/watchdog/mtk-wdt.txt
@@ -1,5 +1,8 @@
Mediatek SoCs Watchdog timer
+The watchdog supports a pre-timeout interrupt that fires timeout-sec/2
+before the expiry.
+
Required properties:
- compatible should contain:
--
2.7.4
next prev parent reply other threads:[~2021-04-22 2:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 2:45 [PATCH V6 0/2] watchdog: mtk: support pre-timeout when the bark irq is available Wang Qing
2021-04-22 2:45 ` [PATCH V6 1/2] " Wang Qing
2021-04-22 3:31 ` Guenter Roeck
2021-04-22 3:46 ` 王擎
2021-04-22 4:02 ` Guenter Roeck
2021-04-22 7:05 ` 王擎
2021-04-22 13:56 ` Guenter Roeck
2021-04-22 2:45 ` Wang Qing [this message]
2021-04-22 3:32 ` [PATCH V6 2/2] doc: mtk-wdt: " Guenter Roeck
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=1619059532-17805-3-git-send-email-wangqing@vivo.com \
--to=wangqing@vivo.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@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).