CONFIG_MIPS_CPS is a better option for systems where it is supported,
which as far as I am aware should be all systems where CONFIG_MIPS_CMP
could provide any value (ie. where there are multiple cores for YAMON to
bring up). This option is therefore deprecated, and marked as such. It
is left intact for the time being in order to provide a fallback should
someone find a system where CONFIG_MIPS_CPS will not function (ie. where
the reset vector cannot be moved), and should be removed entirely in the
future assuming that does not happen.
Signed-off-by: Paul Burton <email@example.com>
arch/mips/Kconfig | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
index bdf4012..5bc27c0 100644
@@ -1980,7 +1980,7 @@ config MIPS_VPE_APSP_API_MT
depends on MIPS_VPE_APSP_API && !MIPS_CMP
- bool "MIPS CMP framework support"
+ bool "MIPS CMP framework support (DEPRECATED)"
depends on SYS_SUPPORTS_MIPS_CMP && !MIPS_MT_SMTC
@@ -1991,6 +1991,9 @@ config MIPS_CMP
framework" protocol (ie. YAMON) and want your kernel to make use of
its ability to start secondary CPUs.
+ Unless you have a specific need, you should use CONFIG_MIPS_CPS
+ instead of this.
bool "MIPS Coherent Processing System support"
depends on SYS_SUPPORTS_MIPS_CPS