Thanks for your input. But I dont want to block the read call. Also I dont want to miss the interrupts.
Regards,
Amit.
On Monday, 27 January 2014 12:22 PM, Richard Weinberger <richard@xxxxxx> wrote:
Am 27.01.2014 06:37, schrieb Amit Mahadik:
> Thanks for the reply Richard.
> The interrupt is not a GPIO pin. I have read something about UIO (userspace I/O).
> Also, I want the operation to be asynchronous. Any pointer to such mechanism will be very helpful.
Using UIO you can also catch an interrupt in userspace.
You can have a read() which blocks till data is available.
Thanks,
//richard
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> Thanks for the reply Richard.
> The interrupt is not a GPIO pin. I have read something about UIO (userspace I/O).
> Also, I want the operation to be asynchronous. Any pointer to such mechanism will be very helpful.
Using UIO you can also catch an interrupt in userspace.
You can have a read() which blocks till data is available.
Thanks,
//richard
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
