> Hi, > Trying to get started with iio and having problems with the iio_dummy > module. I don't have real iio hardware on this machine (or any other). Ah, figured it out. Confusion between events and triggers. You can make fake triggers with -- # modprobe iio_dummy # modprobe iio-trig-sysfs # cd /sys/bus/iio/devices # echo 1 > iio_sysfs_trigger/add_trigger # cat trigger0/name > iio\:device0/trigger/current_trigger # echo 100 > iio\:device0/buffer/length # echo 1 > iio\:device0/scan_elements/in_voltage0_en # echo 1 > iio\:device0/buffer/enable # echo 1 > trigger0/trigger_now -- Now I can see a line for each trigger occurrence. -- # hexdump -v -e '16/1 "%02x " "\n"' < /dev/iio\:device0 07 00 ea d9 00 88 ff ff 9a 81 97 31 6e 8c e6 13 07 00 ea d9 00 88 ff ff 03 28 10 99 6e 8c e6 13 07 00 ea d9 00 88 ff ff b1 84 0d cd 6e 8c e6 13 07 00 ea d9 00 88 ff ff 79 84 6d f9 6e 8c e6 13 07 00 ea d9 00 88 ff ff f5 04 df 23 6f 8c e6 13 07 00 ea d9 00 88 ff ff ea fd e1 4c 6f 8c e6 13 -- Data is buffered while there is no consumer, and outputs any 'stored' samples once the consumer (hexdump) is started. Looking good, Simon. -- 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
