flush I-cache after omap_sram_push()
authorPaul Walmsley <paul@pwsan.com>
Mon, 19 Nov 2007 19:11:43 +0000 (12:11 -0700)
committerTony Lindgren <tony@atomide.com>
Fri, 23 Nov 2007 21:15:14 +0000 (13:15 -0800)
commit498c996e43219fe1bd335e1946225a84d25a9a65
treef60e1a3dcdc237f283047e969f1427fc26d0c13f
parent5e8a760e24d8325007caa4a54d7a4ff3cbb137fb
flush I-cache after omap_sram_push()

This patch implements a suggestion by Richard Woodruff
<r-woodruff2@ti.com>.  omap_sram_push() copies executable code into
SRAM memory.  Currently this happens before Linux executes anything
from the SRAM, so we don't have to worry about evicting any SRAM lines
from the I-cache.  But at some point in the future, the SRAM might be
used more dynamically, adding and removing code while the system is
running.  So we should ensure that the I-cache is clean or at
least up-to-date after the copy.

Signed-off-by: Paul Walmsley <paul@pwsan.com>
Signed-off-by: Richard Woodruff <r-woodruff2@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
arch/arm/plat-omap/sram.c