Hello Oliver, I am sorry, but I think I don't understand , You said: >A USB driver never will request an irq. Interrupt handling is done in > the core usb layer. Individual drivers have no business there.
but in the zd1211 driver (not the rewrite version) I found this call to request an irq: request_irq(dev->irq, &zd1205_intr, SA_SHIRQ, dev->name, dev) Also when looking in the linux tree, I see some request_irq() calls in USB drivers, for exmaple in some drivers under usb/gadgaets, and more. Can you please elaborate a bit ? What do you mean by saying "A USB driver never will request an irq"? -- John On 6/4/06, Oliver Neukum <[EMAIL PROTECTED]> wrote: > Am Sonntag, 4. Juni 2006 18:29 schrieb John Que: > > I had noticed that the zd1211 driver does call request_irq() in > > zd1205_open(), > > file zd1205.c; grepping for request_irq() in the rewrite driver yields > > no results. > > (I looked at the rewrite version from a week ago but in this point it > > is probably the > > same). > > Why is this so ? I assume that the softmac layer does not call > > request_irq() on > > behalf of the driver because this is not supposed to be like it, as I > > understand > > its functionality. Can anybody briefly calrify this point ? > > A USB driver never will request an irq. Interrupt handling is done in > the core usb layer. Individual drivers have no business there. > > Regards > Oliver > _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel