Hi Cliff, On Tue, 12 Mar 2013, Cliff Brake wrote: > On Mon, Feb 20, 2012 at 12:58 PM, Richard Watts <rrw@xxxxxxxxxxxxx> wrote: > > > > There is an erratum in DM3730 which results in the > > EHCI USB PLL (DPLL5) not updating sufficiently frequently; this > > leads to USB PHY clock drift and once the clock has drifted far > > enough, the PHY's ULPI interface stops responding and USB > > drops out. This is manifested on a Beagle xM by having the attached > > SMSC9514 report 'Cannot enable port 2. Maybe the USB cable is bad?' > > or similar. > > > > The fix is to carefully adjust your DPLL5 settings so as to > > keep the PHY clock as close as possible to 120MHz over the long > > term; TI SPRZ319e gives a table of such settings and this patch > > applies that table to systems with a 13MHz or a 26MHz clock, > > thus fixing the issue (inasfar as it can be fixed) on Beagle xM > > and Overo Firestorm. > > > > Signed-off-by: Richard Watts <rrw@xxxxxxxxxxxxx> > > Has any more testing been done with this? We're running into a > situation where the USB subsystem crashes in a beagleboard xM after > running for a couple hours to a day. A USB camera is running > continuously during this time. The error message typically something > like: > > [ 2817.415710] hub 1-0:1.0: port 2 disabled by hub (EMI?), re-enabling... > [ 2817.422607] usb 1-2: USB disconnect, device number 2 > [ 2817.427886] usb 1-2.1: USB disconnect, device number 3 > [ 2817.441986] usb 1-2.4: USB disconnect, device number 4 > [ 2817.450134] usb 1-2.5: USB disconnect, device number 5 Are you in a position to test whether the patch works for you? I'd still like to find someone whose USB problem is fixed by the patch and is willing to try a slight modification of it before applying... - 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
