aboutsummaryrefslogtreecommitdiff
path: root/configs
diff options
context:
space:
mode:
authorAndrew F. Davis <afd@ti.com>2020-07-15 17:02:36 -0400
committerLokesh Vutla <lokeshvutla@ti.com>2020-08-11 10:18:27 +0530
commit864e2857393dc98504ec5da16e0e41e38a0abe39 (patch)
tree6b396a8df6d75c111d34c84f1f3b7bab3e4ef2d1 /configs
parente1c36685949ebad091f5807f980cae7be5d4ba23 (diff)
downloadu-boot-864e2857393dc98504ec5da16e0e41e38a0abe39.zip
u-boot-864e2857393dc98504ec5da16e0e41e38a0abe39.tar.gz
u-boot-864e2857393dc98504ec5da16e0e41e38a0abe39.tar.bz2
arm: mach-k3: Clean non-coherent lines out of L3 cache
When switching on or off the ARM caches some care must be taken to ensure existing cache line allocations are not left in an inconsistent state. An example of this is when cache lines are considered non-shared by and L3 controller even though the lines are shared. To prevent these and other issues all cache lines should be cleared before enabling or disabling a coherent master's cache. ARM cores and many L3 controllers provide a way to efficiently clean out all cache lines to allow for this, unfortunately there is no such easy way to do this on current K3 MSMC based systems. We could explicitly clean out every valid external address tracked by MSMC (all of DRAM), or we could attempt to identify only the set of addresses accessed by a given boot stage and flush only those specifically. This patch attempts the latter. We start with cleaning the SPL load address. More addresses can be added here later as they are identified. Note that we perform a flush operation for both the flush and invalidate operations, this is not a typo. We do this to avoid the situation that some ARM cores will promote an invalidate to a clean+invalidate, but only emit the invalidation operation externally, leading to a loss of data. Signed-off-by: Andrew F. Davis <afd@ti.com> Tested-by: Faiz Abbas <faiz_abbas@ti.com>
Diffstat (limited to 'configs')
0 files changed, 0 insertions, 0 deletions