On Fri, Feb 20, 2009 at 11:44:25AM +0100, Anand Gadiyar wrote: > On Friday Feb 20, 2009 Grazvydas Ignotas wrote: > > On Fri, Feb 20, 2009 at 12:46 AM, Felipe Balbi <me@xxxxxxxxxxxxxxx> wrote: > > > On Thu, Feb 19, 2009 at 02:43:36PM -0800, Steve Sakoman wrote: > > >> EHCI omap driver definitely needs some work - there is machine > > >> specific stuff in there that rightfully belongs in platform data. I > > >> haven't had time to work on it :-( > > > > > > For sure, and there's still workaround for clk framework stuff that > > > should already move there. > > > > > > I'll try to start with some cleanups already during this weekend (yeah, > > > I've got no life :-p) and post as RFT asap. After the cleanups are ok, > > > then I'll start moving platform code out of there and for the clock > > > workarounds I'll need help from Paul Walmsley, probably :-) > > > > Great, I'll be watching the list and gladly test them on pandora too. > > It would be nice to have those remote wakeup issues [1] sorted out > > too. > > > > 1: http://marc.info/?l=linux-omap&m=122911571519657&w=2 > > > Sorry, that is not something that will be fixed in ES3.1. It also affects > suspend-resume, not just remote-wakeup. > > However, there is a software workaround that is being tested right now > - the one mentioned in the link does not work reliably. The new > workaround should be ready shortly (maybe after Felipe is done with > the cleanups he plans). well, it's been about 5 months since you said TI would be doing such cleanups, I've even had my patches dropped at that time because of that and till now nothing happened. About the workaround, I'd rather read the errata myself and implement it. -- balbi -- 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
