It is found that system is not very stable with current 1GHz OPP configuration
(a...@1g, i...@880m, v...@1.31v) and it has been recommended to
use below configuration for stable 1GHz OPP.
(a...@1g, i...@800m, v...@1.35v).
Signed-off-by: Vishwanath BS <vishwanath...@ti.com>
---
diff --git a/arch/arm/mach-omap2/cpufreq34xx.c
b/arch/arm/mach-omap2/cpufreq34xx.c
index c453ec5..189c42e
--- a/arch/arm/mach-omap2/cpufreq34xx.c
+++ b/arch/arm/mach-omap2/cpufreq34xx.c
@@ -82,7 +82,7 @@ static struct omap_opp_def __initdata
omap36xx_mpu_rate_table[] = {
/* OPP3 - OPP-Turbo */
OMAP_OPP_DEF(false, 800000000, 1260000),
/* OPP4 - OPP-SB */
- OMAP_OPP_DEF(false, 1000000000, 1310000),
+ OMAP_OPP_DEF(false, 1000000000, 1350000),
/* Terminator */
OMAP_OPP_DEF(0, 0, 0)
};
@@ -104,7 +104,7 @@ static struct omap_opp_def __initdata
omap36xx_dsp_rate_table[] = {
/* OPP3 - OPP-Turbo */
OMAP_OPP_DEF(false, 660000000, 1260000),
/* OPP4 - OPP-SB */
- OMAP_OPP_DEF(false, 875000000, 1310000),
+ OMAP_OPP_DEF(false, 800000000, 1350000),
/* Terminator */
OMAP_OPP_DEF(0, 0, 0)
};
--
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
