Denis Ciocca <denis.ciocca@xxxxxxxxx> wrote: >Hi everybody, > >I write in this mailing list because I have some problems to >understand the trigger event catch and I ask for your help. > >I write a little driver for accelerometer and the core driver works, >but now I want to write trigger code. What I understand is that: > >1. register iio_trigger; >2. associate iio_trigger to iio_dev; >3. associate pollfunc with iio_alloc_pollfunc to iio_info; Buffer set up and enabled? > >when trigger occuring (in my example at hrtimers), I call >iio_trigger_poll() function and I expect which handler function >declared inside iio_alloc_pollfunc(...) is called. >This does not happen! Superficially looks correct. Verify the trigger association worked by checking current_trigger under sysfs entry for the iio device. Otherwise either post code or insert some printk statements to see where things are going. > >What I'm doing wrong? >There is some documentation about this? Kind of in code... generic_buffer.c for userspace side and dummy driver for kernel side. Text docs rotted so until someone has time to update heavily commented examples were more useful. > >Thanks, > >Denis >-- >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 -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- 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
