From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Babic Date: Thu, 26 Mar 2015 09:27:26 +0100 Subject: [U-Boot] [PATCH] watchdog/imx_watchdog: do not set WCR_WDW In-Reply-To: <5513BD12.6030301@linutronix.de> References: <1425401143-2647-1-git-send-email-bigeasy@linutronix.de> <5512D9F7.2040601@denx.de> <5513BD12.6030301@linutronix.de> Message-ID: <5513C2EE.4030408@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 Hi Sebastian, On 26/03/2015 09:02, Sebastian Andrzej Siewior wrote: > On 03/25/2015 04:53 PM, Stefano Babic wrote: >> On 03/03/2015 17:45, Sebastian Andrzej Siewior wrote: >>> with WCR_WDW set, the watchdog won't trigger if we bootet linux and idle >>> around while the watchdog is not triggered. It seems the timer makes >>> progress very slowly if at all. I managed to remain 20minutes alive >>> while the timeout was set to 60secs. It reboots within 60secs if I start >>> a busyloop in userland (something like "while (1) { }"). >>> >>> While I don't see a reason why the WDT should not be running while the >>> CPU is in idle, I'm dropping this bit. >>> >>> Signed-off-by: Sebastian Andrzej Siewior >>> --- >> >> Applied to u-boot-imx, thanks ! > > Thanks. What just came to mind: In case you do suspend-to-mem. Would > the watchdog trigger then? I am not sure and I have no way to test? I have also not tested, but in my understanding this is ruled by the WDZST. This is also a write-once bit, and suspend the watchdog timer during low power modes. Best regards, Stefano Babic -- ===================================================================== DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de =====================================================================