aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/watchdog/watchdog-kernel-api.txt
diff options
context:
space:
mode:
authorWim Van Sebroeck <wim@iguana.be>2011-07-22 14:58:54 -0400
committerWim Van Sebroeck <wim@iguana.be>2011-07-28 04:01:12 -0400
commit017cf0805105496ab1880e236cb3e4bf156fb915 (patch)
treef6889e009ddba78c5c5d1965d0dae77f4fb5edd8 /Documentation/watchdog/watchdog-kernel-api.txt
parent014d694e5d59e4219803cd14deaae496d86e4910 (diff)
watchdog: WatchDog Timer Driver Core - Add Magic Close feature
Add support for the Magic Close feature to the WatchDog Timer Driver Core framework. Signed-off-by: Alan Cox <alan@lxorguk.ukuu.org.uk> Signed-off-by: Wim Van Sebroeck <wim@iguana.be> Acked-by: Arnd Bergmann <arnd@arndb.de> Acked-by: Wolfram Sang <w.sang@pengutronix.de>
Diffstat (limited to 'Documentation/watchdog/watchdog-kernel-api.txt')
-rw-r--r--Documentation/watchdog/watchdog-kernel-api.txt7
1 files changed, 7 insertions, 0 deletions
diff --git a/Documentation/watchdog/watchdog-kernel-api.txt b/Documentation/watchdog/watchdog-kernel-api.txt
index acdee39fb08..41d552698ad 100644
--- a/Documentation/watchdog/watchdog-kernel-api.txt
+++ b/Documentation/watchdog/watchdog-kernel-api.txt
@@ -127,6 +127,13 @@ bit-operations. The status bits that are defined are:
127* WDOG_DEV_OPEN: this status bit shows whether or not the watchdog device 127* WDOG_DEV_OPEN: this status bit shows whether or not the watchdog device
128 was opened via /dev/watchdog. 128 was opened via /dev/watchdog.
129 (This bit should only be used by the WatchDog Timer Driver Core). 129 (This bit should only be used by the WatchDog Timer Driver Core).
130* WDOG_ALLOW_RELEASE: this bit stores whether or not the magic close character
131 has been sent (so that we can support the magic close feature).
132 (This bit should only be used by the WatchDog Timer Driver Core).
133
134Note: The WatchDog Timer Driver Core supports the magic close feature. To use
135the magic close feature you must set the WDIOF_MAGICCLOSE bit in the options
136field of the watchdog's info structure.
130 137
131To get or set driver specific data the following two helper functions should be 138To get or set driver specific data the following two helper functions should be
132used: 139used: