* Koen Kooi <k.kooi@xxxxxxxxxxxxxxxxxx> [080508 11:22]: > > Op 8 mei 2008, om 20:13 heeft Paul Walmsley het volgende geschreven: > > > > Hello everyone, > > > > occasionally the TWL4030 driver on the 3430SDP freaks out on boot. > > (This > > is either an ES2.0 or ES2.1, not sure.) Here's a partial console > > log with > > initcall debugging enabled. This probably happens every thirty or > > forty > > boots, I would guess. The board does boot to userspace when this > > happens. > > > > Perhaps the TWL4030 experts out there might know what's going on? > > > > <3>i2c_omap i2c_omap.1: controller timed out > > <3>i2c_omap i2c_omap.1: controller timed out > > <3>twl4030_usb: i2c write failed, line 422 > > Looks suspiciously like the symptons in > > http://code.google.com/p/beagleboard/issues/detail?id=14 This also looks similar to the earlier twl4030 hangs where access to some domains caused twl4030 to hang. If twl4030 hangs, there's no way to reset it as all control is over I2C. When twl4030 hangs, bootloader won't be able to detect the chip either unless devices is power cycled (and USB cable detached). The reason earlier was that twl4030 internal clock was not being programmed properly, and was fixed by patch 0d81cf7e804c529c58d3054c1b9bdb7b3f1dec5d. Maybe there's some twl4030 register access going on before the internal clock is programmed properly? Tony -- 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
