OMAP3 clocks initialization not consistent with x-loader?
Hi,
x-loader has the following comment and if statement for all boards supporting omap36xx SoC:
----------------------cut----------------------------------------
/*
* On OMAP3630, DDR data corruption has been observed on OFF mode
* exit if the sys clock was lower than 26M. As a work around,
* OMAP3630 is operated at 26M sys clock and this internal division
* is not performed.
*/
if((is_cpu_family() != CPU_OMAP36XX) && (sys_clkin_sel > 2)) {
sr32(PRM_CLKSRC_CTRL, 6, 2, 2);/* input clock divider */
clk_index = sys_clkin_sel/2;
} else {
sr32(PRM_CLKSRC_CTRL, 6, 2, 1);/* input clock divider */
clk_index = sys_clkin_sel;
}----------------------cut----------------------------------------
U-Boot's omap3 clock initialization does not have that check for omap36xx.
Shouldn't we have it also in U-Boot to workaround that DDR data corruption issue?
Signature · 2 lines
Regards, Igor.