Ed Endejan wrote: > Gadiyar, Anand <gadiyar@...> writes: > > > > Sorry I'm late to this thread - I've been out of office all of June and > > am only catching up on list emails now. > > > > @Ed, > > > > Which OMAP board is this being tested on? It appears to be an OMAP3 device, > > but I'm not sure if it's a 3430 or a 3630. > > > > Are you running any heavy video/camera tests at the same time on the board? > > > > OMAP3430 devices and early OMAP3630 devices are affected by a bug that > > can cause a controller lockup if video/camera subsystems of the OMAP are > > stressed. This was fixed in OMAP3630 ES1.2. See [1] for a description > > of the issue. > > > > If you are affected by this bug, I'm afraid the only known way to recover > > is by a softreset of the host controller. > > > > Would it be possible for you to test this on a new beagleboard XM or a > > pandaboard (or a board with newer silicon)? > > > > Thanks, > > Anand > > The tests were performed on a proprietary board using an > OMAP3525, revision 3.1 silicon. > > The video/camera ports are not being used, so it seems that should not be an > issue. But can you reference an Advisory number for the issue you describe? I'd > like to review the errata to see if it is somehow relevant. Sure - the advisory number and link to a public errata document were in the link to the older thread that I pointed out earlier. I'll quote them here too. Errata ID i572 is the bug I had in mind. See section 3.1.1.200 of this document: http://focus.ti.com/lit/er/sprz278f/sprz278f.pdf I don't think we've come across anything else resembling the issue you describe. - Anand -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
