Here's an edit on the WDIOC_SETTIMEOUT ioctl:
If the watchdog has a configurable timeout, then this is how and
where it gets set (other than module load or kernel command line).
The passed argument is the new timeout in seconds. Watchdogs
with a granularity that does not allow the new timeout must set
the timeout to the next greater allowable timeout. The watchdog
must never fire in less than the passed timeout. After setting
the new timeout, the ioctl copies the actual timeout in seconds
back to userspace. This allows userspace to know what the
timeout really is.
Life's Little Instruction Book #306
"Take a nap on Sunday afternoons."
Joel Becker Senior Member of Technical Staff Oracle Corporation E-mail: firstname.lastname@example.org Phone: (650) 506-8127 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/