soc/intel/jasperlake: Move tco_configure to bootblock

Similar to CB:43313 (SHA bb50c67227), it seems possible for the same
problem to come up on jasperlake. Again, it should be harmless to
configure the TCO device earlier in the boot flow.

Signed-off-by: Tim Wawrzynczak <twawrzynczak@chromium.org>
Change-Id: If95e46124660b4ed457434f727c9f9f7b02b0327
Reviewed-on: https://review.coreboot.org/c/coreboot/+/43539
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Reviewed-by: Karthik Ramasubramanian <kramasub@google.com>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
This commit is contained in:
Tim Wawrzynczak 2020-07-16 16:35:27 -06:00
parent 03ed5bff5c
commit 60c619f6a3
2 changed files with 4 additions and 4 deletions

View File

@ -2,6 +2,7 @@
#include <bootblock_common.h>
#include <intelblocks/systemagent.h>
#include <intelblocks/tco.h>
#include <intelblocks/uart.h>
#include <soc/bootblock.h>
@ -25,4 +26,7 @@ void bootblock_soc_init(void)
{
report_platform_info();
pch_init();
/* Programming TCO_BASE_ADDRESS and TCO Timer Halt */
tco_configure();
}

View File

@ -1,14 +1,10 @@
/* SPDX-License-Identifier: GPL-2.0-only */
#include <intelblocks/smbus.h>
#include <intelblocks/tco.h>
#include <soc/romstage.h>
void pch_init(void)
{
/* Programming TCO_BASE_ADDRESS and TCO Timer Halt */
tco_configure();
/* Program SMBUS_BASE_ADDRESS and Enable it */
smbus_common_init();
}