Lines Matching +full:assigned +full:- +full:resolution +full:- +full:bits

5 Last reviewed: 12-Feb-2013
10 ------------
14 file: Documentation/watchdog/watchdog-api.rst .
24 -------
82 * gov: a pointer to the assigned watchdog device pretimeout governor or NULL.
91   'timeout'. Not used if max_hw_heartbeat_ms is non-zero.
93   in milli-seconds. This value is normally 0; it should only be provided
95 * max_hw_heartbeat_ms: Maximum hardware heartbeat, in milli-seconds.
106   should define ops->restart. Priority can be changed through
109   WDIOF_* status bits).
114 * status: this field contains a number of status bits that give extra
183   status of the device is reported with watchdog WDIOF_* status flags/bits.
186   it is not necessary to report those bits from the driver. Also, if no status
187   function is provided by the driver, the watchdog core reports the status bits
191   timer device. It returns 0 on success, -EINVAL for "parameter out of range"
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).
219   -EINVAL for "parameter out of range" and -EIO for "could not write value to
235   our own internal ioctl call handling. This routine should return -ENOIOCTLCMD
239 The status bits should (preferably) be set with the set_bit and clear_bit alike
240 bit-operations. The status bits that are defined are:
299 using the module timeout parameter or by retrieving the timeout-sec property from