Re: Handling interrupts in spidev

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks Richard. One more question. If I register an SPI irq  struct spi_board_info spi_board_info[] structure in machine board.c file; then the request irq api and irq handler should be written in board.c file or in the spidev driver.

Regards,
Amit.


On Monday, 27 January 2014 2:54 PM, Richard Weinberger <richard@xxxxxx> wrote:
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 <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 <mailto:Kernelnewbies@xxxxxxxxxxxxxxxxx>
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

>
>

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux