summaryrefslogtreecommitdiff
path: root/src/soc/intel/jasperlake
diff options
context:
space:
mode:
authorTim Wawrzynczak <twawrzynczak@chromium.org>2020-07-16 16:31:32 -0600
committerTim Wawrzynczak <twawrzynczak@chromium.org>2020-07-22 21:06:29 +0000
commit03ed5bff5cb13118b203b34b18e05694e713a30a (patch)
treee70d2b749b7c72b3c6936e0d755b6d8400be03d6 /src/soc/intel/jasperlake
parentbfd6521ce71b67a619da221dce7070db3959533b (diff)
soc/intel/cannonlake: Move tco_configure to bootblock
Similar to CB:43313 (SHA bb50c672278), it seems possible for the same problem to come up on cannonlake. 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: Ib8883d27b2a0994a67ec5e044a692a2e853fd680 Reviewed-on: https://review.coreboot.org/c/coreboot/+/43538 Reviewed-by: Furquan Shaikh <furquan@google.com> Reviewed-by: Aaron Durbin <adurbin@chromium.org> Reviewed-by: Karthik Ramasubramanian <kramasub@google.com> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'src/soc/intel/jasperlake')
0 files changed, 0 insertions, 0 deletions