summaryrefslogtreecommitdiff
path: root/firmware/lib/vboot_display.c
diff options
context:
space:
mode:
authorFurquan Shaikh <furquan@chromium.org>2016-11-03 16:05:07 -0700
committerchrome-bot <chrome-bot@chromium.org>2016-11-08 02:52:45 -0800
commit95b2d6ca2bea2a81ceeea58bc4660dfb3fa13a07 (patch)
treeadd29853a6a58dd85f92c4b08d7222cfc13fc7ed /firmware/lib/vboot_display.c
parent6e3931d1f609fc23b3ca8c7f6e563926e4f38b69 (diff)
downloadvboot-95b2d6ca2bea2a81ceeea58bc4660dfb3fa13a07.tar.gz
recovery: Add new recovery reason to train memory and reboot
This new recovery reason will instruct the calling firmware in vboot_select_and_load_kernel to reboot the device (under the assumption that training of memory has already been performed by the firmware). On seeing the return code VBERROR_REBOOT_REQUESTED, calling firmware should perform a reboot. BUG=chrome-os-partner:59352 BRANCH=None TEST=make -j runtests successful Change-Id: I110a735e612665cb2378bd71ca01a111edaf58e3 Signed-off-by: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/407656 Reviewed-by: Randall Spangler <rspangler@chromium.org>
Diffstat (limited to 'firmware/lib/vboot_display.c')
-rw-r--r--firmware/lib/vboot_display.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/firmware/lib/vboot_display.c b/firmware/lib/vboot_display.c
index adbeaa9f..e4720046 100644
--- a/firmware/lib/vboot_display.c
+++ b/firmware/lib/vboot_display.c
@@ -539,6 +539,8 @@ const char *RecoveryReasonString(uint8_t code)
return "User-mode requested recovery via BCB";
case VBNV_RECOVERY_US_FASTBOOT:
return "User-mode requested fastboot mode";
+ case VBNV_RECOVERY_TRAIN_AND_REBOOT:
+ return "User-mode requested DRAM train and reboot";
case VBNV_RECOVERY_US_UNSPECIFIED:
return "Unspecified/unknown error in user-mode";
}