public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michael Heimpold <mhei@heimpold.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] arm: mxs: No arch specific invalidate_icache_all available!
Date: Sat, 29 Apr 2017 09:21:32 +0200	[thread overview]
Message-ID: <1593756.jibKTJDvME@kerker> (raw)
In-Reply-To: <CAOMZO5AUUgzsDrsYHrZ0igg2ByV1+wmOtFfRAKAQTSGw=ocqAQ@mail.gmail.com>

Hi,

Am Montag, 24. April 2017, 20:12:55 CEST schrieb Fabio Estevam:
> Hi Stefan,
> 
> On Mon, Apr 24, 2017 at 8:03 AM, Stefan Wahren <stefan.wahren@i2se.com> 
wrote:
> > Hi,
> > 
> > i tried to port our Duckbill (based on NXP i.MX28 SoC) to U-Boot
> > v2017.03 [1]. The startup works fine, except of this warning:
> > 
> > No arch specific invalidate_icache_all available!
> > 
> > I didn't found a MXS specific implementation of invalidate_icache_all().
> > 
> > Did i miss something? Shouldn't be the other MXS boards also affected?
> > 
> > [1] - https://github.com/lategoodbye/u-boot/tree/v2017.03-duckbill
> 
> Looks like ARM926 needs a invalidate_icache_all available() implementation.
> 

we could move the implementation in arch/arm/mach-at91/arm926ejs/cache.c
to a more generic place and re-use it.

However, the warning is only generated because lib/efi_loader/efi_runtime.c
calls invalidate_icache_all from efi_runtime_relocate. This is because
CONFIG_EFI_LOADER is set.

I don't know if somebody using the EFI stuff for other MXS-based boards.
For our Duckbill, I would simply force
# CONFIG_EFI_LOADER is not set
via config.

Regards,
Michael

  reply	other threads:[~2017-04-29  7:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-24 11:03 [U-Boot] arm: mxs: No arch specific invalidate_icache_all available! Stefan Wahren
2017-04-24 23:12 ` Fabio Estevam
2017-04-29  7:21   ` Michael Heimpold [this message]
2017-05-03  0:56     ` Fabio Estevam
2017-05-03  7:19       ` Michael Heimpold
2017-05-03 13:29         ` Fabio Estevam

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=1593756.jibKTJDvME@kerker \
    --to=mhei@heimpold.de \
    --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