From mboxrd@z Thu Jan 1 00:00:00 1970 From: richard@nod.at (Richard Weinberger) Date: Mon, 27 Jan 2014 10:23:17 +0100 Subject: Handling interrupts in spidev In-Reply-To: <1390814505.58456.YahooMailNeo@web125701.mail.ne1.yahoo.com> References: <1390739101.73437.YahooMailNeo@web125705.mail.ne1.yahoo.com> <1390801028.48573.YahooMailNeo@web125705.mail.ne1.yahoo.com> <52E601DC.2040008@nod.at> <1390814505.58456.YahooMailNeo@web125701.mail.ne1.yahoo.com> Message-ID: <52E62585.1040001@nod.at> To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org Am 27.01.2014 10:21, schrieb Amit Mahadik: > Thanks for your input. But I dont want to block the read call. Also I dont want to miss the interrupts. Look how other drivers/programs deal with that... Thanks, //richard > Regards, > Amit. > > > On Monday, 27 January 2014 12:22 PM, Richard Weinberger 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 at kernelnewbies.org > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > >