On 02/05/2016 01:03 PM, Kyle Roeschley wrote:
On Fri, Feb 05, 2016 at 02:27:20PM -0600, Josh Cartwright wrote:
On Thu, Feb 04, 2016 at 07:28:03PM -0600, Kyle Roeschley wrote:
When first powering on, the NI 903x/913x watchdog starts in boot mode.
If not switched from boot mode to user mode within 30 seconds of power
on, the device status LED indicates an unrecoverable error. While before
this was handled automatically, now add a module parameter to disable
this behavior.
In order to still have a useful watchdog, also add a R/W sysfs attribute
`mode' which can be used to switch the watchdog mode from boot to user
mode (but not user to boot mode).
Hmm. Instead of an attribute, why don't we just ensure the watchdog is
in "user" mode in start()?
Josh
Seems like a good idea, except for the fact that we then lose a way to query
the current watchdog mode. Maybe we could only enable the `mode' attribute
(and possibly make it read-only) when auto_mode_switch is set to false?
If the system is still running after 30 seconds, it is in user mode.
So your query would have to be pretty quick. If you want to know if the
watchdog is running, which might be more important for the user,
you could check the 'state' attribute instead.
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
