u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Dmitry Malkin <dmitry@bedrocksystems.com>
To: u-boot@lists.denx.de
Subject: [RFC PATCH 2/2] rpi5: initial support
Date: Sat, 18 Nov 2023 17:41:59 +0100	[thread overview]
Message-ID: <CAKRNjQ0CKPJkR8ONivsOrb3fr=J-0f7ubvVfD7KWdo=g2dKCrA@mail.gmail.com> (raw)

rpi5: add initial memory map for bcm2712

---
 arch/arm/mach-bcm283x/init.c | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/arch/arm/mach-bcm283x/init.c b/arch/arm/mach-bcm283x/init.c
index d76c8e5eb2..3424b116d5 100644
--- a/arch/arm/mach-bcm283x/init.c
+++ b/arch/arm/mach-bcm283x/init.c
@@ -68,6 +68,26 @@ static struct mm_region
bcm2711_mem_map[MEM_MAP_MAX_ENTRIES] = {
     }
 };

+static struct mm_region bcm2712_mem_map[MEM_MAP_MAX_ENTRIES] = {
+    {
+        .virt = 0x00000000UL,
+        .phys = 0x00000000UL,
+        .size = 0x3f800000UL,
+        .attrs = PTE_BLOCK_MEMTYPE(MT_NORMAL) |
+             PTE_BLOCK_INNER_SHARE
+    }, {
+        .virt = 0x107c000000UL,
+        .phys = 0x107c000000UL,
+        .size = 0x0004000000UL,
+        .attrs = PTE_BLOCK_MEMTYPE(MT_DEVICE_NGNRNE) |
+             PTE_BLOCK_NON_SHARE |
+             PTE_BLOCK_PXN | PTE_BLOCK_UXN
+    }, {
+        /* List terminator */
+        0,
+    }
+};
+
 struct mm_region *mem_map = bcm283x_mem_map;

 /*
@@ -78,6 +98,7 @@ static const struct udevice_id board_ids[] = {
     { .compatible = "brcm,bcm2837", .data = (ulong)&bcm283x_mem_map},
     { .compatible = "brcm,bcm2838", .data = (ulong)&bcm2711_mem_map},
     { .compatible = "brcm,bcm2711", .data = (ulong)&bcm2711_mem_map},
+    { .compatible = "brcm,bcm2712", .data = (ulong)&bcm2712_mem_map},
     { },
 };

-- 
2.40.1

                 reply	other threads:[~2023-11-18 16:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAKRNjQ0CKPJkR8ONivsOrb3fr=J-0f7ubvVfD7KWdo=g2dKCrA@mail.gmail.com' \
    --to=dmitry@bedrocksystems.com \
    --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;
as well as URLs for NNTP newsgroup(s).