From: Josh Cartwright <joshc@ni.com>
To: Kyle Roeschley <kyle.roeschley@ni.com>
Cc: wim@iguana.be, linux-watchdog@vger.kernel.org
Subject: Re: [RFC 2/4] watchdog: ni9x3x_wdt: Add counter sysfs attribute
Date: Fri, 5 Feb 2016 13:53:36 -0600 [thread overview]
Message-ID: <20160205195336.GB9579@jcartwri.amer.corp.natinst.com> (raw)
In-Reply-To: <1454635683-13668-2-git-send-email-kyle.roeschley@ni.com>
[-- Attachment #1: Type: text/plain, Size: 379 bytes --]
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?).
Josh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-02-05 19:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 1:28 [RFC 1/4] watchdog: ni9x3x_wdt: Add NI 903x/913x watchdog driver Kyle Roeschley
2016-02-05 1:28 ` [RFC 2/4] watchdog: ni9x3x_wdt: Add counter sysfs attribute Kyle Roeschley
2016-02-05 19:53 ` Josh Cartwright [this message]
2016-02-06 16:35 ` Guenter Roeck
2016-02-05 1:28 ` [RFC 3/4] watchdog: ni9x3x_wdt: Add timeout_action " Kyle Roeschley
2016-02-05 20:08 ` Josh Cartwright
2016-02-05 21:13 ` Kyle Roeschley
2016-02-05 21:40 ` Josh Cartwright
2016-02-06 0:00 ` Guenter Roeck
2016-02-05 1:28 ` [RFC 4/4] watchdog: ni9x3x_wdt: Let user control watchdog mode Kyle Roeschley
2016-02-05 20:27 ` Josh Cartwright
2016-02-05 21:03 ` Kyle Roeschley
2016-02-05 21:34 ` Josh Cartwright
2016-02-06 16:42 ` Guenter Roeck
2016-02-05 19:49 ` [RFC 1/4] watchdog: ni9x3x_wdt: Add NI 903x/913x watchdog driver Josh Cartwright
2016-02-06 16:30 ` Guenter Roeck
2016-02-08 16:06 ` Kyle Roeschley
2016-02-06 16:33 ` Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160205195336.GB9579@jcartwri.amer.corp.natinst.com \
--to=joshc@ni.com \
--cc=kyle.roeschley@ni.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=wim@iguana.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.