summaryrefslogtreecommitdiff
path: root/arch
diff options
context:
space:
mode:
authorVladimir Zapolskiy <vz@mleia.com>2016-11-28 00:15:13 +0200
committerTom Rini <trini@konsulko.com>2016-12-02 21:32:39 -0500
commitee47c4cb2b3413b3ee0edd2207de46d715b2628c (patch)
tree87e4f1be1c973597b8d69f50bf4818ae1fc39ce4 /arch
parentfd184b9c8003811d797dfc64af6375ecb43cc79d (diff)
downloadu-boot-imx-ee47c4cb2b3413b3ee0edd2207de46d715b2628c.zip
u-boot-imx-ee47c4cb2b3413b3ee0edd2207de46d715b2628c.tar.gz
u-boot-imx-ee47c4cb2b3413b3ee0edd2207de46d715b2628c.tar.bz2
sh4: cache: correct dcache flush to invalidate with write-back
In common usecases flush_cache() assumes both cache invalidation and write-back to memory, thus in flush_dcache_range() implementation change SH4 cache write-back only instruction 'ocbwb' with cache purge instruction 'ocbp', according to the User's Manual there should be no performance penalty for that. Note that under circumstances only cache invalidation is expected from flush_cache() call, in these occasional cases the current version of flush_cache() works, which is a wrapper over invalidate_dcache_range() at the moment, this will be fixed in the following change. Signed-off-by: Vladimir Zapolskiy <vz@mleia.com>
Diffstat (limited to 'arch')
-rw-r--r--arch/sh/cpu/sh4/cache.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/sh/cpu/sh4/cache.c b/arch/sh/cpu/sh4/cache.c
index e1ee970..b3e5fd5 100644
--- a/arch/sh/cpu/sh4/cache.c
+++ b/arch/sh/cpu/sh4/cache.c
@@ -97,7 +97,7 @@ void flush_dcache_range(unsigned long start, unsigned long end)
start &= ~(L1_CACHE_BYTES - 1);
for (v = start; v < end; v += L1_CACHE_BYTES) {
- asm volatile ("ocbwb %0" : /* no output */
+ asm volatile ("ocbp %0" : /* no output */
: "m" (__m(v)));
}
}