diff options
| author | Joel Kitching <kitching@google.com> | 2019-05-29 16:22:28 +0800 |
|---|---|---|
| committer | Commit Bot <commit-bot@chromium.org> | 2019-06-07 20:09:42 +0000 |
| commit | 40c35a022fc9ff9a2be0f394be45747e8f767931 (patch) | |
| tree | b852beb588493e14f5875f63e3a1fb3d2f2b2cf5 /tests/vboot_detach_menu_tests.c | |
| parent | 2d150c697904584f1ef863155129071bb2fed48d (diff) | |
| download | vboot-40c35a022fc9ff9a2be0f394be45747e8f767931.tar.gz | |
vboot: check for VB2_NV_DIAG_REQUEST when enabling display
VB2_NV_DISPLAY_REQUEST should only be used for cases where there
is no other way for coreboot to tell that display initialization
is required.
In the case of developer, recovery, and diagnostic modes, display
should always be initialized without looking at
VB2_NV_DISPLAY_REQUEST.
In the case of EC slow sync, VB2_NV_DISPLAY_REQUEST should still
be used.
BUG=b:124141368, chromium:948592, chromium:967298, b:133175864
TEST=make clean && make runtests
BRANCH=none
Change-Id: I56e7d50bfd7de596d25ba232251f73ccd2d5df9b
Signed-off-by: Joel Kitching <kitching@google.com>
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/vboot_reference/+/1634450
Reviewed-by: Joel Kitching <kitching@chromium.org>
Tested-by: Joel Kitching <kitching@chromium.org>
Commit-Queue: Jason Clinton <jclinton@chromium.org>
Diffstat (limited to 'tests/vboot_detach_menu_tests.c')
0 files changed, 0 insertions, 0 deletions