Bin Meng 723b43daec 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>		2017-09-15 08:05:10 -04:00
..
blk_legacy.c	blk: Remove various places that do flush cache after read	2017-09-15 08:05:10 -04:00
blk-uclass.c	blk: Remove various places that do flush cache after read	2017-09-15 08:05:10 -04:00
blkcache.c	drivers: block: add block device cache	2016-04-01 17:18:27 -04:00
ide.c	block: ide: Don't bother to create BLK device if no CDROM inserted	2017-09-10 12:27:40 -04: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
sandbox.c	blk: dm: make blk_create_device() take a number of block instead of a size	2017-09-11 21:43:58 -06:00
systemace.c	dm: systemace: Add driver-mode block-device support	2016-05-17 09:54:43 -06:00