All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Erwin Rol <mailinglists@erwinrol.com>
Cc: barebox@lists.infradead.org
Subject: Re: Watchdog support
Date: Mon, 17 May 2010 10:36:33 +0200	[thread overview]
Message-ID: <20100517083633.GI31199@pengutronix.de> (raw)
In-Reply-To: <4BECF779.50306@erwinrol.com>

Hi Erwin,

On Fri, May 14, 2010 at 09:10:49AM +0200, Erwin Rol wrote:
> Marc Reilly wrote:
>> Hi Erwin,
>>
>>> does barebox have any watchdog support ?
>>
>> I think the answer to your question is really dependent on what platform you
>> are using, and exactly what you want the watchdog to do.
>
> Platform does not really matter here, I mean does barebox trigger the  
> watchdog if it is doing lengthy operations like writing flash to prevent  
> it from being reset in the middle of the operation. That has little to  
> do with if the platform has a watchdog or not.
>
> So let me changes the question a bit;
>
> Does barebox have a standard API to trigger and program a watchdog ?

No, we do not have this atm.

Are you looking for real watchdog support, i.e. 'reset watchdog when my
system is in a sane state' or do you have a piece of hardware on which
you have to reset the watchdog frequently because you can't disable it
in software?

For the first case I propose a 'watchdog' command with an underlying
reset_watchdog() function which resets the watchdog.
For the latter case you don't have another choice but to scatter the
code with RESET_WATCHDOG macros like U-Boot does.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2010-05-17  8:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-13 10:14 Watchdog support Erwin Rol
2010-05-14  2:16 ` Marc Reilly
2010-05-14  7:10   ` Erwin Rol
2010-05-14  8:33     ` Marc Reilly
2010-05-17  8:36     ` Sascha Hauer [this message]
2010-05-17 10:57       ` Marc Reilly

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=20100517083633.GI31199@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=mailinglists@erwinrol.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.