From: "Marc Reilly" <marc@cpdesign.com.au>
To: 'Sascha Hauer' <s.hauer@pengutronix.de>,
'Erwin Rol' <mailinglists@erwinrol.com>
Cc: barebox@lists.infradead.org
Subject: RE: Watchdog support
Date: Mon, 17 May 2010 20:57:18 +1000 [thread overview]
Message-ID: <013001caf5af$ba7b5fd0$2f721f70$@cpdesign.com.au> (raw)
In-Reply-To: <20100517083633.GI31199@pengutronix.de>
Hi,
> > 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.
IMHO the use of 'reset' with watchdogs is ambiguous. Typically, the primary
use is to _prevent_ the watchdog from attacking you (the system resetting),
but sometimes it is also used to _cause_ the reset, so that the system
restarts properly. (suicide and resurrection. I suck at analogies.)
So, that said, I'd suggest watchdog_ping() or watchdog_feed() as functions
for the first usage, and save watchdog_reset() for the second. (or
watchdog_trigger_reset() etc)
Just my 0.02c. In the end, I don't think I'll be the one writing it, so I
won't be the one designing it. :)
> For the latter case you don't have another choice but to scatter the code
with
> RESET_WATCHDOG macros like U-Boot does.
Or put it in the timer interrupt :)
That was, of course, a joke.
Cheers
Marc
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2010-05-17 10:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 10:14 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
2010-05-17 10:57 ` Marc Reilly [this message]
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='013001caf5af$ba7b5fd0$2f721f70$@cpdesign.com.au' \
--to=marc@cpdesign.com.au \
--cc=barebox@lists.infradead.org \
--cc=mailinglists@erwinrol.com \
--cc=s.hauer@pengutronix.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