summaryrefslogtreecommitdiff
path: root/drivers/block/blk_legacy.c
diff options
context:
space:
mode:
authorBin Meng <bmeng.cn@gmail.com>2017-09-13 05:00:23 +0300
committerTom Rini <trini@konsulko.com>2017-09-15 15:05:10 +0300
commit723b43daec7ee2ddb600cfcb9b0253d4a71c3915 (patch)
tree44953c1e7fc2634c1e3ec329262d9a3332ba0453 /drivers/block/blk_legacy.c
parent6305db960447ff2d32c335de8bbd9b44cb7d6554 (diff)
downloadu-boot-723b43daec7ee2ddb600cfcb9b0253d4a71c3915.tar.xz
blk: Remove various places that do flush cache after read
All these places seem to inherit the codes from the MMC driver where a FIXME was put in the comment. However the correct operation after read should be cache invalidate, not flush. The underlying drivers should be responsible for the cache operation. Remove these codes completely. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Stefan Roese <sr@denx.de> Reviewed-by: York Sun <york.sun@nxp.com> Reviewed-by: Joe Hershberger <joe.hershberger@ni.com> Reviewed-by: Simon Glass <sjg@chromium.org> Tested-by: York Sun <york.sun@nxp.com>
Diffstat (limited to 'drivers/block/blk_legacy.c')
-rw-r--r--drivers/block/blk_legacy.c3
1 files changed, 0 insertions, 3 deletions
diff --git a/drivers/block/blk_legacy.c b/drivers/block/blk_legacy.c
index 981872ecb3..16d3bfe7f2 100644
--- a/drivers/block/blk_legacy.c
+++ b/drivers/block/blk_legacy.c
@@ -232,9 +232,6 @@ ulong blk_read_devnum(enum if_type if_type, int devnum, lbaint_t start,
if (IS_ERR_VALUE(n))
return n;
- /* flush cache after read */
- flush_cache((ulong)buffer, blkcnt * desc->blksz);
-
return n;
}