blob: 6ce6b33579f2135d95be728af9bfc41a030cf1cd [file] [log] [blame]
Kyösti Mälkki71216c92013-07-28 23:39:37 +03001config SOUTHBRIDGE_INTEL_COMMON
2 def_bool n
Kyösti Mälkkib5d998b2017-08-20 21:36:08 +03003
Patrick Rudolph59de6c92015-12-26 08:33:16 +01004config SOUTHBRIDGE_INTEL_COMMON_GPIO
5 def_bool n
Kyösti Mälkkib5d998b2017-08-20 21:36:08 +03006
Arthur Heymans16fe7902017-04-12 17:01:31 +02007config SOUTHBRIDGE_INTEL_COMMON_SMBUS
8 def_bool n
Kyösti Mälkkib5d998b2017-08-20 21:36:08 +03009 select HAVE_DEBUG_SMBUS
10
Arthur Heymansbddef0d2017-09-25 12:21:07 +020011config SOUTHBRIDGE_INTEL_COMMON_SPI
12 def_bool n
13 select SPI_FLASH
14
Bill XIEd533b162017-08-22 16:26:22 +080015config HAVE_INTEL_CHIPSET_LOCKDOWN
16 def_bool n
17
18config INTEL_CHIPSET_LOCKDOWN
19 depends on HAVE_INTEL_CHIPSET_LOCKDOWN && HAVE_SMI_HANDLER && !CHROMEOS
20 #ChromeOS's payload seems to handle finalization on its on.
21 bool "Lock down chipset in coreboot"
22 default y
23 help
24 Some registers within host bridge on particular chipsets should be
25 locked down on each normal boot path (done by either coreboot or payload)
26 and S3 resume (always done by coreboot). Select this to let coreboot
27 to do this on normal boot path.