Vikram Kanigiri 12e7c4ab0b Initialise cpu ops after enabling data cache ... The cpu-ops pointer was initialized before enabling the data cache in the cold and warm boot paths. This required a DCIVAC cache maintenance operation to invalidate any stale cache lines resident in other cpus. This patch moves this initialization to the bl31_arch_setup() function which is always called after the data cache and MMU has been enabled. This change removes the need: 1. for the DCIVAC cache maintenance operation. 2. to initialise the CPU ops upon resumption from a PSCI CPU_SUSPEND call since memory contents are always preserved in this case. Change-Id: Ibb2fa2f7460d1a1f1e721242025e382734c204c6		2015-03-13 10:38:09 +00:00
..
bl31_arch_setup.c	Initialise cpu ops after enabling data cache	2015-03-13 10:38:09 +00:00
bl31_entrypoint.S	Initialise cpu ops after enabling data cache	2015-03-13 10:38:09 +00:00
context.S	Miscellaneous documentation fixes	2014-08-27 19:13:56 +01:00
cpu_data.S	Per-cpu data cache restructuring	2014-06-16 21:30:32 +01:00
crash_reporting.S	Add CPU specific crash reporting handlers	2014-08-20 19:14:31 +01:00
runtime_exceptions.S	Miscellaneous documentation fixes	2014-08-27 19:13:56 +01:00