Manish Regmi wrote:
Thanks for your help,
The signal that causes the interrupt is also connected to the write
enable (start filling fifo) of the fifo, so that means
when an interrupt occurs, the fifo is being triggered to fill itself
with data from an ADC.
There is no signal to wake up the process on the wait queue because only
the interrupt
causes the fifo to be filled, there is no signal that says: the fifo is
full now.
So what i want is:
interrupt -> wait for 400 uS --> read fifo --> send fifo data to
userspace.
the only problem i have is the delay, the rest is obvious to me.
Christian.
Why don't you want to use udelay().
You have three functions to busywait for that small amount of time.
udelay, ndelay and mdelay.
othres wait at least 1 jiffy.
So, you might not have any other choice than to use udelay() :).
I cant wait 400 uS because the fifo data has to be sent through UDP
messages and the interval for the trigger signals are tight.
If there is no other solution i'll try to change the hardware.
Christian.
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/
