On Wed, 16 May 2012, Tomi Valkeinen wrote: > JFYI, I also tested changing DISPC's SYSCONFIG:CLOCKACTIVITY, which, to > me, sounds a bit related to dpll autoidle. By default it's 0, "interface > and functional clocks can be switched off". I tested the three other > values, but none of them had any effect. As I understand it (which could very well be mistaken), the CLOCKACTIVITY bits are only useful in situations where we'd like to allow the interconnect to idle, but keep the functional clock of the IP block (or subsystem) running. Right now, we control an IP block's interface clock and functional clock together, so CLOCKACTIVITY should probably always be 0. But for drivers that want to do more fine-grained clock control, or if we create some notion of an "autonomous IP block" in our integration layer for devices that can function without its interconnect, it might be worth exploring whether it is worthwhile to change those bits. - 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
