On 18/06/15 07:15, simon@xxxxxxxxxxxxx wrote: > >>> I have further advanced the patch to include reading via buffer, but I'm >>> having trigger 'conceptual' problems getting my head around the HID >>> device >>> issuing an interrupt when a input report is received. Looking at >>> iio_dummy_event and iios_sysfs for inspiration.... >> You can skip the triggers. It's not obligatory, you can push directly >> into a buffer. >> Triggers are nice for 'data ready' type signals (which is closest to what >> we >> have here) if you might want to hang other sensors off the timing (so read >> on demand ADCs etc. They aren't actually 'required' as such. > > After a bit of poking around I got the triggers working as well, I can > self trigger and even trigger another (iio-dummy) device. > > However I couldn't trigger two devices at the same time from a single > trigger, is this normal for IIO? You should be able to. Defaults limit it to 2 per trigger, in Kconfig it is "Maximum number of consumers per trigger". Any chance that has the value 1 for your build? Otherwise, if you can do a bit of debugging to find out where things get stuck, that would be great. Can you bring up the buffers with the trigger attached or is it failing before that? After that it would just be a case of chasing in your trigger driver to see if it gets reenabled correctly after the first trigger. > > > Next is a little code clean-up and I'll post what I have for some more > comments, Cool. -- To unsubscribe from this list: send the line "unsubscribe linux-input" in
