mb/google/skywalker: 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:433636690 TEST=emerge-skywalker coreboot TEST="elogtool list" contained "Hardware watchdog reset" BRANCH=skywalker Change-Id: Iac6ec72d5c148244ccbd7d1b02af78c359897d7d Signed-off-by: Yu-Ping Wu <yupingso@chromium.org> Reviewed-on: https://review.coreboot.org/c/coreboot/+/90174 Reviewed-by: Yidi Lin <yidilin@google.com> Reviewed-by: Chen-Tsung Hsieh <chentsung@google.com> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
This commit is contained in:
parent
e4b0410946
commit
f5f304a5f3
1 changed files with 1 additions and 1 deletions
|
|
@ -26,7 +26,7 @@ config BOARD_SPECIFIC_OPTIONS
|
|||
select SOC_MEDIATEK_MT8189
|
||||
select BOARD_ROMSIZE_KB_8192
|
||||
select MAINBOARD_HAS_CHROMEOS
|
||||
select CHROMEOS_USE_EC_WATCHDOG_FLAG if CHROMEOS
|
||||
select CHROMEOS_USE_EC_WATCHDOG_FLAG if CHROMEOS && !MEDIATEK_WDT_RESET_BY_SW
|
||||
select COMMON_CBFS_SPI_WRAPPER
|
||||
select SPI_FLASH
|
||||
select SPI_FLASH_INCLUDE_ALL_DRIVERS
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue