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.
Joshua Emele (4):
cpufreq: OMAP: if an iva clock name is specified, load iva resources
cpufreq: OMAP: for omap3 devices, specify the iva clock name
cpufreq: OMAP: ensure the iva coprocessor is at the same opp as the
mpu
cpufreq: OMAP: scale the iva coprocessor if available
drivers/cpufreq/omap-cpufreq.c | 113 +--
1 files changed, 95 insertions(+), 18 deletions(-)
--
1.7.6.5
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
