On 05/19/2015 01:26 AM, Timo Kokkonen wrote:
It is possible that the specified watchdog timeout value is shorter than the time it takes for the watchdog daemon to start up and take over the watchdog device. This is problem if WATCHDOG_BOOT_RUNNING is the desired watchdog policy. Add a new timeout value that specifies how long kernel should extend the timeout by pinging the watchdog hardware. This option still ensures a watchdog reset takes place in case watchdog daemon fails to open the device, but gives more freedom in case user space is slow starting up and watchdog might trigger prematurely.
Same as my other comment. This should not be a configuration option (just like the default timeout isn't one). I really think we are going into the wrong direction. I can understand the point why it makes sense to have a devicetree parameter for this, and we should focus (have focused) on getting it accepted. Now we have to deal with kernel configuration options, and we get more and more distracted from the real goal. Guenter -- To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
