Hi Jan, Jan Kiszka wrote: > What is the usage model of your driver? Is there an application thread
associated to each frequency or even each channel? Or is there a single reader which gets woken up once some channel finishes the conversion? Or does the application requests a bulk of samples from multiple channels?
I want to implement this as a single reader. The only thing I've to do is to log the data from the different channels to one or more file(s).
Depending on that usage model, an alternative way to implement your driver is to let the application generate the conversion clock, i.e. let it poll the data (maybe just blocking on the conversion completion).
I'll try that.
On the other hand, if the acquisition job currently performed in rtdm_tasks is rather light-weight,
I think so, only a few small macros with bit-operations that set/read the register from the ISA-card
maybe timers would help you to reduce the overhead involved in multiple threads reading from the same device (including locking etc.). Unfortunately, an RTDM interface for direct timer usage has not yet been fully specified. Some preliminary patch hangs around on my box for quite a few months now. Do you see advantages for your scenario when using timers, i.e. executing the periodic jobs directly in the context of the timer IRQ handler? If yes, I could try to accelerate the finalisation of this patch.
There are some sensors on the serial device, too, and the event-driven programming is a very elegant way (using xeno_16550A with "rt_dev_ioctl(imu_fd, RTSER_RTIOC_WAIT_EVENT, &rx_event );". So I thought it would be nice to implement the driver for the ISA-card in a similar way.
Thanks Maggo _______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
