Lines Matching refs:timer

18 a watchdog timer driver then only needs to provide the different routines
19 (operations) that control the watchdog timer (WDT).
23 Each watchdog timer driver that wants to use the WatchDog Timer Driver Core
31 The watchdog_register_device routine registers a watchdog timer device.
35 The watchdog_unregister_device routine deregisters a registered watchdog timer
68   additional information about the watchdog timer itself. (Like it's unique name)
70 * timeout: the watchdog timer's timeout value (in seconds).
71 * min_timeout: the watchdog timer's minimum timeout value (in seconds).
72 * max_timeout: the watchdog timer's maximum timeout value (in seconds).
80   information about the status of the device (Like: is the watchdog timer
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
124   The routine needs a pointer to the watchdog timer device structure as a
126 * stop: with this routine the watchdog timer device is being stopped.
127   The routine needs a pointer to the watchdog timer device structure as a
129   Some watchdog timer hardware can only be started and not be stopped. The
131   routine is being provided. This can be done by using a timer in the driver
132   that regularly sends a keepalive ping to the watchdog timer hardware.
134 Not all watchdog timer hardware supports the same functionality. That's why
137 * ping: this is the routine that sends a keepalive ping to the watchdog timer
139   The routine needs a pointer to the watchdog timer device structure as a
142   start function to restart the watchdog timer hardware. And that's also what
143   the watchdog timer driver core does: to send a keepalive ping to the watchdog
144   timer hardware it will either use the ping operation (when available) or the
149 * status: this routine checks the status of the watchdog timer device. The
152   timer device. It returns 0 on success, -EINVAL for "parameter out of range"
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
182   If this bit is set then the watchdog timer will not be able to stop.
190   timer device) you can either: