[...] > > A quick test of this series on 3430/n900 shows that it prevents PER > retention. I see CM_FCLKEN_PER=0000c000 (debounce clock for GPIO banks > 3 & 4 are still enabled.) > > Can you retest with debounce enabled on one of the GPIOs for one of your > platforms? With one of the module debounce clock enabled it doesn't go to retention. Later I disabled all modules debounce clock. It doesn't to retention either. So this is same as your observation. I am surprised what has happened now. The only thing I could recollect is few patches to solve LDO and OMAP1 issues while testing before posting. I will investigate further. -- Tarun > > Kevin > > -- 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