From c6c9b9cf486eaa1bc7892b142e9201463fc99025 Mon Sep 17 00:00:00 2001 From: Angel Pons Date: Mon, 7 Sep 2020 13:45:53 +0200 Subject: apollolake: Define MAX_CPUS at SoC scope The three Intel Apollo Lake boards (apl_rvp, leafhill and minnow3) do not define MAX_CPUS, which would then default to 1. Since this is most likely an oversight, use the same value as other Apollo Lake boards. To ensure this does not happen again, factor out MAX_CPUS to SoC scope. Change-Id: I5ed98a6b592c8010b59eca7ff773ae1ccc4cd7b1 Signed-off-by: Angel Pons Reviewed-on: https://review.coreboot.org/c/coreboot/+/45144 Reviewed-by: Nico Huber Reviewed-by: Mario Scheithauer Tested-by: build bot (Jenkins) --- src/soc/intel/apollolake/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/soc') diff --git a/src/soc/intel/apollolake/Kconfig b/src/soc/intel/apollolake/Kconfig index f5d932396b..a30333bb68 100644 --- a/src/soc/intel/apollolake/Kconfig +++ b/src/soc/intel/apollolake/Kconfig @@ -110,7 +110,7 @@ config CPU_SPECIFIC_OPTIONS config MAX_CPUS int - default 4 if SOC_INTEL_GEMINILAKE + default 4 config CHROMEOS select CHROMEOS_RAMOOPS_DYNAMIC -- cgit v1.2.3