From: Francesco Zanella <francesco.zanella@vimar.com>
To: linux-watchdog@vger.kernel.org, wim@linux-watchdog.org,
linux@roeck-us.net
Cc: devicetree@vger.kernel.org, robh+dt@kernel.org,
linux-kernel@vger.kernel.org,
Francesco Zanella <francesco.zanella@vimar.com>
Subject: [PATCH 0/2] GPIO WDT "start-at-boot" property
Date: Wed, 21 Apr 2021 18:26:19 +0200 [thread overview]
Message-ID: <20210421162621.24910-1-francesco.zanella@vimar.com> (raw)
I propose to add a new property to GPIO WDT device tree binding
"start-at-boot".
If this property is present, start pinging hw watchdog at probe, in order
to take advantage of kernel configs:
- WATCHDOG_HANDLE_BOOT_ENABLED: Avoid possible reboot if hw watchdog was
been enabled before the kernel (by uboot for example) and userspace
doesn't take control of /dev/watchdog in time;
- WATCHDOG_OPEN_TIMEOUT: Reboot if userspace doesn't take control of
/dev/watchdog within the timeout.
Francesco Zanella (2):
dt-bindings: watchdog: gpio-wdt: add "start-at-boot"
watchdog: gpio_wdt: add "start-at-boot" feature
Documentation/devicetree/bindings/watchdog/gpio-wdt.txt | 7 +++++++
drivers/watchdog/gpio_wdt.c | 6 +++++-
2 files changed, 12 insertions(+), 1 deletion(-)
--
2.17.1
next reply other threads:[~2021-04-21 16:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 16:26 Francesco Zanella [this message]
2021-04-21 16:26 ` [PATCH 1/2] dt-bindings: watchdog: gpio-wdt: add "start-at-boot" Francesco Zanella
2021-04-21 16:37 ` Guenter Roeck
2021-04-22 16:28 ` Francesco Zanella
2021-04-21 16:26 ` [PATCH 2/2] watchdog: gpio_wdt: add "start-at-boot" feature Francesco Zanella
2021-04-21 16:42 ` Guenter Roeck
2021-04-22 16:28 ` Francesco Zanella
2021-04-22 18:05 ` Guenter Roeck
2021-04-23 9:47 ` Francesco Zanella
2021-04-23 11:36 ` Rasmus Villemoes
2021-04-23 14:24 ` Francesco Zanella
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=20210421162621.24910-1-francesco.zanella@vimar.com \
--to=francesco.zanella@vimar.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--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
all inboxes | Powered by JetHome®