Vladimir - before I forget, could you try to wrap emails to around 
80 characters per line.  Otherwise we end up with really tricky
to read thread when some are doing so and others aren't!

On 07/08/15 17:10, Vladimir Barinov wrote:

Hi Lars,

On 07.08.2015 16:45, Lars-Peter Clausen wrote:

quoted

Hi,

On 07/29/2015 02:57 PM, Vladimir Barinov wrote:

quoted

Support triggered events.

This is useful for chips that don't have their own interrupt sources.
It allows to use generic/standalone iio triggers for those drivers.

Thanks for the patch. Can you describe in more detail how
INDIO_EVENT_TRIGGERED differs from the INDIO_BUFFER_TRIGGERED. By just
looking at the source code I don't understand quite why it is necessary.

This is needed for the case when iio buffer is not used and used only
iio event.

The difference to INDIO_BUFFER_TRIGGERED is that for triggered buffer
the trigger poll function is attached (using
iio_trigger_attach_poll_func) only in industrialio-buffer.c using
number of steps/conditions starting by issuing 1 to buffer/enable
sysfs path.

For chips that do not use iio buffer but use only iio events the
iio_trigger_attach_poll_func never called.

In case of using INDIO_BUFFER_TRIGGERED the poll func is
attached/detached via industrialio-buffer.c In case of using
INDIO_EVENT_TRIGGERED the poll func is attached/detached via
industrialio-trigger.c during set/change the current trigger.

Regards, Vladimir

You've convinced Lars and I agree with his argument that this
is a sensible addition to IIO.

quoted

Thanks,
- Lars

-- 
To unsubscribe from this list: send the line "unsubscribe linux-iio" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html