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

Minkyu Kang promsoft at gmail.com
Fri Feb 24 10:05:42 CET 2023


On Mon, 13 Feb 2023 at 23:45, Simon Glass <sjg at chromium.org> wrote:

> On Mon, 13 Feb 2023 at 01:08, Henrik Grimler <henrik at grimler.se> wrote:
> >
> > 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 at grimler.se>
> > ---
> >  board/samsung/common/board.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
>
> Reviewed-by: Simon Glass <sjg at chromium.org>
>

Reviewed-by: Minkyu Kang <mk7.kang at samsung.com>

-- 
Thanks,
Minkyu Kang.


More information about the U-Boot mailing list