Hello, > > it should be iio_trigger_poll_chained(), not iio_trigger_poll(), since > > this is an interrupt handler; this solves my WARN_ON() > That's not the reason, it's because you are calling it from a bottom half. > The nature of the trigger code is that it would normally be called from the > top half (as it's normally just calling a tree of other interrupt handlers > which may or may not have their own top halves.) > > The chained call is probably ok, but does limit what other devices may use > this as a trigger source. Lars-Peter had another approach that is used > in the sysfs trigger using irq_work_queues which might work here (I haven't > thought about it in much depth...) see drivers/staging/triggers/iio-trig-sysfs.c thank you for the pointer, will have a look p. -- Peter Meerwald +43-664-2444418 (mobile) -- 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
