On 02/22/2016 12:32 PM, Gregor Boirie wrote: > On 02/21/2016 09:08 PM, Jonathan Cameron wrote: >> On 19/02/16 19:18, Gregor Boirie wrote: >>> From: Grégor Boirie <gregor.boirie@xxxxxxxxxx> >>> >> Hi Gregor. >> >> You certainly have some unusual requirements - or perhaps you are >> simply the first person to show up with them here! > I would give preference to 2nd option :) >>> Add a sysfs file entry for each interrupt trigger instance allowing >>> userspace to : >>> * poll for interrupt events ; >> Why? > On our platform, several sensors are driven by a dedicated "real-time" > CPU (bare-metal context). This CPU interrupts Linux in a periodic manner > which in turn wakes a user process up to perform sensor fusion. > This sysfs poll support allows the user process to explictly wait for > this dedicated CPU interrupt to fetch data located in RAM then process > them. So you are only using the IIO trigger in this setup, but no buffers or devices? If you just want to forward the interrupt to userspace UIO might be the better solution in this case: https://www.kernel.org/doc/htmldocs/uio-howto/about.html - Lars -- 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
