Understanding the USB OHCI Glue layer (OMAP)

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

 



Hi All,

The probe function of OMAP Bus Glue for USB OHCI HCD, 
(function "usb_hcd_omap_probe" in file drivers\usb\host\ohci-omap.c)
expects the HCD memory and interrupt resources to be allocated in the 
platform_device structure when it is called. 

I however could not locate any call to platform_device_register or 
platform_device_register_simple for the OHCI device (which would have
allocated
these resources), anywhere in the kernel tree. Also, the probe function
would 
not be called unless the device was registered (so it must be getting
done somewhere). 

I wish to know where the OHCI device is registered and the resources
allocated?
Am I missing something basic?

Any help in this regard is greately appreciated.

Thanks,
Sekhar Nori.

--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           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