Hi, On Tuesday 06 November 2012 07:47 PM, Joshua Emele wrote:
The iva coprocessor, available on some omap platforms, shares a voltage domain with the mpu. If cpufreq is active and the mpu processor is scaled down, the iva coprocessor should also be scaled. The goal is to make sure we do not ramp down the voltage on the domain and affect clocking on the iva coprocessor leading to a dsp crash. I only have access to an omap3evm-ish device, so I do not know what the iva clock name is for omap24xx and omap44xx. This detail can be added later if the general approach is approved. I have tested a version of this patch against the linux-3.3 kernel, so this my attempt at a forward port against the current mainline. I have based my patch series against linux-omap-pm/pm-next.
How about making use of CPUFREQ notifiers to handle it. I don't like this series since it adds multi-media co-processor scaling into the CPUFreq driver. Regards Santosh -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
