diff options
author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2016-06-27 19:31:05 +0900 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2016-07-14 18:22:16 -0400 |
commit | 6b6024eadb96bc471643bd183fe940fb657bef83 (patch) | |
tree | 35c09153ac815289e395ddbf7678587c0232c114 /arch/arm/cpu/armv7/s5p-common | |
parent | 3a592a1349ac3961b0f4f2db0a8d9f128225d897 (diff) |
arm64: add better and more generic spin-table support
There are two enable methods supported by ARM64 Linux; psci and
spin-table. The latter is simpler and helpful for quick SoC bring
up. My main motivation for this patch is to improve the spin-table
support, which allows us to boot an ARMv8 system without the ARM
Trusted Firmware.
Currently, we have multi-entry code in arch/arm/cpu/armv8/start.S
and the spin-table is supported in a really ad-hoc way, and I see
some problems:
- We must hard-code CPU_RELEASE_ADDR so that it matches the
"cpu-release-addr" property in the DT that comes from the
kernel tree.
- The Documentation/arm64/booting.txt in Linux requires that
the release address must be zero-initialized, but it is not
cared by the common code in U-Boot. We must do it in a board
function.
- There is no systematic way to protect the spin-table code from
the kernel. We are supposed to do it in a board specific manner,
but it is difficult to predict where the spin-table code will be
located after the relocation. So, it also makes difficult to
hard-code /memreserve/ in the DT of the kernel.
So, here is a patch to solve those problems; the DT is run-time
modified to reserve the spin-table code (+ cpu-release-addr).
Also, the "cpu-release-addr" property is set to an appropriate
address after the relocation, which means we no longer need the
hard-coded CPU_RELEASE_ADDR.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Diffstat (limited to 'arch/arm/cpu/armv7/s5p-common')
0 files changed, 0 insertions, 0 deletions