From: narmstrong@baylibre.com (Neil Armstrong)
To: linus-amlogic@lists.infradead.org
Subject: [U-Boot] [PATCH v2 1/1] ARM: meson: Extend mem_map to support 3GiB of RAM
Date: Wed, 26 Sep 2018 17:11:06 +0200 [thread overview]
Message-ID: <a0c52f5a-2e47-224c-7dd1-1f7d5c0206c0@baylibre.com> (raw)
In-Reply-To: <20180925143035.20621-1-ldevulder@suse.de>
Hi Loic,
On 25/09/2018 16:30, Loic Devulder wrote:
> The current mem_map definition for Meson SoCs has support for up
> to 2GiB of RAM. According to S905, S905X, S912 and S805X datasheets
> the DDR region is set from 0x00000000 to 0xBFFFFFFF, so mem_map's
> definition should be changed accordingly.
>
> It is also needed to be able to boot Khadas VIM2 board with S912
> SoC.
>
> Signed-off-by: Loic Devulder <ldevulder@suse.de>
> ---
> v2: set the correct size for devices memory map
>
> arch/arm/mach-meson/board.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm/mach-meson/board.c b/arch/arm/mach-meson/board.c
> index 1ef7e5a6d1..48096ca7cf 100644
> --- a/arch/arm/mach-meson/board.c
> +++ b/arch/arm/mach-meson/board.c
> @@ -111,13 +111,13 @@ static struct mm_region gx_mem_map[] = {
> {
> .virt = 0x0UL,
> .phys = 0x0UL,
> - .size = 0x80000000UL,
> + .size = 0xc0000000UL,
> .attrs = PTE_BLOCK_MEMTYPE(MT_NORMAL) |
> PTE_BLOCK_INNER_SHARE
> }, {
> - .virt = 0x80000000UL,
> - .phys = 0x80000000UL,
> - .size = 0x80000000UL,
> + .virt = 0xc0000000UL,
> + .phys = 0xc0000000UL,
> + .size = 0x30000000UL,
> .attrs = PTE_BLOCK_MEMTYPE(MT_DEVICE_NGNRNE) |
> PTE_BLOCK_NON_SHARE |
> PTE_BLOCK_PXN | PTE_BLOCK_UXN
>
You were faster than me, and already reviewed physically by Marek and Alexander !!
This will fix support for upcoming 3GiB capable boards !
Acked-by: Neil Armstrong <narmstrong@baylibre.com>
Neil
parent reply other threads:[~2018-09-26 15:11 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20180925143035.20621-1-ldevulder@suse.de>]
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=a0c52f5a-2e47-224c-7dd1-1f7d5c0206c0@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=linus-amlogic@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
all inboxes | Powered by JetHome®