summaryrefslogtreecommitdiff
path: root/src/soc/intel/apollolake/bootblock
diff options
context:
space:
mode:
authorDuncan Laurie <dlaurie@chromium.org>2016-09-19 12:02:54 -0700
committerDuncan Laurie <dlaurie@chromium.org>2016-09-19 19:03:34 -0700
commit5e3dad66227bba4be9365ee76d00231bb5577b56 (patch)
treed37e1d608326d34fbc9fd85f514cbbd437323a77 /src/soc/intel/apollolake/bootblock
parent884dfe632940b940df68d09f997fa5cd25121def (diff)
downloadcoreboot-5e3dad66227bba4be9365ee76d00231bb5577b56.tar.xz
soc/intel/apollolake: Initialize GPEs in bootblock
Initialize the GPEs from mainboard config in bootblock, so they can be used in verstage to query latched interrupt status. I still left it called in ramstage just to be sure that the configuration was not overwritten in FSP stages. Tested by reading and reporting GPE status in a loop in verstage and manually triggering an interrupt on EC console. BUG=chrome-os-partner:53336 Change-Id: I1af3e9ac1e5c59b9ebb5c6dd1599309c1f036581 Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
Diffstat (limited to 'src/soc/intel/apollolake/bootblock')
-rw-r--r--src/soc/intel/apollolake/bootblock/bootblock.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/src/soc/intel/apollolake/bootblock/bootblock.c b/src/soc/intel/apollolake/bootblock/bootblock.c
index 3015d17079..28a912818f 100644
--- a/src/soc/intel/apollolake/bootblock/bootblock.c
+++ b/src/soc/intel/apollolake/bootblock/bootblock.c
@@ -182,4 +182,7 @@ void bootblock_soc_early_init(void)
enable_spibar();
cache_bios_region();
+
+ /* Initialize GPE for use as interrupt status */
+ pmc_gpe_init();
}