| commit | a673d1cd2d4d74fdc6f373952f14667f51908f1d | |
| author | Duncan Laurie <dlaurie@chromium.org> | |
| Mon, 19 Sep 2016 19:02:54 +0000 (19 12:02 -0700) | ||
| committer | Patrick Georgi <pgeorgi@google.com> | |
| Wed, 21 Sep 2016 08:46:14 +0000 (21 10:46 +0200) | ||
| tree | 40962ef0979455c7895f267d26fc9185b6486187 | treesnapshot (tar.gz zip) |
| parent | 1f6e6813554606bb23481fe64401809ab43bdcc7 | commitdiff |
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: Iacd0483e4b3229aca602bb5bb40586eedf35a6ea
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-on: https://review.coreboot.org/16670
Tested-by: build bot (Jenkins)
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
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: Iacd0483e4b3229aca602bb5bb40586eedf35a6ea
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-on: https://review.coreboot.org/16670
Tested-by: build bot (Jenkins)
Reviewed-by: Aaron Durbin <adurbin@chromium.org>