From 7b205808e464a369ddffb49cb15cd2f13e59862d Mon Sep 17 00:00:00 2001 From: Jarried Lin Date: Mon, 9 Feb 2026 13:24:20 +0800 Subject: [PATCH] mb/google/rauru: Disable CHROMEOS_USE_EC_WATCHDOG_FLAG Now that we use the WATCHDOG_TOMBSTONE section to store the watchdog event magic, there is no need to ask EC for the last reset reason. In fact, with MEDIATEK_WDT_RESET_BY_SW enabled, EC doesn't even record the watchdog reset reason. Enable CHROMEOS_USE_EC_WATCHDOG_FLAG only if MEDIATEK_WDT_RESET_BY_SW is disabled. BUG=b:481854714 TEST= After triggering WDT timeout, the following log can be observed: [NOTE ] coreboot-coreboot-unknown.9999.782bb84 Mon Feb 23 06:42:21 UTC 2026 aarch64 bootblock starting (log level: 8) [DEBUG] ARM64: Exception handlers installed. [DEBUG] ARM64: Testing exception [DEBUG] ARM64: Done test exception [DEBUG] [booker_init] AP hash rule: 0xbe00 [INFO ] mtk_cksys_init = 0x1 [INFO ] WDT: Status = 0x20000 [INFO ] WDT: Last reset was other reset type: 0x00020000 [INFO ] mtk_wdt_swreset() called! [INFO ] board_reset() called! And "elogtool list" contained "Hardware watchdog reset". Change-Id: I44a940d88948897e6727fad5c87f364e3ba9ac61 Signed-off-by: Jarried Lin Reviewed-on: https://review.coreboot.org/c/coreboot/+/91421 Reviewed-by: Yu-Ping Wu Tested-by: build bot (Jenkins) --- src/mainboard/google/rauru/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/mainboard/google/rauru/Kconfig b/src/mainboard/google/rauru/Kconfig index c13149aefe..dbbfcfb360 100644 --- a/src/mainboard/google/rauru/Kconfig +++ b/src/mainboard/google/rauru/Kconfig @@ -26,7 +26,7 @@ config BOARD_SPECIFIC_OPTIONS select SPI_FLASH_INCLUDE_ALL_DRIVERS select MAINBOARD_HAS_NATIVE_VGA_INIT select HAVE_LINEAR_FRAMEBUFFER - select CHROMEOS_USE_EC_WATCHDOG_FLAG if CHROMEOS + select CHROMEOS_USE_EC_WATCHDOG_FLAG if CHROMEOS && !MEDIATEK_WDT_RESET_BY_SW select EC_GOOGLE_CHROMEEC select EC_GOOGLE_CHROMEEC_BOARDID select EC_GOOGLE_CHROMEEC_FW_CONFIG_FROM_UFSC if BOARD_GOOGLE_SAPPHIRE