public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
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 15:59:38 +0200	[thread overview]
Message-ID: <200909291559.38963.sr@denx.de> (raw)
In-Reply-To: <73173D32E9439E4ABB5151606C3E19E202EF7E9608@SC-VEXCH1.marvell.com>

On Tuesday 29 September 2009 15:45:44 Prafulla Wadaskar 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.
> 
> 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.

I think it's perfectly legal to enable the watchdog already in U-Boot. And as 
Simon already mentioned, it has some advantages doing this as early as 
possible.

> Secondly If it is supported on Kirkwood platforms in Linux,
> then the same can be triggered from OS too.

But things could go wrong while booting Linux.
 
> In u-boot I didn't find much watchdog implementation for other arm
>  architectures.

It doesn't matter if there are many, but there are at least some. And the 
infrastructure is there. Why not use it. You don't have to enable the watchdog 
support for your boards of course. :)
 
Cheers,
Stefan

--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de

  reply	other threads:[~2009-09-29 13:59 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 [this message]
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=200909291559.38963.sr@denx.de \
    --to=sr@denx.de \
    --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