Lines Matching refs:that

14 So what does this document describe? It describes the API that can be used by
15 WatchDog Timer Drivers that want to use the WatchDog Timer Driver Core
16 Framework. This framework provides all interfacing towards user space so that
17 the same code does not have to be reproduced each time. This also means that
19 (operations) that control the watchdog timer (WDT).
23 Each watchdog timer driver that wants to use the WatchDog Timer Driver Core
69 * ops: a pointer to the list of watchdog operations that the watchdog supports.
79 * status: this field contains a number of status bits that give extra
101 It is important that you first define the module owner of the watchdog timer
122 * start: this is a pointer to the routine that starts the watchdog timer
130   driver supporting this hardware needs to make sure that a start and stop
132   that regularly sends a keepalive ping to the watchdog timer hardware.
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
142   start function to restart the watchdog timer hardware. And that's also what
159 * get_timeleft: this routines returns the time that's left before a reset.
160 * ref: the operation that calls kref_get on the kref of a dynamically
162 * unref: the operation that calls kref_put on the kref of a dynamically
166   if a command is not supported. The parameters that are passed to the ioctl
170 bit-operations. The status bits that are defined are:
179   has been sent (so that we can support the magic close feature).
185   any watchdog_ops, so that you can be sure that no operations (other then