Hi Marc, > > Bottom line: Yes, there is hardware available that can only be pinged > > and not be stopped, but No, Userspace needs the start/stop and ping > > functionality so that a watchdog daemon can work correctly (which is > > important because some watchdog daemons also do application testing. > > Right, but if the hardware doesn't support this functionality it seems > better to have the core deal with this rather than requiring the driver > to implement empty operations. As said, should indeed become part of the core, but the core needs to be able to handle multiple devices and then this becomes more complex (because some devices need and and other's don't). Coming back to now: if the driver incorporates the timer (like all other devices that can be started but not stopped once started do), then the start and stop functions are not empty. The timer (with the example that I prepared as part of the generic code) is not so difficult and will be a good solution for the time being. (Unless Dmitry Artamonow's comment about the fact that the watchdog could perhaps be started and stopped is correct... This should be investigated first imho). Kind regards, Wim. -- 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
