Lines Matching refs:this

11 with a WatchDog Timer. If you want to know this then please read the following
14 So what does this document describe? It describes the API that can be used by
24 must #include <linux/watchdog.h> (you would have to do this anyway when
32 The parameter of this routine is a pointer to a watchdog_device structure.
36 device. The parameter of this routine is the pointer to the registered
39 The watchdog device structure looks like this:
65 * parent: set this to the parent device (or NULL) before calling
79 * status: this field contains a number of status bits that give extra
110 The simplest (and usually sufficient) implementation of this is to:
113 3) Call kref_init on this kref *before* calling watchdog_register_device()
114 4) Define a ref operation calling kref_get on this kref
115 5) Define a unref operation calling kref_put on this kref
117  * Do not kfree() the struct holding both, the last kref_put will do this!
122 * start: this is a pointer to the routine that starts the watchdog timer
126 * stop: with this routine the watchdog timer device is being stopped.
130   driver supporting this hardware needs to make sure that a start and stop
137 * ping: this is the routine that sends a keepalive ping to the watchdog timer
141   Most hardware that does not support this as a separate function uses the
149 * status: this routine checks the status of the watchdog timer device. The
151 * set_timeout: this routine checks and changes the timeout of the watchdog
153   and -EIO for "could not write value to the watchdog". On success this
159 * get_timeleft: this routines returns the time that's left before a reset.
164 * ioctl: if this routine is present then it will be called first before we do
171 * WDOG_ACTIVE: this status bit indicates whether or not a watchdog timer device
173   set this status bit (Note: when you register the watchdog timer device with
174   this bit set, then opening /dev/watchdog will skip the start operation)
175 * WDOG_DEV_OPEN: this status bit shows whether or not the watchdog device
178 * WDOG_ALLOW_RELEASE: this bit stores whether or not the magic close character
181 * WDOG_NO_WAY_OUT: this bit stores the nowayout setting for the watchdog.
182   If this bit is set then the watchdog timer will not be able to stop.
183 * WDOG_UNREGISTERED: this bit gets set by the WatchDog Timer Driver Core
193     (this will set the value the same as CONFIG_WATCHDOG_NOWAYOUT) or
209 arguments of this function are the watchdog device where you want to add the
213 The argument of this function is the watchdog device where you want to retrieve
225 then use this function to set the user "preferred" timeout value.