diff options
author | Robin Gong <b38343@freescale.com> | 2015-02-15 05:00:35 +0300 |
---|---|---|
committer | Vinod Koul <vinod.koul@intel.com> | 2015-03-16 13:25:22 +0300 |
commit | 855832e47c1e51db701786ed76f8a9fec323aad6 (patch) | |
tree | b76442f46ff0273290a19e9f095a5eee7bb861ba /drivers/dma/dw | |
parent | bdf6c79278b3fb6caf1811ae877078c5f424bcb1 (diff) | |
download | linux-855832e47c1e51db701786ed76f8a9fec323aad6.tar.xz |
dmaengine: imx-sdma: switch to dynamic context mode after script loaded
Below comments got from Page4724 of Reference Manual of i.mx6q:
http://cache.freescale.com/files/32bit/doc/ref_manual/IMX6DQRM.pdf
--"Static context mode should be used for the first channel called
after reset to ensure that the all context RAM for that channel is
initialized during the context SAVE phase when the channel is
done or yields. Subsequent calls to the same channel or
different channels may use any of the dynamic context modes.
This will ensure that all context locations for the bootload
channel are initialized, and prevent undefined values in context
RAM from being loaded during the context restore if the
channel is re-started later"
Unfortunately, the rule was broken by commit(5b28aa319bba96987316425a1131813d87cbab35)
.This patch just take them back.
Signed-off-by: Robin Gong <b38343@freescale.com>
Signed-off-by: Vinod Koul <vinod.koul@intel.com>
Diffstat (limited to 'drivers/dma/dw')
0 files changed, 0 insertions, 0 deletions