diff options
author | Ard Biesheuvel <ardb@kernel.org> | 2020-11-17 08:41:01 +0100 |
---|---|---|
committer | Russell King <rmk+kernel@armlinux.org.uk> | 2020-12-21 12:19:21 +0100 |
commit | 10fce53c0ef8f6e79115c3d9e0d7ea1338c3fa37 (patch) | |
tree | 5b03a336058bcf12c9e1dad16ab78f0f6a4546b0 /samples/nitro_enclaves | |
parent | ARM: 9038/1: Link with '-z norelro' (diff) | |
download | linux-10fce53c0ef8f6e79115c3d9e0d7ea1338c3fa37.tar.xz linux-10fce53c0ef8f6e79115c3d9e0d7ea1338c3fa37.zip |
ARM: 9027/1: head.S: explicitly map DT even if it lives in the first physical section
The early ATAGS/DT mapping code uses SECTION_SHIFT to mask low order
bits of R2, and decides that no ATAGS/DTB were provided if the resulting
value is 0x0.
This means that on systems where DRAM starts at 0x0 (such as Raspberry
Pi), no explicit mapping of the DT will be created if R2 points into the
first 1 MB section of memory. This was not a problem before, because the
decompressed kernel is loaded at the base of DRAM and mapped using
sections as well, and so as long as the DT is referenced via a virtual
address that uses the same translation (the linear map, in this case),
things work fine.
However, commit 7a1be318f579 ("9012/1: move device tree mapping out of
linear region") changes this, and now the DT is referenced via a virtual
address that is disjoint from the linear mapping of DRAM, and so we need
the early code to create the DT mapping unconditionally.
So let's create the early DT mapping for any value of R2 != 0x0.
Reported-by: "kernelci.org bot" <bot@kernelci.org>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Diffstat (limited to 'samples/nitro_enclaves')
0 files changed, 0 insertions, 0 deletions