src/southbridge/intel/common/Kconfig

config SOUTHBRIDGE_INTEL_COMMON
	def_bool n
	select SOUTHBRIDGE_INTEL_COMMON_RESET

config SOUTHBRIDGE_INTEL_COMMON_RESET
	bool
	select HAVE_CF9_RESET

config SOUTHBRIDGE_INTEL_COMMON_GPIO
	def_bool n

config SOUTHBRIDGE_INTEL_COMMON_SMBUS
	def_bool n
	select HAVE_DEBUG_SMBUS

config SOUTHBRIDGE_INTEL_COMMON_SPI
	def_bool n
	select SPI_FLASH

config SOUTHBRIDGE_INTEL_COMMON_PIRQ_ACPI_GEN
	def_bool n

config SOUTHBRIDGE_INTEL_COMMON_RCBA_PIRQ
	def_bool n
	select SOUTHBRIDGE_INTEL_COMMON_PIRQ_ACPI_GEN

config HAVE_INTEL_CHIPSET_LOCKDOWN
	def_bool n

config SOUTHBRIDGE_INTEL_COMMON_SMM
	def_bool n
	select HAVE_POWER_STATE_AFTER_FAILURE
	select HAVE_POWER_STATE_PREVIOUS_AFTER_FAILURE

config SOUTHBRIDGE_INTEL_COMMON_ACPI_MADT
	bool

config SOUTHBRIDGE_INTEL_COMMON_FINALIZE
	bool

config INTEL_DESCRIPTOR_MODE_CAPABLE
	def_bool n
	help
	  This config simply states that the platform is *capable* of running in
	  descriptor mode (when the descriptor in flash is valid).

config INTEL_DESCRIPTOR_MODE_REQUIRED
	def_bool y if INTEL_DESCRIPTOR_MODE_CAPABLE
	help
	  This config states descriptor mode is *required* for the platform to
	  function properly, or to function at all.

config INTEL_CHIPSET_LOCKDOWN
	depends on HAVE_INTEL_CHIPSET_LOCKDOWN && HAVE_SMI_HANDLER && !CHROMEOS
	#ChromeOS's payload seems to handle finalization on its on.
	bool "Lock down chipset in coreboot"
	default y
	help
	  Some registers within host bridge on particular chipsets should be
	  locked down on each normal boot path (done by either coreboot or payload)
	  and S3 resume (always done by coreboot). Select this to let coreboot
	  to do this on normal boot path.

if SOUTHBRIDGE_INTEL_COMMON_FINALIZE

choice
	prompt "Flash locking during chipset lockdown"
	default LOCK_SPI_FLASH_NONE

config LOCK_SPI_FLASH_NONE
	bool "Don't lock flash sections"

config LOCK_SPI_FLASH_RO
	bool "Write-protect all flash sections"
	help
	  Select this if you want to write-protect the whole firmware flash
	  chip. The locking will take place during the chipset lockdown, which
	  is either triggered by coreboot (when INTEL_CHIPSET_LOCKDOWN is set)
	  or has to be triggered later (e.g. by the payload or the OS).

	        NOTE: If you trigger the chipset lockdown unconditionally,
	        you won't be able to write to the flash chip using the
	        internal programmer any more.

config LOCK_SPI_FLASH_NO_ACCESS
	bool "Write-protect all flash sections and read-protect non-BIOS sections"
	help
	  Select this if you want to protect the firmware flash against all
	  further accesses (with the exception of the memory mapped BIOS re-
	  gion which is always readable). The locking will take place during
	  the chipset lockdown, which is either triggered by coreboot (when
	  INTEL_CHIPSET_LOCKDOWN is set) or has to be triggered later (e.g.
	  by the payload or the OS).

	        NOTE: If you trigger the chipset lockdown unconditionally,
	        you won't be able to write to the flash chip using the
	        internal programmer any more.

endchoice

endif