From: Lucas Stach <l.stach@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH] Arm: i.MX5: Do not disable L2 cache
Date: Thu, 18 Jun 2020 14:21:08 +0200 [thread overview]
Message-ID: <8ed6835fbd1cb8e35117ff87f49502ef35d455d2.camel@pengutronix.de> (raw)
In-Reply-To: <20200618121206.5013-1-s.hauer@pengutronix.de>
Am Donnerstag, den 18.06.2020, 14:12 +0200 schrieb Sascha Hauer:
> Disabling the L2 cache is not working in imx5_init_lowlevel() because
> the necessary cache maintenance operations are missing. This often
> results in cache corruption in a chainloaded barebox.
> Disabling the cache is unnecessary: when we come from the ROM the L2
> cache is disabled anyway, so disabling it is a no-op. When we get here
> in a chainloaded barebox the L2 cache is already enabled and correctly
> configured. So instead of initializing it again we can take an enabled
> L2 cache as a sign to skip initialization and just return from the
> function.
While this won't hurt much, shouldn't we also disable the L2 cache on
Barebox shutdown, like we do on other SoCs?
Regards,
Lucas
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> ---
> arch/arm/mach-imx/imx5.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/mach-imx/imx5.c b/arch/arm/mach-imx/imx5.c
> index 96288f99e0..dd6c079fe3 100644
> --- a/arch/arm/mach-imx/imx5.c
> +++ b/arch/arm/mach-imx/imx5.c
> @@ -37,10 +37,13 @@ void imx5_init_lowlevel(void)
> {
> u32 r;
>
> - /* ARM errata ID #468414 */
> __asm__ __volatile__("mrc 15, 0, %0, c1, c0, 1":"=r"(r));
> +
> + if (r & (1 << 1))
> + return;
> +
> + /* ARM errata ID #468414 */
> r |= (1 << 5); /* enable L1NEON bit */
> - r &= ~(1 << 1); /* explicitly disable L2 cache */
> __asm__ __volatile__("mcr 15, 0, %0, c1, c0, 1" : : "r"(r));
>
> /* reconfigure L2 cache aux control reg */
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2020-06-18 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 12:12 Sascha Hauer
2020-06-18 12:21 ` Lucas Stach [this message]
2020-06-26 4:47 ` Sascha Hauer
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=8ed6835fbd1cb8e35117ff87f49502ef35d455d2.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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