summaryrefslogtreecommitdiff
path: root/src/mainboard/google/gru
diff options
context:
space:
mode:
authorFurquan Shaikh <furquan@google.com>2016-07-25 17:00:07 -0700
committerFurquan Shaikh <furquan@google.com>2016-07-28 00:40:03 +0200
commit0d9cd92efb8b1bf2f9ef75d241040fb6955f4930 (patch)
treea3091130c04a9231bb0852cae48f5b8dfd3fc986 /src/mainboard/google/gru
parentc66a02634c1d4b0f7929cb9f4c510fff56db0ca6 (diff)
downloadcoreboot-0d9cd92efb8b1bf2f9ef75d241040fb6955f4930.tar.xz
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)
Diffstat (limited to 'src/mainboard/google/gru')
-rw-r--r--src/mainboard/google/gru/mainboard.c3
1 files changed, 0 insertions, 3 deletions
diff --git a/src/mainboard/google/gru/mainboard.c b/src/mainboard/google/gru/mainboard.c
index 5a6b82cbb1..7ec377f201 100644
--- a/src/mainboard/google/gru/mainboard.c
+++ b/src/mainboard/google/gru/mainboard.c
@@ -189,9 +189,6 @@ static void mainboard_init(device_t dev)
register_reset_to_bl31();
register_poweroff_to_bl31();
setup_rtc();
-
- elog_init();
- elog_add_boot_reason();
}
static void enable_backlight_booster(void)