public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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 16:01:33 +0200	[thread overview]
Message-ID: <20090929160133.2423cd9e@marrow.netinsight.se> (raw)
In-Reply-To: <73173D32E9439E4ABB5151606C3E19E202EF7E9608@SC-VEXCH1.marvell.com>

On Tue, 29 Sep 2009 06:45:44 -0700
Prafulla Wadaskar <prafulla@marvell.com> wrote:

> > 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.
> 
> Its good to have watchdog, it will be very useful for some applications.
> But I don't think we should do it at u-boot level.
> Secondly If it is supported on Kirkwood platforms in Linux,
> then the same can be triggered from OS too.

Sure, it's just nice to have it running when Linux is started, so that
the board is properly rebooted if it hangs during kernel startup. And
in the same way as a watchdog can be useful for other boards, it should
be useful for Kirkwood-based ones.

> In u-boot I didn't find much watchdog implementation for other arm architectures.

Well, you pointed at at91sam9_wdt.c, which I believe is for an ARM :-)

> > 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.
> 
> newly added code for Kirkwood may not, we need to check and add

It works fine for me at least. I don't think any of the kirkwood code
has delays of several seconds so far :-). And again, boards which don't
need it or don't want to use it doesn't need to turn the watchdog on -
it will simply be compiled out in that case.

> > > 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.
> 
> I think you should follow the same method to keep it as "add Kirkwood watchdog driver"

Sorry, I'm not sure what this comment means. Do you mean to move it out
of timer.c? I put it there since it uses the timer registers and is
really just a special use of the built-in timer support.

// Simon

  parent reply	other threads:[~2009-09-29 14:01 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
2009-09-29 13:45     ` Prafulla Wadaskar
2009-09-29 13:59       ` Stefan Roese
2009-09-29 14:01       ` Simon Kagstrom [this message]
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=20090929160133.2423cd9e@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