From: "Getz, Robin" <robin.getz@analog.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Jonathan Cameron <jic23@cam.ac.uk>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
Marten Svanfeldt <marten@intuitiveaerial.com>
Subject: Re: [PATCH v3] staging:iio: trigger: Add hrtimer trigger
Date: Wed, 18 Apr 2012 07:58:34 -0400 [thread overview]
Message-ID: <201204180758.34751.robin.getz@analog.com> (raw)
In-Reply-To: <4F8C4F17.5040101@metafoo.de>
On Mon 16 Apr 2012 12:55, Lars-Peter Clausen pondered:
> On 04/16/2012 06:17 PM, Jonathan Cameron wrote:
> > Lars-Peter Clausen <lars@metafoo.de> wrote:
> >> From: Marten Svanfeldt <marten@intuitiveaerial.com>
> >>
> >> This patch adds a IIO trigger driver which uses a highres timer to
> >> provide a
> >> frequency based trigger.
> >
> > Fine as it stands but same issue arises as we had with userspace trigger
> > still. What are we doing registering a pure software element not
> > associated to any specific hardware via a platform device. Why not do it
> > on userspace asking for one as we do with the sysfs file based trigger?
>
> I suppose this is a general question how we want to mange our triggers in
> general. None of the other existing trigger drivers does direct IO access
> and just use existing infrastructure. They could all be easily be
> instantiated by writing a string or number to a sysfs file. So where do we
> draw the line?
Isn't there an issue of accuracy? the timing accuracy of sysfs/userspace is
non-existant with respect to what you need to do in most of these cases.
-Robin
next prev parent reply other threads:[~2012-04-18 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 13:03 [PATCH v3] staging:iio: trigger: Add hrtimer trigger Lars-Peter Clausen
2012-04-16 16:17 ` Jonathan Cameron
2012-04-16 16:55 ` Lars-Peter Clausen
2012-04-18 11:58 ` Getz, Robin [this message]
2012-04-18 12:45 ` Jonathan Cameron
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=201204180758.34751.robin.getz@analog.com \
--to=robin.getz@analog.com \
--cc=jic23@cam.ac.uk \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=marten@intuitiveaerial.com \
/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.