summaryrefslogtreecommitdiff
path: root/drivers/net
diff options
context:
space:
mode:
authorPeng Fan <Peng.Fan@freescale.com>2015-02-02 15:36:43 +0800
committerPeng Fan <Peng.Fan@freescale.com>2015-04-29 14:56:32 +0800
commitfcbde55a890d42bbfac92b3b8e7b93fb59bee6b3 (patch)
tree4b33fa7f8c96e59dbf5240d3c96d1688363e6ca9 /drivers/net
parent90efa4017b2a44b3f6c84d51a9589a9011f929fa (diff)
downloadu-boot-imx-fcbde55a890d42bbfac92b3b8e7b93fb59bee6b3.zip
u-boot-imx-fcbde55a890d42bbfac92b3b8e7b93fb59bee6b3.tar.gz
u-boot-imx-fcbde55a890d42bbfac92b3b8e7b93fb59bee6b3.tar.bz2
MLK-10178-8 mmc:fsl_esdhc fix dcache issue
DCIMVAC is upgraded to DCCIMVAC for the individual processor (Cortex-A7) that the DCIMVAC is executed on. We should follow the linux dma follow. Before DMA read, first invalidate dcache then after DMA read, invalidate dcache again. With the DMA direction DMA_FROM_DEVICE, the dcache need be invalidated again after the DMA completion. The reason is that we need explicity make sure the dcache been invalidated thus to get the DMA'ed memory correctly from the physical memory. Any cache-line fill during the DMA operations such as the pre-fetching can cause the DMA coherency issue, thus CPU get the stale data. Signed-off-by: Peng Fan <Peng.Fan@freescale.com> Signed-off-by: Ye.Li <B37916@freescale.com> Signed-off-by: Nitin Garg <nitin.garg@freescale.com> Signed-off-by: Jason Liu <r64343@freescale.com> (cherry picked from commit 13cdb96bc52b3079ba91a08c1704307e5598ee59) Conflicts: drivers/mmc/fsl_esdhc.c
Diffstat (limited to 'drivers/net')
0 files changed, 0 insertions, 0 deletions