From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from bh-25.webhostbox.net ([208.91.199.152]:39671 "EHLO bh-25.webhostbox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754219AbbAUXfr (ORCPT ); Wed, 21 Jan 2015 18:35:47 -0500 Received: from mailnull by bh-25.webhostbox.net with sa-checked (Exim 4.82) (envelope-from ) id 1YE4oL-001Fmv-Da for linux-watchdog@vger.kernel.org; Wed, 21 Jan 2015 23:35:46 +0000 Message-ID: <54C037CC.2070707@roeck-us.net> Date: Wed, 21 Jan 2015 15:35:40 -0800 From: Guenter Roeck MIME-Version: 1.0 To: Doug Anderson , Wim Van Sebroeck CC: Heiko Stuebner , Lunxue Dai , Jisheng Zhang , Dinh Nguyen , linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/2] watchdog: dw_wdt: pat the watchdog before enabling it References: <1421882243-3631-1-git-send-email-dianders@chromium.org> In-Reply-To: <1421882243-3631-1-git-send-email-dianders@chromium.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-watchdog-owner@vger.kernel.org List-Id: linux-watchdog@vger.kernel.org On 01/21/2015 03:17 PM, Doug Anderson wrote: > On some dw_wdt implementations the "top" register may be initted to 0 > at bootup. In such a case, each "pat" of the watchdog will reset the > timer to 0xffff. That's pretty short. > > The input clock of the wdt can be any of a wide range of values. On > an rk3288 system, I've seen the wdt clock be 24.75 MHz. That means > each tick is ~40ns and we'll count to 0xffff in ~2.6ms. > > Because of the above two facts, it's a really good idea to pat the > watchdog after initting the "top" register properly and before > enabling the watchdog. If you don't then there's no way we'll get the > next heartbeat in time. > > Signed-off-by: Doug Anderson > --- Reviewed-by: Guenter Roeck