tree 2db7629ee20b14eb097b1d4f1b33ac9acd1b1ead
parent 0d9390330b04a146a32609f74c5c7be6beb5ddf5
author Julius Werner <jwerner@chromium.org> 1553805235 -0700
committer chrome-bot <chrome-bot@chromium.org> 1554497036 -0700

UPSTREAM: vboot: Change oprom checks to CONFIG_VBOOT, assert OPROM_MATTERS

Skipping display init on normal-mode boot is a vboot feature, not
specific to Chrome OS. Fix the code in display_init_required() and
pci_dev_init() to check CONFIG_VBOOT rather than CONFIG_CHROMEOS now
that the two aren't always the same anymore.

Also add a check to guarantee at compile time that
CONFIG_VBOOT_OPROM_MATTERS is enabled on all platforms that make a check
to this function (when CONFIG_VBOOT is also enabled). The whole display
skipping mechanism is based on the oprom_needed NVRAM flag, and skipping
display init without enabling the option to tell vboot that it needs to
pay attention to that flag would make the whole thing not work right.

BUG=none
BRANCH=none
TEST=none

Change-Id: Ica124a124f0d89b4562a8289b70b1372847bdec2
Signed-off-by: Patrick Georgi <pgeorgi@google.com>
Original-Commit-Id: 6d9c131061fbc984711cb97a0a24e7d4ce77549e
Original-Change-Id: I5d6421509bdcdaa61b78015af3fa6241fe75bb7f
Original-Signed-off-by: Julius Werner <jwerner@chromium.org>
Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/32112
Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Original-Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Original-Reviewed-by: Patrick Georgi <pgeorgi@google.com>
Reviewed-on: https://chromium-review.googlesource.com/1553839
Commit-Ready: Patrick Georgi <pgeorgi@chromium.org>
Tested-by: Patrick Georgi <pgeorgi@chromium.org>
Reviewed-by: Patrick Georgi <pgeorgi@chromium.org>