summaryrefslogtreecommitdiff
path: root/src/soc/intel/jasperlake/chip.h
diff options
context:
space:
mode:
authorTim Wawrzynczak <twawrzynczak@chromium.org>2020-07-16 16:35:27 -0600
committerTim Wawrzynczak <twawrzynczak@chromium.org>2020-07-22 21:06:34 +0000
commit60c619f6a3c0fbe2f53095a029cd07a11f5cf5e1 (patch)
tree9728187c12e23ddfe10d1273f5af6d8b3a29bc2d /src/soc/intel/jasperlake/chip.h
parent03ed5bff5cb13118b203b34b18e05694e713a30a (diff)
soc/intel/jasperlake: Move tco_configure to bootblock
Similar to CB:43313 (SHA bb50c672278), 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>
Diffstat (limited to 'src/soc/intel/jasperlake/chip.h')
0 files changed, 0 insertions, 0 deletions