[RESEND PATCH v2 2/2] samsung: common: do not reset if cros-ec uclass is missing

[Henrik Grimler]

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 <hen...@grimler.se>
Reviewed-by: Simon Glass <s...@chromium.org>
Reviewed-by: Minkyu Kang <mk7.k...@samsung.com>
---
 board/samsung/common/board.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/board/samsung/common/board.c b/board/samsung/common/board.c
index 16ce5cb89253..663d7ca991bc 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;
 
-- 
2.30.2