From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH v2 1/3] arm: caches: protect dram_bank_mmu_setup access to bi_dram
Date: Fri, 1 May 2020 17:56:14 -0400 [thread overview]
Message-ID: <20200501215614.GL12564@bill-the-cat> (raw)
In-Reply-To: <20200424201957.v2.1.I64599059b66bacb531db38c67273754a145dbad8@changeid>
On Fri, Apr 24, 2020 at 08:20:15PM +0200, Patrick Delaunay wrote:
> Add protection in dram_bank_mmu_setup() to avoid access to bd->bi_dram
> before relocation.
>
> This patch allow to use the generic weak function dram_bank_mmu_setup
> to activate the MMU and the data cache in SPL or in U-Boot before
> relocation, when bd->bi_dram is not yet initialized.
>
> In this cases, the MMU must be initialized explicitly with
> mmu_set_region_dcache_behaviour function.
>
> Signed-off-by: Patrick Delaunay <patrick.delaunay@st.com>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200501/1dc99cc4/attachment.sig>
next prev parent reply other threads:[~2020-05-01 21:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 18:20 [PATCH v2 0/3] arm: caches: allow to activate dcache in SPL and in U-Boot pre-reloc Patrick Delaunay
2020-04-24 18:20 ` [PATCH v2 1/3] arm: caches: protect dram_bank_mmu_setup access to bi_dram Patrick Delaunay
2020-05-01 21:56 ` Tom Rini [this message]
2020-04-24 18:20 ` [PATCH v2 2/3] arm: caches: add DCACHE_DEFAULT_OPTION Patrick Delaunay
2020-05-01 21:56 ` Tom Rini
2020-04-24 18:20 ` [PATCH v2 3/3] arm: caches: manage phys_addr_t overflow in mmu_set_region_dcache_behaviour Patrick Delaunay
2020-05-01 21:56 ` Tom Rini
2020-04-28 19:49 ` [PATCH v2 0/3] arm: caches: allow to activate dcache in SPL and in U-Boot pre-reloc Tom Rini
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=20200501215614.GL12564@bill-the-cat \
--to=trini@konsulko.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