chromeos: Clean up elog handling
1. Currenty, boot reason is being added to elog only for some ARM32/ARM64 platforms. Change this so that boot reason is logged by default in elog for all devices which have CHROMEOS selected. 2. Add a new option to select ELOG_WATCHDOG_RESET for the devices that want to add details about watchdog reset in elog. This requires a special region WATCHDOG to be present in the memlayout. 3. Remove calls to elog add boot reason and watchdog reset from mainboards. BUG=chrome-os-partner:55639 Change-Id: I91ff5b158cfd2a0749e7fefc498d8659f7e6aa91 Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://review.coreboot.org/15897 Reviewed-by: Aaron Durbin <adurbin@chromium.org> Tested-by: build bot (Jenkins)
This commit is contained in:
@@ -52,24 +52,6 @@ void chromeos_init_vboot(chromeos_acpi_t *chromeos)
|
||||
ARRAY_SIZE(chromeos->vdat));
|
||||
#endif
|
||||
|
||||
#if CONFIG_ELOG
|
||||
if (vboot_developer_mode_enabled() ||
|
||||
(vboot_wants_oprom() && !vboot_recovery_mode_enabled()))
|
||||
elog_add_event(ELOG_TYPE_CROS_DEVELOPER_MODE);
|
||||
if (vboot_recovery_mode_enabled()) {
|
||||
int reason = get_recovery_mode_from_vbnv();
|
||||
#if CONFIG_VBOOT
|
||||
if (vboot_handoff && !reason) {
|
||||
VbSharedDataHeader *sd = (VbSharedDataHeader *)
|
||||
vboot_handoff->shared_data;
|
||||
reason = sd->recovery_reason;
|
||||
}
|
||||
#endif
|
||||
elog_add_event_byte(ELOG_TYPE_CROS_RECOVERY_MODE,
|
||||
reason ? reason : ELOG_CROS_RECOVERY_MODE_BUTTON);
|
||||
}
|
||||
#endif
|
||||
|
||||
chromeos_ram_oops_init(chromeos);
|
||||
}
|
||||
|
||||
|
Reference in New Issue
Block a user