Lines Matching full:not

11 This document does not describe what a WatchDog Timer (WDT) Driver or Device is.
12 It also does not describe the API which can be used by user space to communicate
19 the same code does not have to be reproduced each time. This also means that
85   not send a heartbeat request if WDOG_ACTIVE is set.
91   'timeout'. Not used if max_hw_heartbeat_ms is non-zero.
94   if the hardware can not tolerate lower intervals between heartbeats.
99   seconds. max_hw_heartbeat_ms must be set if a driver does not implement
150 Not all watchdog timer hardware supports the same functionality. That's why
158   Some watchdog timer hardware can only be started and not be stopped. A
159   driver supporting such hardware does not have to implement the stop routine.
165   If a watchdog driver does not implement the stop function, it must set
173   Most hardware that does not support this as a separate function uses the
177   start operation (when the ping operation is not available).
186   it is not necessary to report those bits from the driver. Also, if no status
192   and -EIO for "could not write value to the watchdog". On success this
195   because the watchdog does not necessarily have a 1 second resolution).
204   If the watchdog driver does not have to perform any action but setting the
207   If set_timeout is not provided but, WDIOF_SETTIMEOUT is set, the watchdog
216   the watchdog. It is optional because not all watchdogs support pretimeout
217   notification. The timeout value is not an absolute time, but the number of
219   -EINVAL for "parameter out of range" and -EIO for "could not write value to
225   If the watchdog driver does not have to perform any action but setting the
227   set_pretimeout is not provided but WDIOF_PRETIMEOUT is set, the watchdog
236   if a command is not supported. The parameters that are passed to the ioctl
242 * WDOG_ACTIVE: this status bit indicates whether or not a watchdog timer device
243   is active or not from user perspective. User space is expected to send
246   If this bit is set then the watchdog timer will not be able to stop.
248   running. The bit must be set if the watchdog timer hardware can not be
252   WDOG_ACTIVE is not set.
311 nowayout flag is not set.
336 the watchdog device. If watchdog pretimeout governor framework is not