summaryrefslogtreecommitdiff
path: root/board
diff options
context:
space:
mode:
authorMichael Walle <michael@walle.cc>2022-05-31 00:02:07 +0300
committerPeng Fan <peng.fan@nxp.com>2022-06-20 10:52:45 +0300
commit6bdda4b2003fadbcbcc28a1d395ec1f6f6557539 (patch)
tree4fd174441b93ae79f561109b68f714bfa7d6227d /board
parent2a9cf320afb051f40a4bbb98aa9a6b1a94332d27 (diff)
downloadu-boot-6bdda4b2003fadbcbcc28a1d395ec1f6f6557539.tar.xz
board: sl28: set CPO value
With a 8GiB memory board, it seems that the "very unlikely event" of a DDR initialization with non-optimal values are not really that unlikely. It happens in about every other reboot. As described in erratum A-009942, preset the DEBUG_28 register with an optimal value. The value iself depends on the memory configuration of the board, but the used value seems to work well for all variants. Signed-off-by: Michael Walle <michael@walle.cc>
Diffstat (limited to 'board')
-rw-r--r--board/kontron/sl28/ddr.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/board/kontron/sl28/ddr.c b/board/kontron/sl28/ddr.c
index 41426996ab..d75b23e54c 100644
--- a/board/kontron/sl28/ddr.c
+++ b/board/kontron/sl28/ddr.c
@@ -54,6 +54,9 @@ static fsl_ddr_cfg_regs_t __maybe_unused ddr_cfg_regs = {
.ddr_cdr1 = 0x80040000,
.ddr_cdr2 = 0x0000bc01,
+
+ /* Erratum A-009942, set optimal CPO value */
+ .debug[28] = 0x00700040,
};
int fsl_initdram(void)