* Paul Walmsley <[EMAIL PROTECTED]> [080508 11:33]: > On Thu, 8 May 2008, Tony Lindgren wrote: > > > 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? > > IRQ 56 is the TWL4030 I2C1 IRQ. Seems strange that there would be no > handler for it after i2c_omap has initialized...
Well if the I2C register access hangs, nothing will be able to reset the twl4030 interrupt registers when an interrupt happens. Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
