From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Tony Lindgren <tony@atomide.com>
Cc: Wim Van Sebroeck <wim@iguana.be>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Felipe Balbi <me@felipebalbi.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
"George G. Davis" <gdavis@mvista.com>, Alan Cox <alan@redhat.com>,
Felipe Balbi <felipe.balbi@nokia.com>
Subject: Re: How to kick a secondary watchdog? (Re: [PATCH 1/3] watchdog: sync linux-omap changes)
Date: Tue, 23 Sep 2008 11:39:29 +0100 [thread overview]
Message-ID: <20080923113929.3691e51e@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20080923102159.GD5102@atomide.com>
> Some omap devices like Nokia 770, N800 and N810 have also a secondary
> watchdog on the retu chip connected via cbus. This watchdog needs
> to be kicked as it cannot be disabled.
If you have a chip that runs continually then the easiest approach I've
seen is to have kernel code that manages it and the watchdog driver just
keeps a time value indicating whether it should be refreshed.
We've got a few watchdogs like that in the watchdog tree.
If it can be user started but then not stopped that is fine - the API
doesn't require you can stop it
next prev parent reply other threads:[~2008-09-23 10:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-20 1:14 [PATCH 0/3] omap watchdog updates Felipe Balbi
2008-09-20 1:14 ` [PATCH 1/3] watchdog: sync linux-omap changes Felipe Balbi
2008-09-20 1:14 ` [PATCH 2/3] watchdog: another ioremap() fix Felipe Balbi
2008-09-20 1:14 ` [PATCH 3/3] watchdog: cleanup a bit omap_wdt.c Felipe Balbi
2008-09-22 18:22 ` [PATCH 1/3] watchdog: sync linux-omap changes Wim Van Sebroeck
2008-09-22 19:13 ` Russell King - ARM Linux
2008-09-23 8:39 ` Wim Van Sebroeck
2008-09-23 10:22 ` How to kick a secondary watchdog? (Re: [PATCH 1/3] watchdog: sync linux-omap changes) Tony Lindgren
2008-09-23 10:39 ` Alan Cox [this message]
2008-09-23 11:19 ` Wim Van Sebroeck
2008-09-23 11:32 ` Tony Lindgren
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=20080923113929.3691e51e@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@linux-foundation.org \
--cc=alan@redhat.com \
--cc=felipe.balbi@nokia.com \
--cc=gdavis@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=me@felipebalbi.com \
--cc=tony@atomide.com \
--cc=wim@iguana.be \
/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
all inboxes | Powered by JetHome®