linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Octavian Purdila <octavian.purdila@intel.com>,
	Daniel Baluta <daniel.baluta@intel.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Peter Meerwald <pmeerw@pmeerw.net>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: iio: trigger: Use standard attr for sampling frequency
Date: Thu, 12 Mar 2015 09:40:12 +0100	[thread overview]
Message-ID: <550150EC.5080100@metafoo.de> (raw)
In-Reply-To: <CAE1zot+us4bP2n1xQkFdAvJ3iAWwqTFgMK4SNZbmugPD_nB_Lg@mail.gmail.com>

On 03/12/2015 09:16 AM, Octavian Purdila wrote:
> On Wed, Mar 11, 2015 at 6:36 PM, Daniel Baluta <daniel.baluta@intel.com> wrote:
>>
>> As written in Documentation/ABI/testing/sysfs-bus-iio the trigger
>> attribute for sampling frequency should be sampling_frequency.
>>
>> Fix this for iio-trig-periodic-rtc module in order to prepare it
>> for moving out of staging.
>>
>> Signed-off-by: Daniel Baluta <daniel.baluta@intel.com>
>> ---
>> Jonathan, this module is very useful for devices that do not have
>> an interrupt pin.
>>
>> We are working on drivers for such devices and would be very nice to
>> move this driver in advance to the IIO non-staging location.
>>
>> What do you say?
>>
>
> Hmm, I wonder what are the advantages of using RTC timers. Couldn't we
> use a regular kernel timer instead?

The long term plan is to get rid of the RTC timer trigger due to its various 
limitations (poor resolution, etc).

There is the hrtimer trigger 
(https://github.com/analogdevicesinc/linux/blob/xcomm_zynq/drivers/staging/iio/trigger/iio-trig-hrtimer.c) 
but we haven't agreed on a proper interface yet how to instantiate the 
hrtimer trigger.

Check the ml archive for the various discussions on it: 
http://marc.info/?l=linux-iio&w=2&r=1&s=hrtimer&q=b

- Lars

  reply	other threads:[~2015-03-12  8:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 16:36 [PATCH] staging: iio: trigger: Use standard attr for sampling frequency Daniel Baluta
2015-03-12  8:16 ` Octavian Purdila
2015-03-12  8:40   ` Lars-Peter Clausen [this message]
2015-03-12 12:48     ` Daniel Baluta
2015-03-14 17:21       ` Jonathan Cameron
2015-03-15 20:34         ` Daniel Baluta
2015-03-15 20:49           ` Jonathan Cameron
2015-03-15 20:52             ` Daniel Baluta
2015-03-18 15:04         ` Daniel Baluta
2015-03-18 16:47           ` Lars-Peter Clausen
2015-03-18 17:21             ` Daniel Baluta
2015-03-18 17:25               ` Lars-Peter Clausen
2015-03-21 11:44                 ` Jonathan Cameron
2015-03-14 17:26     ` 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=550150EC.5080100@metafoo.de \
    --to=lars@metafoo.de \
    --cc=daniel.baluta@intel.com \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=octavian.purdila@intel.com \
    --cc=pmeerw@pmeerw.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).