All of lore.kernel.org
 help / color / mirror / Atom feed
From: Isaac True <isaac.true@canonical.com>
To: linux-watchdog@vger.kernel.org
Cc: devicetree@vger.kernel.org, wim@linux-watchdog.org,
	linux@roeck-us.net, Isaac True <isaac.true@canonical.com>
Subject: [PATCH 1/2] dt-bindings: watchdog: gpio: add minimum interval
Date: Wed, 29 Jun 2022 13:06:25 +0200	[thread overview]
Message-ID: <20220629110626.2158127-1-isaac.true@canonical.com> (raw)

Add the "min_hw_margin_ms" parameter to gpio_wdt devices, allowing a
minimum interval to be specified, stopping watchdog devices from being
fed too quickly if they require a certain interval between feeds.

Signed-off-by: Isaac True <isaac.true@canonical.com>
---
 Documentation/devicetree/bindings/watchdog/gpio-wdt.txt | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/Documentation/devicetree/bindings/watchdog/gpio-wdt.txt b/Documentation/devicetree/bindings/watchdog/gpio-wdt.txt
index 198794963786..4f13dbbf12fd 100644
--- a/Documentation/devicetree/bindings/watchdog/gpio-wdt.txt
+++ b/Documentation/devicetree/bindings/watchdog/gpio-wdt.txt
@@ -12,6 +12,8 @@ Required Properties:
     the opposite level disables the WDT. Active level is determined
     by the GPIO flags.
 - hw_margin_ms: Maximum time to reset watchdog circuit (milliseconds).
+- min_hw_margin_ms: Minimum time to reset watchdog circuit (milliseconds).
+  Defaults to 0 ms.
 
 Optional Properties:
 - always-running: If the watchdog timer cannot be disabled, add this flag to
-- 
2.34.1


             reply	other threads:[~2022-06-29 11:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29 11:06 Isaac True [this message]
2022-06-29 11:06 ` [PATCH 2/2] watchdog: gpio: add configurable minimum interval Isaac True
2022-07-01 17:18   ` Rob Herring
2022-07-01 17:48     ` Guenter Roeck
2022-07-04 11:05       ` Isaac True
2022-07-05 19:56         ` Rob Herring
2022-07-07  9:00           ` Isaac True
2022-07-08 11:44             ` Guenter Roeck
2022-07-12 21:04               ` Rob Herring

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=20220629110626.2158127-1-isaac.true@canonical.com \
    --to=isaac.true@canonical.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.