MIPS: Deprecate CONFIG_MIPS_CMP

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 <paul.burton@imgtec.com>
Cc: linux-mips@linux-mips.org
Patchwork: https://patchwork.linux-mips.org/patch/6369/
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>

diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
index d0b446e154d5a94ccc5e823291b7e2adcee49705..82aa06974c53f460d8e07c3fc50b6f3529387308 100644 (file)
--- a/arch/mips/Kconfig
+++ b/arch/mips/Kconfig
@@ -1999,7 +1999,7 @@ config MIPS_VPE_APSP_API_MT
        depends on MIPS_VPE_APSP_API && !MIPS_CMP
 
 config MIPS_CMP
-       bool "MIPS CMP framework support"
+       bool "MIPS CMP framework support (DEPRECATED)"
        depends on SYS_SUPPORTS_MIPS_CMP && !MIPS_MT_SMTC
        select MIPS_GIC_IPI
        select SYNC_R4K
@@ -2010,6 +2010,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.
+
 config MIPS_CPS
        bool "MIPS Coherent Processing System support"
        depends on SYS_SUPPORTS_MIPS_CPS