Re: How to kick a secondary watchdog? (Re: [PATCH 1/3] watchdog: sync linux-omap changes)

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Alan Cox
Date: Tuesday, September 23, 2008 - 3:39 am

> Some omap devices like Nokia 770, N800 and N810 have also a secondary

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
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH 0/3] omap watchdog updates, Felipe Balbi, (Fri Sep 19, 6:14 pm)
[PATCH 1/3] watchdog: sync linux-omap changes, Felipe Balbi, (Fri Sep 19, 6:14 pm)
[PATCH 2/3] watchdog: another ioremap() fix, Felipe Balbi, (Fri Sep 19, 6:14 pm)
[PATCH 3/3] watchdog: cleanup a bit omap_wdt.c, Felipe Balbi, (Fri Sep 19, 6:14 pm)
Re: [PATCH 1/3] watchdog: sync linux-omap changes, Wim Van Sebroeck, (Mon Sep 22, 11:22 am)
Re: [PATCH 1/3] watchdog: sync linux-omap changes, Russell King - ARM Linux, (Mon Sep 22, 12:13 pm)
Re: [PATCH 1/3] watchdog: sync linux-omap changes, Wim Van Sebroeck, (Tue Sep 23, 1:39 am)
Re: How to kick a secondary watchdog? (Re: [PATCH 1/3] wat ..., Alan Cox, (Tue Sep 23, 3:39 am)