armv7: Fix dcache writethrough policy handling
The "bufferable" bit was erroneously set for the writethrough policy making it the same as writeback. (credit to jwerner for pointing this out) Signed-off-by: David Hendricks <dhendrix@chromium.org> BUG=none BRANCH=none TEST=compiled only, writethrough isn't actually used at the moment. Change-Id: I567d57f0e522cb4b82988894ba9b4638642bf8db Reviewed-on: https://chromium-review.googlesource.com/167323 Reviewed-by: Julius Werner <jwerner@chromium.org> Tested-by: David Hendricks <dhendrix@chromium.org> Tested-by: ron minnich <rminnich@chromium.org> Commit-Queue: David Hendricks <dhendrix@chromium.org>
This commit is contained in:
parent
322338934a
commit
36cf138396
1 changed files with 1 additions and 1 deletions
|
|
@ -91,7 +91,7 @@ void mmu_config_range(unsigned long start_mb, unsigned long size_mb,
|
|||
str = "writeback";
|
||||
break;
|
||||
case DCACHE_WRITETHROUGH:
|
||||
attr = (0x3 << 10) | (1 << 3) | (1 << 2) | 0x2;
|
||||
attr = (0x3 << 10) | (1 << 3) | 0x2;
|
||||
str = "writethrough";
|
||||
break;
|
||||
default:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue