From: Henrik Grimler <henrik@grimler.se>
To: Stefan Agner <stefan@agner.ch>
Cc: u-boot@lists.denx.de, sjg@chromium.org
Subject: Re: [PATCH] samsung: common: ignore if CROS EC is not supported
Date: Thu, 16 Feb 2023 09:13:23 +0100 [thread overview]
Message-ID: <Y+3lhxCbZja/Mwup@L14.lan> (raw)
In-Reply-To: <841fd733dfe500dee9b4f8354337135d4bc1de93.1676487760.git.stefan@agner.ch>
Hi Stefan,
On Wed, Feb 15, 2023 at 08:03:14PM +0100, Stefan Agner wrote:
> If the CROS device class is not compiled in, uclass returns not
> supported. Ignore this case as well.
>
> This avoids boot failures on ODROID-XU4 without CONFIG_CROS_EC
> ending with:
> cros-ec communications failure -96
> Please reset with Power+Refresh
> Cannot init cros-ec device
Thanks, the same issue happens on odroid-u2 (and probably other
devices as well), issue was reported in
https://lists.denx.de/pipermail/u-boot/2023-January/504115.html, and I
sent an identical patch in
https://lists.denx.de/pipermail/u-boot/2023-February/508929.html.
Best regards,
Henrik Grimler
> Signed-off-by: Stefan Agner <stefan@agner.ch>
> ---
> 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 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;
>
> --
> 2.39.1
>
prev parent reply other threads:[~2023-02-16 8:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 19:03 [PATCH] samsung: common: ignore if CROS EC is not supported Stefan Agner
2023-02-15 23:50 ` Simon Glass
2023-02-16 8:13 ` Henrik Grimler [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y+3lhxCbZja/Mwup@L14.lan \
--to=henrik@grimler.se \
--cc=sjg@chromium.org \
--cc=stefan@agner.ch \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox