From 37bead6d26fc45f66e8032c50b3af619b246f1dc Mon Sep 17 00:00:00 2001 From: Subrata Banik Date: Sun, 9 Feb 2020 19:13:52 +0530 Subject: [PATCH] Kconfig: Guard CONFIGURABLE_RAMSTAGE This patch guards CONFIGURABLE_RAMSTAGE symbol (which is default enable for all x86 systems) with another Kconfig that can be selected by platform that actually planning to use it. TEST=CONFIG_CONFIGURABLE_RAMSTAGE is not enabled by default. Change-Id: I2113445d507294df59fbc7fb1373793b47c6c31c Signed-off-by: Subrata Banik Reviewed-on: https://review.coreboot.org/c/coreboot/+/38795 Tested-by: build bot (Jenkins) Reviewed-by: Martin Roth --- src/Kconfig | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/Kconfig b/src/Kconfig index 3742c04675..4253ec7d52 100644 --- a/src/Kconfig +++ b/src/Kconfig @@ -354,9 +354,13 @@ config RAMPAYLOAD Skip PCI enumeration logic and only allocate BAR for fixed devices (bootable devices, TPM over GSPI). +config HAVE_CONFIGURABLE_RAMSTAGE + bool + config CONFIGURABLE_RAMSTAGE bool "Enable a configurable ramstage." default y if ARCH_X86 + depends on HAVE_CONFIGURABLE_RAMSTAGE help A configurable ramstage allows you to select which parts of the ramstage to run. Currently, we can only select a minimal PCI scanning step. -- 2.11.4.GIT