On Mon, Aug 29, 2016 at 7:48 PM, Jonathan Cameron <jic23@xxxxxxxxxx> wrote: > On 25/08/16 13:37, Linus Walleij wrote: >> On Sun, Aug 21, 2016 at 8:32 PM, Jonathan Cameron <jic23@xxxxxxxxxx> wrote: >> The pattern (support both native hardware trigger and >> say HRTimer) emerge in other sensors too, including the whole >> suite of ST MEMS sensors. Not being able to also use HRTimer >> was reported as a bug when I was working on it so it definately >> is a widespread problem. >> >> I think what I would like to do to alleviate the situation is to >> make the IIO core aware of whether the device is using its >> own trigger or some other trigger. So in the trigger callback >> we can do something like >> >> if (iio_using_own_trigger(indio_dev)) >> ... >> else >> ... >> >> I can try to take a stab at it and prepend this patch with that. >> Would that be interesting? > > Would be interesting to see what it gains us. I suspect you > are right in thinking this would be very useful. I'm trying this on top of the series as a stand-alone thing. It also affects the already in-tree ST Sensors so might as well keep it separate, also given that it's uncertain if it'll go anywhere. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
