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
74 * ops: a pointer to the list of watchdog operations that the watchdog supports.
84 * status: this field contains a number of status bits that give extra
108 It is important that you first define the module owner of the watchdog timer
129 * start: this is a pointer to the routine that starts the watchdog timer
137   driver supporting this hardware needs to make sure that a start and stop
139   that regularly sends a keepalive ping to the watchdog timer hardware.
144 * ping: this is the routine that sends a keepalive ping to the watchdog timer
148   Most hardware that does not support this as a separate function uses the
149   start function to restart the watchdog timer hardware. And that's also what
166 * get_timeleft: this routines returns the time that's left before a reset.
167 * ref: the operation that calls kref_get on the kref of a dynamically
169 * unref: the operation that calls kref_put on the kref of a dynamically
173   if a command is not supported. The parameters that are passed to the ioctl
177 bit-operations. The status bits that are defined are:
186   has been sent (so that we can support the magic close feature).
192   any watchdog_ops, so that you can be sure that no operations (other then