From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH 2/2] watchdog: add watchdog behavior configuration
Date: Fri, 25 Sep 2020 10:36:37 +0200 [thread overview]
Message-ID: <4098208.1601022997@gemini.denx.de> (raw)
In-Reply-To: <20200924131931.GF14816@bill-the-cat>
Dear Tom,
In message <20200924131931.GF14816@bill-the-cat> you wrote:
>
> I'm talking about the case where we say we've enabled the WDT to
> supervise OS, but then bootefi something and have disabled the watchdog
> (to meet UEFI requirements) but didn't tell the user we've turned off
> the WDT that we had told them is on.
Any so-called "watchdog" that can be disabled / switched off by
software is not really woth this name. As such, the concept of
disabling a watchdog in software, is misleading at best and should
never ibe implemented.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Few people do business well who do nothing else.
-- Philip Earl of Chesterfield
next prev parent reply other threads:[~2020-09-25 8:36 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 16:45 [PATCH 1/2] watchdog: Hide WATCHDOG_RESET_DISABLE Michael Walle
2020-09-23 16:45 ` [PATCH 2/2] watchdog: add watchdog behavior configuration Michael Walle
2020-09-23 17:01 ` Mark Kettenis
2020-09-23 17:14 ` Tom Rini
2020-09-23 17:31 ` Heinrich Schuchardt
2020-09-23 17:35 ` Tom Rini
2020-09-24 7:33 ` Michael Walle
2020-09-24 8:10 ` Mark Kettenis
2020-09-24 8:20 ` Michael Walle
2020-09-24 10:22 ` Mark Kettenis
2020-09-24 21:05 ` Michael Walle
2020-09-24 13:19 ` Tom Rini
2020-09-24 20:30 ` Michael Walle
2020-09-24 20:58 ` Mark Kettenis
2020-09-24 21:14 ` Michael Walle
2020-09-25 1:17 ` Tom Rini
2020-09-25 8:36 ` Wolfgang Denk [this message]
2020-09-25 11:29 ` Heinrich Schuchardt
2020-09-25 13:00 ` Tom Rini
2020-09-25 13:26 ` Heinrich Schuchardt
2020-09-26 8:45 ` Wolfgang Denk
2020-09-26 10:54 ` Mark Kettenis
2020-09-26 12:39 ` Heinrich Schuchardt
2020-09-26 12:44 ` Tom Rini
2020-09-27 16:06 ` Michael Walle
2020-09-28 15:34 ` Tom Rini
2020-09-26 14:40 ` Wolfgang Denk
2020-09-26 14:22 ` Wolfgang Denk
2020-09-25 13:04 ` Wolfgang Denk
2020-10-04 14:55 ` Michael Walle
2020-10-04 15:10 ` Heinrich Schuchardt
2020-10-04 15:40 ` Tom Rini
2020-09-23 17:53 ` Mark Kettenis
2020-09-23 18:51 ` Heinrich Schuchardt
2020-09-23 19:02 ` Tom Rini
2020-09-23 20:01 ` Heinrich Schuchardt
2020-09-23 20:23 ` Tom Rini
2020-09-23 20:58 ` Heinrich Schuchardt
2020-09-23 21:09 ` Tom Rini
2020-09-23 20:38 ` Michael Walle
2020-09-23 21:01 ` Heinrich Schuchardt
2020-09-23 17:21 ` Heinrich Schuchardt
2020-09-23 17:28 ` Tom Rini
2020-09-24 6:53 ` Michael Walle
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=4098208.1601022997@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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