On Tue, 6 Nov 2012, Jean Pihet wrote: > On Tue, Nov 6, 2012 at 1:01 AM, Kevin Hilman > <khilman@xxxxxxxxxxxxxxxxxxx> wrote: > > > FYI... I just ran across what appears to be the same bug on 3430/n900 > > during suspend/resume testing. With CPUidle enabled, this happens every > > time. > > > > Reverting the I2C QoS patch makes it work again. > > That makes sense with CPU_IDLE enabled and suspend. ... > For the records here are the patches that have been submitted to > support the OMAP PM QoS: > - func power states [1], > - OMAP PM QoS support [2], which includes the latency figures update > and which depends on [1], > - the conversion of I2C to PM QoS [3], > - the removal of the old no-op OMAP PM API [4], which depends on [3], > > The chicken-and-egg problem is clearly visible since [3] depends on [2]. Well it's definitely time for a revert, then. #3 should not have been sent until #2 was merged. Will send this in a new thread, please ack it. - 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
