From owner-freebsd-arm@FreeBSD.ORG  Wed Nov  6 16:05:05 2013
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: freebsd-arm@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 8BD84FC0
 for <freebsd-arm@freebsd.org>; Wed,  6 Nov 2013 16:05:05 +0000 (UTC)
 (envelope-from jiashiun@gmail.com)
Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com
 [IPv6:2a00:1450:400c:c00::22c])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 2539229A6
 for <freebsd-arm@freebsd.org>; Wed,  6 Nov 2013 16:05:04 +0000 (UTC)
Received: by mail-wg0-f44.google.com with SMTP id n12so5160629wgh.35
 for <freebsd-arm@freebsd.org>; Wed, 06 Nov 2013 08:05:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:from:date:message-id:subject:to
 :cc:content-type;
 bh=vA97X7H30eB/ZZ1FTUQedelFDTiQc2KSehbLUyfQ8tU=;
 b=wAnnvGd/yN3CeonvifQZXM4F4bvsgjegP7+DcAvQY6RnVjiAYL1g5/l2D6Cq4/yrHe
 H9xXxmOfciUnIiPg0UyvaBqQUtZcm67tgpLJ43YmzRN0M7Eum9uJSiiQyHmsxtx5WaB4
 b0QPQqGba66WvnEA3Y6dDFE2uNF5AyMUbgRxnoL0PPzNzHFfDZRDgCSnl3kE0jeUpW2X
 1Wo3tyQoQD58aHoIQP6Wcgd4/YKhHcRWmXCL5ZlryiGhfb1g9URssxBXvGN7/nJuklj0
 4cpP7AlsbI7dj7zkx+TBsgcOg6oEz8/+hy1UlaP1SH5mHwcMI8o508KYTGerIYUz4l/7
 W/uQ==
X-Received: by 10.194.21.225 with SMTP id y1mr2058948wje.60.1383753903260;
 Wed, 06 Nov 2013 08:05:03 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.206.132 with HTTP; Wed, 6 Nov 2013 08:04:33 -0800 (PST)
In-Reply-To: <CAHNYxxM8MYZRBFvf3cSGB=MOM-CLMOwudJMWdzb-UwAvXK4r+g@mail.gmail.com>
References: <43584768717.406e8ebb@mail.schwarzes.net>
 <F4029D36-8C55-4617-A429-0C5A3DA31C63@bluezbox.com>
 <CAHNYxxM8MYZRBFvf3cSGB=MOM-CLMOwudJMWdzb-UwAvXK4r+g@mail.gmail.com>
From: Jia-Shiun Li <jiashiun@gmail.com>
Date: Thu, 7 Nov 2013 00:04:33 +0800
Message-ID: <CAHNYxxOzi-xFksrBtzr4m-A2WVaGkf5aakGNzUMKvGMQ2DVKcw@mail.gmail.com>
Subject: Re: raspberry pi BCM2708 hardware watchdog
To: Oleksandr Tymoshenko <gonzo@bluezbox.com>
Content-Type: text/plain; charset=UTF-8
Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>,
 Andreas Schwarz <freebsd.asc@strcmp.org>
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting FreeBSD to the StrongARM Processor <freebsd-arm.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Nov 2013 16:05:05 -0000

On Fri, Nov 1, 2013 at 3:11 AM, Jia-Shiun Li <jiashiun@gmail.com> wrote:
> I tried playing the watchdog for a while,  but it does not seem to be
> set correct timeout.
>
> I tried to set timeout to 120 seconds to test with the following
> command, but get immediate reset after around 1~2 seconds:
>

Just found out that
- watchdog(4) uses 2^N ns format for timeout value, and
- watchdog timeout value on BCM2835 is restricted to < 16 secs due to
register constraint
so for watchdog(d) users the only meaningful -t value on RPi is 1, 2,
4, and 8 seconds.

In case others may have the same question.

-Jia-Shiun.