Re: Problem with request_irq

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

 




> >
> 
> This is request_irq :
> 
> int request_irq(unsigned int irq, irq_handler_t handler,
>                 unsigned long irqflags, const char *devname, void *dev_id)
> 
> See that second argument? it needs a 'irq_handler_t' as its second
> argument.
> You are passing it a 'me1400_info_type *' as the second argument.
> So, just like the compiler tells you; you are "passing argument 2 of
> 'request_irq' from incompatible pointer type".
> 

This is true. But dev_id is only available at the other side, this is the name of the struct in the intrinsic irq-handler. In my case this is "me1400_isr". dev_id has a void-pointer and that means (I think) that you have to interchange your own declared device-struct trought this interface? Otherwise I do not know where I could get this dev_id. It is not the pci_dev struct or whatever?

On the "request_irq-side" I put a self declared struct into the interface, and on the other side, the irq-handler this is now the struct dev_id?

Gruss Christian

-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kanns mit allen: http://www.gmx.net/de/go/multimessenger

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ


[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