Hi,
I started going through the ohci-omap.c file and trying to make
sense of the interfaces. I am stuck at the point where the interrupt
handler is hooked with request_irq in the function,
usb_hcd_omap_probe. Interrupt handler that is hooked is "usb_hcd_irq"
which in turn calls driver->irq which turns out to be ohci_irq.
What is confusing to me is that OMAP USB is based on MUSB HDRC
OTG core and its registers are not OHCI compatible (am I correct??).
So I expected a OMAP MUSB specific interrupt handler and low level
functions to handle the MUSB registers for interrupts/FIFO handling
etc., Can some one point me to where this stuff happens?
Also in a board view, when system is getting initialized, first
usb_init function in drivers/core/usb.c is called and then respective
HCD driver init methods are called??
Regards,
Meher
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
