mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [RFC] ARM: mmu: Do not try to pick early TTB up
Date: Wed, 23 May 2018 10:43:41 +0200	[thread overview]
Message-ID: <20180523084341.i5edq2nznd7spbi3@pengutronix.de> (raw)
In-Reply-To: <20180523051012.26148-1-andrew.smirnov@gmail.com>

On Tue, May 22, 2018 at 10:10:12PM -0700, Andrey Smirnov wrote:
> The call to create_flat_mapping() in mmu.c will change both memory
> type and shareability of all RAM in use by barebox while MMU is on
> when done in conjunction with CONFIG_MMU_EARLY.

I notice that with MMU_EARLY enabled we call create_flat_mapping()
twice, once in the early MMU code and once when setting up the MMU for
real. In between we remap the the SDRAM cached which then is reverted
during the second call to create_flat_mapping().

This seems unnecessary. Does the following help you?

Sascha

------------------------8<-----------------------------

From 8abcb2fae2ee642bdcbf79aab2d9a3bdbb3dacc1 Mon Sep 17 00:00:00 2001
From: Sascha Hauer <s.hauer@pengutronix.de>
Date: Wed, 23 May 2018 10:39:23 +0200
Subject: [PATCH] ARM: mmu: only create flat mapping when early MMU hasn't done
 it already

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
 arch/arm/cpu/mmu.c | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/arch/arm/cpu/mmu.c b/arch/arm/cpu/mmu.c
index a89f420f20..7e2e5bf7e0 100644
--- a/arch/arm/cpu/mmu.c
+++ b/arch/arm/cpu/mmu.c
@@ -470,15 +470,15 @@ static int mmu_init(void)
 					ttb);
 	} else {
 		ttb = xmemalign(ARM_TTB_SIZE, ARM_TTB_SIZE);
-	}
 
-	pr_debug("ttb: 0x%p\n", ttb);
+		set_ttbr(ttb);
+		set_domain(DOMAIN_MANAGER);
 
-	set_ttbr(ttb);
-	set_domain(DOMAIN_MANAGER);
+		create_flat_mapping(ttb);
+		__mmu_cache_flush();
+	}
 
-	create_flat_mapping(ttb);
-	__mmu_cache_flush();
+	pr_debug("ttb: 0x%p\n", ttb);
 
 	vectors_init();
 
-- 
2.17.0

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2018-05-23  8:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-23  5:10 Andrey Smirnov
2018-05-23  8:43 ` Sascha Hauer [this message]
2018-05-25  3:14   ` Andrey Smirnov
2018-05-25  9:01     ` Sascha Hauer
2018-05-25  9:09       ` Lucas Stach
2018-05-25 17:07         ` Andrey Smirnov
2018-05-25 17:09       ` Andrey Smirnov
2018-05-25 17:35         ` Sam Ravnborg
2018-05-28 12:05         ` Sascha Hauer
2018-05-28 18:08           ` Andrey Smirnov

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=20180523084341.i5edq2nznd7spbi3@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=andrew.smirnov@gmail.com \
    --cc=barebox@lists.infradead.org \
    /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