From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932209AbbCGLGu (ORCPT ); Sat, 7 Mar 2015 06:06:50 -0500 Received: from down.free-electrons.com ([37.187.137.238]:43106 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755025AbbCGLGs (ORCPT ); Sat, 7 Mar 2015 06:06:48 -0500 Date: Sat, 7 Mar 2015 12:06:45 +0100 From: Alexandre Belloni To: Pavel Machek Cc: Sylvain Rochet , Peter Zijlstra , Mark Rutland , Boris Brezillon , Alessandro Zummo , Mike Turquette , Jason Cooper , "rtc-linux@googlegroups.com" , Len Brown , Greg Kroah-Hartman , "linux-pm@vger.kernel.org" , "Rafael J. Wysocki" , "linux-kernel@vger.kernel.org" , Nicolas Ferre , Wim Van Sebroeck , "linux-serial@vger.kernel.org" , Jean-Christophe Plagniol-Villard , Thomas Gleixner , Jiri Slaby , "linux-arm-kernel@lists.infradead.org" , "linux-watchdog@vger.kernel.org" Subject: Re: [PATCH v2 5/6] watchdog: at91sam9: request the irq with IRQF_NO_SUSPEND Message-ID: <20150307110645.GW3989@piout.net> References: <1425287898-15093-1-git-send-email-boris.brezillon@free-electrons.com> <1425287898-15093-6-git-send-email-boris.brezillon@free-electrons.com> <20150304183809.GD22156@leverpostej> <20150305095306.3db98ac8@bbrezillon> <20150305105308.GA13617@leverpostej> <20150305121723.1da0d016@bbrezillon> <20150305115307.GA14093@leverpostej> <20150307091846.GN23367@worktop.ger.corp.intel.com> <20150307102056.GA28436@gradator.net> <20150307103939.GA17964@amd> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150307103939.GA17964@amd> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/03/2015 at 11:39:39 +0100, Pavel Machek wrote : > > The Atmel watchdog can't be stopped once it's started. This is actually > > very useful so we can reset if suspend or resume failed, the only > > drawback is that you have to wake up from time to time (e.g. by using > > the RTC/RTT) to clear the watchdog and then go back to sleep ASAP. > > Yeah. So you do "echo mem > /sys/power/state", and few seconds/minutes > after watchdog kills the system. But you did not ask for dead system, > you asked for suspend. > > And while that behaviour is useful for you, I don't think it is > exactly useful behaviour, nor it is the behaviour user would expect. > I think you misunderstood, that is exactly the expected behaviour. This is hardware defined. Once the watchdog is started, nobody can stop it. Trying to change the mode register will result in a reset of the SoC. It is documented in the datasheet and any user wanting another behaviour is out of luck. So basically, when using a watchdog, you have to wake up every 15-16s to restart it. -- Alexandre Belloni, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com