On Tue, May 28, 2013 at 09:22:18AM -0700, Guenter Roeck wrote: > On Tue, May 28, 2013 at 10:10:53AM +0200, Johannes Thumshirn wrote: > > On Mon, May 27, 2013 at 08:25:54PM +0200, Wim Van Sebroeck wrote: > > [...] > > > > + watchdog_set_drvdata(&a21_wdt, drv); > > > > > > I am missing the initialisation of the watchdog's timeout value here... > > > > This watchdog only knows two timeout values, 1s and 30s with the constraint > > that you can't go back to 30s once your in a 1s timeout without a reset of the > > CPLD. I could initially set it to 30s but that would be redundant. > > > I wonder - why bother with supporting one-second timeouts ? > > Is this realistic, ie can you guarantee that the watchdog will be pinged fast > enough to keep the system alive under all load conditions ? As far as I know > you can not even configure the watchdog application for less than 1 second > ping intervals. > > Thanks, > Guenter Well in my tests it was possible, maybe not under extremely high load. But considering the application these boards (the VME CPU board the watchdogs chip is on) are usually used by our customers, I hope they can react within a single second. Another reason why I want to support the 1s timeout is, the VxWorks BSP does it too and we don't want a Linux driver have less features than it's VxWorks counterpart, do we ;-). Just kidding. My opinion is, the hardware supports it and so should the driver, especially for the (safety critical) industrial control and automation applications our customers usually do. Just my point of view though. Regards, Johannes -- 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
