On 02/05/2016 11:53 AM, Josh Cartwright wrote:
On Thu, Feb 04, 2016 at 07:28:01PM -0600, Kyle Roeschley wrote:
The NI 9x3x watchdog timer has 30.72 µs resolution, so expose this
by allowing the user to set the timeout counter directly via a sysfs
attribute.
But _why_? That isn't clear to me. Why do we want a user to directly
muck with the counter value? (As opposed to working in units of time?).
In addition to that, this also messes up the watchdog core's notion of
wdd->timeout, meaning the watchdog subsystem would no longer report
the actually configured timeout value to user space.
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
