From: Nishanth Menon <n...@ti.com> As per OMAP5 TRM, phy_fast_dll_lock is meant for simulations only. '0' is supposed to be used for normal operations. So, use 0.
Signed-off-by: Nishanth Menon <n...@ti.com> --- drivers/memory/emif.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/memory/emif.h b/drivers/memory/emif.h index bfe08ba..574fdfb 100644 --- a/drivers/memory/emif.h +++ b/drivers/memory/emif.h @@ -82,7 +82,7 @@ #define EMIF_DLL_SLAVE_DLY_CTRL_100_MHZ_AND_LESS_ATTILAPHY 0xFF /* DDR_PHY_CTRL_1 values for EMIF4D5 INTELLIPHY combination */ -#define EMIF_DDR_PHY_CTRL_1_BASE_VAL_INTELLIPHY 0x0E084200 +#define EMIF_DDR_PHY_CTRL_1_BASE_VAL_INTELLIPHY 0x0E084000 #define EMIF_PHY_TOTAL_READ_LATENCY_INTELLIPHY_PS 10000 /* TEMP_ALERT_CONFIG - corresponding to temp gradient 5 C/s */ -- 1.7.9.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
