bootcounter_ram: Flush dcache after data is written into SDRAM
This patch adds a call to flush_dcache_range() to bootcount_store() to make sure, that the bootcounter data (including the patterns) is written to memory. Without this, platforms with dcache enabled may not have the bootcounter updated upon reset. Signed-off-by: Stefan Roese <sr@denx.de> Cc: Valentin Longchamp <valentin.longchamp@keymile.com>
This commit is contained in:
parent
d9b2678e0a
commit
20adda4cf8
|
@ -35,6 +35,9 @@ void bootcount_store(ulong a)
|
||||||
writel(patterns[i % NBR_OF_PATTERNS],
|
writel(patterns[i % NBR_OF_PATTERNS],
|
||||||
&save_addr[i + OFFS_PATTERN]);
|
&save_addr[i + OFFS_PATTERN]);
|
||||||
|
|
||||||
|
/* Make sure the data is written to RAM */
|
||||||
|
flush_dcache_range((ulong)&save_addr[0],
|
||||||
|
(ulong)&save_addr[REPEAT_PATTERN + OFFS_PATTERN]);
|
||||||
}
|
}
|
||||||
|
|
||||||
ulong bootcount_load(void)
|
ulong bootcount_load(void)
|
||||||
|
|
Loading…
Reference in New Issue