Hi Richard, trying to fix this problem and have a few questions. On Wed, 8 Oct 2008, Woodruff, Richard wrote: > None of the module local OCP registers are being setup properly. A > write of a 0x2 kills other settings. If after this operation the SSYC > reg will say: > -Forced Idle > -Locally gate I+F clock on ocp-segment idle request > -wake up disabled > > If it is left this way what can happen is when L4/L3 clock stop partial > idle is broadcast, this module will ack and gate its clocks. This will > result in you dropping data. Or if the data was sent ok, but clock stop > happens, you won't be able to wake the system properly as you've cleared > the local wakeup generation. The result will be a timeout. Okay, so for OMAP3, the workarounds in the omapzoom tree to change the SYSC.CLOCKACTIVITY bits when the clocks are enabled and disabled are not necessary? It sounds like the only thing that is needed on OMAP3 is to make sure that the SYSCONFIG register is set properly after a software reset? > On OMAP2 I2C wasn't hooked properly into PRCM for handshake so it needed > a workaround. The same isn't true for OMAP3. Treating the two as if > they are the same with respect to power is false. Could you explain further about which workaround this is? OMAP2 I2C does not appear to have any SYSC bits exposed other than SOFTRESET? - 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
