blob: 4f8a407490e6dc5ca5791329435075aa88786669 [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
Tobias Diedrich9d8be5a2017-12-13 23:25:32 +010015config SOUTHBRIDGE_INTEL_COMMON_PIRQ_ACPI_GEN
16 def_bool n
17
18config SOUTHBRIDGE_INTEL_COMMON_RCBA_PIRQ
19 def_bool n
20 select SOUTHBRIDGE_INTEL_COMMON_PIRQ_ACPI_GEN
21
Bill XIEd533b162017-08-22 16:26:22 +080022config HAVE_INTEL_CHIPSET_LOCKDOWN
23 def_bool n
24
Arthur Heymansa0508172018-01-25 11:30:22 +010025config SOUTHBRIDGE_INTEL_COMMON_SMM
26 def_bool n
27
Bill XIEd533b162017-08-22 16:26:22 +080028config INTEL_CHIPSET_LOCKDOWN
29 depends on HAVE_INTEL_CHIPSET_LOCKDOWN && HAVE_SMI_HANDLER && !CHROMEOS
30 #ChromeOS's payload seems to handle finalization on its on.
31 bool "Lock down chipset in coreboot"
32 default y
33 help
34 Some registers within host bridge on particular chipsets should be
35 locked down on each normal boot path (done by either coreboot or payload)
36 and S3 resume (always done by coreboot). Select this to let coreboot
37 to do this on normal boot path.