On Mon, 13 Feb 2023 at 23:45, Simon Glass <s...@chromium.org> wrote: > On Mon, 13 Feb 2023 at 01:08, Henrik Grimler <hen...@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 <hen...@grimler.se> > > --- > > board/samsung/common/board.c | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > Reviewed-by: Simon Glass <s...@chromium.org> >
Reviewed-by: Minkyu Kang <mk7.k...@samsung.com> -- Thanks, Minkyu Kang.