Hi Guenter, On Tue, Jul 05, 2016 at 08:33:35AM -0700, Guenter Roeck wrote: > On 07/05/2016 06:22 AM, Stefan Christ wrote: > >Triggering the watchdog faster than T_WDMIN=256ms leads to resets of the > >da9063 chip. The datasheet says that the watchdog must only be triggered > >in the timeframe T_WDMIN to T_WDMAX. The T_WDMAX is configured in the > >driver. > > > >This problem was already mentioned in the patch: > > > > http://comments.gmane.org/gmane.linux.watchdog/1708 > > > >You also could say that this behavior is a feature. When the userspace > >goes wild, triggering the watchdog to fast, the system is reseted. But > >there is currently no information in the watchdog ABI to report a > >minimum wait time between two watchdog heartbeats. > > > > There isn't ? What is the problem with min_hw_heartbeat_ms which was > introduced exactly for that purpose ? > Ah your right. Sorry, I didn't noticed it. I'm sending a v2 patch for it. Thanks. Mit freundlichen Grüßen / Kind regards, Stefan Christ > Thanks, > Guenter > -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
