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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080923113929.3691e51e@lxorguk.ukuu.org.uk>
Date:	Tue, 23 Sep 2008 11:39:29 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Tony Lindgren <tony@...mide.com>
Cc:	Wim Van Sebroeck <wim@...ana.be>,
	Russell King - ARM Linux <linux@....linux.org.uk>,
	Felipe Balbi <me@...ipebalbi.com>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	"George G. Davis" <gdavis@...sta.com>, Alan Cox <alan@...hat.com>,
	Felipe Balbi <felipe.balbi@...ia.com>
Subject: Re: How to kick a secondary watchdog? (Re: [PATCH 1/3] watchdog:
 sync linux-omap changes)

> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/