From: Lars-Peter Clausen <lars@metafoo.de>
To: Ezequiel Garcia <ezequiel.garcia@imgtec.com>, linux-iio@vger.kernel.org
Cc: Jonathan Cameron <jic23@kernel.org>,
James Hartley <james.hartley@imgtec.com>,
Naidu Tellapati <Naidu.Tellapati@imgtec.com>
Subject: Re: IIO hrtimer trigger
Date: Fri, 05 Sep 2014 21:06:35 +0200 [thread overview]
Message-ID: <540A09BB.5010709@metafoo.de> (raw)
In-Reply-To: <20140905152203.42ff6868@arch>
On 09/05/2014 08:22 PM, Ezequiel Garcia wrote:
> Hello Lars,
>
> I'm picking this discussion, since we're also interested in using an hrtimer
> trigger.
>
>> On 10/06/2013 08:15 PM, Jonathan Cameron wrote:
>>> We are pretty much stuck with that for the sysfs trigger already...
>>
>> Unfortunately yes. I never liked its API and I still don't like it and we
>> have to live with it. But this doesn't mean we have to add more of the same.
>
> So the reason why the hrtimer trigger hasn't been merged in its current form is
> because we're still discussing the ABI, right?
I think the configfs documentation explains this quite well:
"Where sysfs is a filesystem-based view of kernel objects, configfs is a
filesystem-based manager of kernel objects, or config_items." [1]
>
> Can you elaborate on why you don't like the sysfs trigger API? If you can give
> me some hints I can try to cook a patch for the configfs hrtimer trigger.
That would be great. I unfortunately only have a very foggy view of how the
ABI and API should look like.
But I think the basic interface is have a toplevel iio configfs folder,
maybe a subfolder called "triggers" and than a subfolder for each software
trigger. E.g. "timer" (We shouldn't call it hrtimer cause that is just a
implementation detail). Then in those trigger folders you can do mkdir to
create a new instance of that trigger. In the folder there might be trigger
specific config settings exposed as files.
- Lars
[1] https://www.kernel.org/doc/Documentation/filesystems/configfs/configfs.txt
next prev parent reply other threads:[~2014-09-05 19:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 18:22 IIO hrtimer trigger Ezequiel Garcia
2014-09-05 19:06 ` Lars-Peter Clausen [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-09-29 19:36 Denis CIOCCA
2013-10-03 17:10 ` Lars-Peter Clausen
2013-10-06 18:15 ` Jonathan Cameron
2013-10-07 14:18 ` Lars-Peter Clausen
2014-06-18 19:47 ` Jonathan Cameron
2014-06-19 10:57 ` Lars-Peter Clausen
2014-06-19 14:42 ` 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=540A09BB.5010709@metafoo.de \
--to=lars@metafoo.de \
--cc=Naidu.Tellapati@imgtec.com \
--cc=ezequiel.garcia@imgtec.com \
--cc=james.hartley@imgtec.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
/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.