Bin Meng 010034028f UPSTREAM: 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. Change-Id: I8f04c721432753b34e85b19616a0b42d83a633eb 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> Signed-off-by: Kever Yang <kever.yang@rock-chips.com> (cherry picked from commit 723b43daec7ee2ddb600cfcb9b0253d4a71c3915)		2018-01-16 18:16:48 +08:00
..
Kconfig	dm: mmc: Allow disabling driver model in SPL	2017-08-01 11:58:00 +09:00
Makefile	block: Drop the ftide020 driver	2017-09-03 15:30:35 -04:00
blk-uclass.c	UPSTREAM: blk: Remove various places that do flush cache after read	2018-01-16 18:16:48 +08:00
blk_legacy.c	UPSTREAM: blk: Remove various places that do flush cache after read	2018-01-16 18:16:48 +08:00
blkcache.c	…
ide.c	block: ide: Don't bother to create BLK device if no CDROM inserted	2017-09-10 12:27:40 -04:00
sandbox.c	…
systemace.c	…