From c9901bd2adad104adb132bdcc92fe2e86b4bcaa0 Mon Sep 17 00:00:00 2001 From: Henrik Grimler Date: Tue, 9 May 2023 21:05:47 +0200 Subject: samsung: common: do not reset if cros-ec uclass is missing Otherwise non-ChromeOS samsung devices, like the odroid boards, are stuck in a bootloop if CONFIG_CROS_EC is not enabled: <...> MMC: SAMSUNG SDHCI: 2, EXYNOS DWMMC: 0 Loading Environment from MMC... *** Warning - bad CRC, using default environment cros-ec communications failure -96 Please reset with Power+Refresh Cannot init cros-ec device resetting ... Issue started after commit e44d7e73fe0d ("dm: core: Switch uclass_*_device_err to use uclass_*_device_check"). Signed-off-by: Henrik Grimler Reviewed-by: Simon Glass Reviewed-by: Minkyu Kang --- board/samsung/common/board.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'board/samsung') diff --git a/board/samsung/common/board.c b/board/samsung/common/board.c index 16ce5cb892..663d7ca991 100644 --- a/board/samsung/common/board.c +++ b/board/samsung/common/board.c @@ -223,7 +223,7 @@ int board_late_init(void) char mmcbootdev_str[16]; ret = uclass_first_device_err(UCLASS_CROS_EC, &dev); - if (ret && ret != -ENODEV) { + if (ret && ret != -ENODEV && ret != -EPFNOSUPPORT) { /* Force console on */ gd->flags &= ~GD_FLG_SILENT; -- cgit v1.2.3