diff options
| author | Henrik Grimler <henrik@grimler.se> | 2023-05-09 21:05:47 +0200 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2023-05-15 17:14:46 -0400 |
| commit | c9901bd2adad104adb132bdcc92fe2e86b4bcaa0 (patch) | |
| tree | cad0bb2f6f0fb7ee96f761f57135019b179fdcc3 | |
| parent | 7d01ee9d19db9670486ffc427c67855420ed8c94 (diff) | |
| download | u-boot-c9901bd2adad104adb132bdcc92fe2e86b4bcaa0.tar.gz u-boot-c9901bd2adad104adb132bdcc92fe2e86b4bcaa0.tar.bz2 u-boot-c9901bd2adad104adb132bdcc92fe2e86b4bcaa0.zip | |
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 <henrik@grimler.se>
Reviewed-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Minkyu Kang <mk7.kang@samsung.com>
| -rw-r--r-- | board/samsung/common/board.c | 2 |
1 files changed, 1 insertions, 1 deletions
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; |