quoted

quoted

Still use IRQF_SHARED for the usb interrupt, but:
* The IRQ handler in ehci-mxs, that's set in hc_driver.irq would be
always
returning IRQ_NONE.
* The IRQ handler in imx-otg would call the callback registered via
imx_otg_set_irq_handler() only if the port was actually in host mode

The interrupt which is registered by hcd core is usb_hcd_irq, it will

call

quoted

ehci_irq. The hc_driver.irq is included in usb_hcd_irq.

Hm, that's correct. I'll dive in and see if there's any other way around.
I
think I saw IRQF_DISABLED somewhere there, but that might be just some
phantom.
Either way, is this direction I'm taking the correct one (have irq
handler in
imx-otg and send IRQs to gadget/host drivers from there)?

Sorry for late as I can't see this email at my inbox.
If you can handle hcd irq well, I think it is correct direction. 


 

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html