mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-11-20 18:54:09 +08:00
3721924c81
The kernel already has the responsibility to handle resources such as the CCI when hotplugging CPUs, during the booting of secondary CPUs, and when resuming from suspend/idle. It would be more coherent and less confusing if the CCI for the boot CPU (or cluster) was also initialized by the kernel rather than expecting the firmware/bootloader to do it and only in that case. After all, the kernel has all the necessary code already and the bootloader shouldn't have to care at all. The CCI may be turned on only when the cache is off. Leveraging the CPU suspend code to loop back through the low-level MCPM entry point is all that is needed to properly turn on the CCI from the kernel by using the same code as during secondary boot. Let's provide a generic MCPM loopback function that can be invoked by backend initialization code to set things (CCI or similar) on the boot CPU just as it is done for the other CPUs. Signed-off-by: Nicolas Pitre <nico@linaro.org> Reviewed-by: Kevin Hilman <khilman@linaro.org> Tested-by: Kevin Hilman <khilman@linaro.org> Tested-by: Doug Anderson <dianders@chromium.org> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> |
||
|---|---|---|
| .. | ||
| bL_switcher_dummy_if.c | ||
| bL_switcher.c | ||
| dmabounce.c | ||
| edma.c | ||
| firmware.c | ||
| icst.c | ||
| it8152.c | ||
| Kconfig | ||
| locomo.c | ||
| Makefile | ||
| mcpm_entry.c | ||
| mcpm_head.S | ||
| mcpm_platsmp.c | ||
| sa1111.c | ||
| scoop.c | ||
| sharpsl_param.c | ||
| timer-sp.c | ||
| vlock.h | ||
| vlock.S | ||