>-----Original Message----- >From: Paul Walmsley [mailto:paul@xxxxxxxxx] >Sent: Friday, December 12, 2008 3:13 PM >To: Pandita, Vikram >Cc: Grazvydas Ignotas; Steve Sakoman; Tony Lindgren; David Brownell; me@xxxxxxxxxxxxxxx; Kridner, >Jason; sakari.poussa@xxxxxxxxx; Jeff Steele; linux-omap >Subject: RE: status of USB on omap35xx ? > >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? It should be submitted to usb tree and that activity will start soon. > > >- Paul -- 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
