From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 2/7] ARM tx28: Add mmu support
Date: Fri, 14 Jan 2011 20:51:34 +0100 [thread overview]
Message-ID: <1295034699-18863-3-git-send-email-s.hauer@pengutronix.de> (raw)
In-Reply-To: <1295034699-18863-1-git-send-email-s.hauer@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
arch/arm/boards/karo-tx28/tx28.c | 23 +++++++++++++++++++++++
arch/arm/mach-stm/Kconfig | 1 +
2 files changed, 24 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boards/karo-tx28/tx28.c b/arch/arm/boards/karo-tx28/tx28.c
index 6f4ef4e..5692171 100644
--- a/arch/arm/boards/karo-tx28/tx28.c
+++ b/arch/arm/boards/karo-tx28/tx28.c
@@ -21,6 +21,7 @@
#include <asm/io.h>
#include <generated/mach-types.h>
#include <mach/imx-regs.h>
+#include <asm/mmu.h>
static struct memory_platform_data ram_pdata = {
.name = "ram0",
@@ -82,6 +83,28 @@ static const uint32_t tx28_pad_setup[] = {
extern void base_board_init(void);
+#ifdef CONFIG_MMU
+static int tx28_mmu_init(void)
+{
+ mmu_init();
+
+ arm_create_section(0x40000000, 0x40000000, 128, PMD_SECT_DEF_CACHED);
+ arm_create_section(0x50000000, 0x40000000, 128, PMD_SECT_DEF_UNCACHED);
+
+ setup_dma_coherent(0x10000000);
+
+#if TEXT_BASE & (0x100000 - 1)
+#warning cannot create vector section. Adjust TEXT_BASE to a 1M boundary
+#else
+ arm_create_section(0x0, TEXT_BASE, 1, PMD_SECT_DEF_UNCACHED);
+#endif
+ mmu_enable();
+
+ return 0;
+}
+postcore_initcall(tx28_mmu_init);
+#endif
+
static int tx28_devices_init(void)
{
int i;
diff --git a/arch/arm/mach-stm/Kconfig b/arch/arm/mach-stm/Kconfig
index e47d9f1..402a9b7 100644
--- a/arch/arm/mach-stm/Kconfig
+++ b/arch/arm/mach-stm/Kconfig
@@ -55,6 +55,7 @@ choice
config MACH_TX28
bool "KARO tx28"
+ select HAVE_MMU
help
Say Y here if you are using the KARO TX28 CPU module.
--
1.7.2.3
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-01-14 19:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 19:51 some i.MX28 related patches Sascha Hauer
2011-01-14 19:51 ` [PATCH 1/7] fec i.MX28: Make it work with MMU on Sascha Hauer
2011-01-14 19:51 ` Sascha Hauer [this message]
2011-01-14 19:51 ` [PATCH 3/7] video stm/mx2x: simplify memory allocation Sascha Hauer
2011-01-15 15:00 ` Juergen Beisert
2011-01-15 15:10 ` Sascha Hauer
2011-01-14 19:51 ` [PATCH 4/7] video stm/mx2x: allow to pass in fb memory from platform data Sascha Hauer
2011-01-15 15:04 ` Juergen Beisert
2011-01-14 19:51 ` [PATCH 5/7] provide real barebox end variable Sascha Hauer
2011-01-15 1:50 ` Jean-Christophe PLAGNIOL-VILLARD
2011-01-15 14:48 ` Sascha Hauer
2011-01-14 19:51 ` [PATCH 6/7] ARM i.MX28 tx28: use a fixed framebuffer address Sascha Hauer
2011-01-14 19:51 ` [PATCH 7/7] ARM i.MX28 tx28 defconfig: enable MMU 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=1295034699-18863-3-git-send-email-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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