From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wolfgang Denk Date: Fri, 25 Sep 2020 10:36:37 +0200 Subject: [PATCH 2/2] watchdog: add watchdog behavior configuration In-Reply-To: <20200924131931.GF14816@bill-the-cat> References: <20200923164527.26894-1-michael@walle.cc> <20200923164527.26894-2-michael@walle.cc> <8ba6107a460b8647@bloch.sibelius.xs4all.nl> <20200923171409.GT14816@bill-the-cat> <8070fb73-d42b-fa66-98a6-a2b9926b2d3f@gmx.de> <20200923173504.GV14816@bill-the-cat> <20200924131931.GF14816@bill-the-cat> Message-ID: <4098208.1601022997@gemini.denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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