Re: [PATCH] staging: iio: trigger: Use standard attr for sampling frequency

From: Jonathan Cameron
Date: Sat Mar 14 2015 - 13:26:46 EST

On 12/03/15 08:40, Lars-Peter Clausen wrote:
> On 03/12/2015 09:16 AM, Octavian Purdila wrote:
>> On Wed, Mar 11, 2015 at 6:36 PM, Daniel Baluta <daniel.baluta@xxxxxxxxx> 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@xxxxxxxxx>
>>> ---
>>> 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).
Just to add to this, the rtc timer stuff was a nasty hack a long time
ago to allow use of additional periodic timers available on the pxa72x.
At one point I had a rtc driver that exposed these. There was discussion
at the time about more generic 'additional timer' support in the kernel
but no one ever took the job on. The blackfin timer driver was a later
approach to handling the same sort of timers.

In more recent times, the periodic timer element of the RTC framework
has become entirely simulated anyway with no use made of true periodic
interrupts any more. As such its a totally silly approach to getting
us a periodic trigger. Perhaps we should just drop it now. Previously
we have kept it around on the basis the hrt trigger was always on the
way, but does anyone actively use it?


> There is the hrtimer trigger
> (
> 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:
> - Lars

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at