> Hello Vikram, > > On Sat, 13 Dec 2008, Pandita, Vikram wrote: > > > >From: Paul Walmsley [mailto:paul@xxxxxxxxx] > > > > > >Were you able to get USB remote wakeup or auto-suspend working on > > >ehci-omap.c with the 3430SDP? > > > > For remote-wakeup: > > There was a long discussion with USBHOST IP vendor. We were observing a device disconnect on a remote-wakeup as well as host initiated wakeup. > > > > It turned out to be an issue with the IP block and will be fixed in 3430 ES3.1 finally. > > And a software workaround for waiting for USB micro frame boundary. > > Now the workaround has been done in USB EHCI stack code which is not the best way ... > > > > Take a look at Zoom GIT tree for the reference implementation: > > > http://git.omapzoom.com/?p=omapkernel.git;a=commitdiff;h=baa196583f4af08d15da0389fed8f9005b0f812d > > Thanks for the info; that's quite helpful. Do you happen to know if there > are any projects ongoing inside TI to send patches for the existing > ehci-omap.c driver in linux-omap? > > > - Paul Yes, but only if Tony will accept them. And he won't - it will only increase the diff between linux-omap and mainline. The EHCI driver should actually go to linux-usb. If you look at the list archives, you will find that I had said I would do that - ages ago. Unfortunately I have not been able to do that so far. It's high on the priority list however. Also, that reference patch is not complete either. It uses ehci_get_frame() which returns the current frame number, instead of the EHCI FrameIndex register value (which is all we need - so we end up waiting longer). Also, it's a while loop without a timeout, which is bad. This patch does get EHCI suspend-resume working however, so feel free to take it if you need it. It's a hack for now. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
