From: John Watts <contact@jookia.org>
To: barebox@lists.infradead.org
Cc: John Watts <contact@jookia.org>
Subject: [PATCH v2] ARM: i.MX6: Specify OCRAM base address and size
Date: Fri, 27 Jan 2023 06:02:58 +1100 [thread overview]
Message-ID: <20230126190258.110423-1-contact@jookia.org> (raw)
In-Reply-To: <20230126183624.85500-1-contact@jookia.org>
The i.MX6 includes some on-chip RAM: 128KiB on most variants, with 256KiB on
the Dual and Quad variants.
This region is where the first stage of Barebox gets loaded if RAM
initialization isn't hard coded using DCD information.
Add the base address and size so it can be used to calculate where to put the
stack at boot.
Signed-off-by: John Watts <contact@jookia.org>
---
Changes v1 -> v2:
- Fixed wrong size (thanks Marco!)
---
arch/arm/mach-imx/include/mach/imx6-regs.h | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/mach-imx/include/mach/imx6-regs.h b/arch/arm/mach-imx/include/mach/imx6-regs.h
index 39e2751533..89a3b267c6 100644
--- a/arch/arm/mach-imx/include/mach/imx6-regs.h
+++ b/arch/arm/mach-imx/include/mach/imx6-regs.h
@@ -3,6 +3,12 @@
#ifndef __MACH_IMX6_REGS_H
#define __MACH_IMX6_REGS_H
+#include <linux/sizes.h>
+
+/* Set MAX_SIZE to 128K, only the Quad and Dual have 256K */
+#define MX6_OCRAM_BASE_ADDR 0x00900000
+#define MX6_OCRAM_MAX_SIZE SZ_128K
+
#define MX6_APBH_BASE_ADDR 0x00110000
#define MX6_GPMI_BASE_ADDR 0x00112000
#define MX6_BCH_BASE_ADDR 0x00114000
--
2.39.1
next prev parent reply other threads:[~2023-01-26 19:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 18:36 [PATCH] " John Watts
2023-01-26 18:45 ` Marco Felsch
2023-01-26 19:02 ` John Watts [this message]
2023-01-27 8:06 ` [PATCH v2] " Marco Felsch
2023-01-27 8:56 ` John Watts
2023-01-30 8:08 ` Sascha Hauer
2023-01-30 8:08 ` 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=20230126190258.110423-1-contact@jookia.org \
--to=contact@jookia.org \
--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