From: Simon Kagstrom <simon.kagstrom@netinsight.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm:kirkwood: Add hardware watchdog support for Marvell Kirkwood boards
Date: Tue, 29 Sep 2009 10:28:46 +0200 [thread overview]
Message-ID: <20090929102846.2040875e@marrow.netinsight.se> (raw)
In-Reply-To: <73173D32E9439E4ABB5151606C3E19E202EF7E9507@SC-VEXCH1.marvell.com>
On Mon, 28 Sep 2009 19:16:16 -0700
Prafulla Wadaskar <prafulla@marvell.com> wrote:
> But do you really need Watchdog support for u-boot?
Paranoia really has no limits :-). The main objective for me personally
is to have the watchdog on when Linux starts, but if there is a risk
(for whatever reason) that U-boot hangs, it would also help there.
> Because if you want to use the watchdog, you will need to keep it running in
> Entire code.
That's fine, the code is already sprinkled with WATCHDOG_RESET() in
many places (which calls hw_watchdog_reset()). Also note that this
patch doesn't actually turn it on, you'll have to call
kw_watchdog_init() first to do that.
> Secondly Pls have a look at drivers/watchdog/at91sam9_wdt.c and its implementation,
> This will be a good way of implementation.
Well, I did look at that, and I believe the implementation is fairly
similar.
What I wonder about in that context is the use of hw_watchdog_init(). I
first thought this was generic, but it's not exported via watchdog.h
(like hw_watchdog_reset()). I think it would be nice to have a generic
interface which exports
void hw_watchdog_init(unsigned long timeout_ms);
to initialize the watchdog and timeout. The timeout would be a bit
crude since hardware have limits to how long the timeouts would be, but
anyway.
Another good feature would be a command-line interface to turn it on
and configure it, i.e., something like
watchdog on 5000 # Set timeout to 5000 ms
watchdog off # Turn off (if possible)
// Simon
next prev parent reply other threads:[~2009-09-29 8:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 7:06 [U-Boot] [PATCH] arm:kirkwood: Add hardware watchdog support for Marvell Kirkwood boards Simon Kagstrom
2009-09-28 12:36 ` Tom
2009-09-28 13:36 ` Simon Kagstrom
2009-09-28 14:28 ` Tom
2009-09-29 2:16 ` Prafulla Wadaskar
2009-09-29 8:28 ` Simon Kagstrom [this message]
2009-09-29 13:45 ` Prafulla Wadaskar
2009-09-29 13:59 ` Stefan Roese
2009-09-29 14:01 ` Simon Kagstrom
2009-10-28 8:17 ` Simon Kagstrom
2009-10-28 9:24 ` Prafulla Wadaskar
2009-10-28 9:53 ` Simon Kagstrom
2009-10-28 11:34 ` Prafulla Wadaskar
2009-10-28 12:44 ` Simon Kagstrom
2009-10-28 12:57 ` Prafulla Wadaskar
2009-10-28 13:05 ` Simon Kagstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090929102846.2040875e@marrow.netinsight.se \
--to=simon.kagstrom@netinsight.net \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox