u-boot/arch/arm/mach-uniphier/arm64/Makefile at aaebb900c60c12110f6dd2ae5ec3dc83984f8a18 - Mirrors/u-boot - CherryKitten

Mirrors/u-boot

mirror of https://github.com/AsahiLinux/u-boot synced 2024-11-18 02:38:56 +00:00

Masahiro Yamada 1f8e6a670c Revert "ARM: uniphier: add weird workaround code for LD20"

This reverts commit 45f41c134b.

This weird workaround was the best I came up with at that time
to boot U-Boot from TF-A.

I noticed U-Boot successfully boots on LD20 (i.e. CA72 CPU) by using
the latest TF-A.

Specifically, since the following TF-A commit, U-Boot runs at EL2
instead of EL1, and this issue went away as a side-effect.

|commit f998a052fd94ea082833109f25b94ed5bfa24e8b
|Author: Masahiro Yamada <yamada.masahiro@socionext.com>
|Date:   Thu Jul 25 10:57:38 2019 +0900
|
|    uniphier: run BL33 at EL2
|
|    All the SoCs in 64-bit UniPhier SoC family support EL2.
|
|    Just hard-code MODE_EL2 instead of using el_implemented() helper.
|
|    Change-Id: I7ab48002c5205bc8c013e1b46313b57d6c431db0
|    Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>

However, if I reverted that, this problem would come back, presumably
because some EL1 code in U-Boot triggers this issue.

Now that commit f8ddd8cbb5 ("arm64: issue ISB after updating system
registers") fixed this issue properly, this weird workaround is no
longer needed irrespective of the exception level at which U-Boot runs.

Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>

2020-07-11 21:30:21 +09:00

3 lines

56 B

Makefile

Raw Blame History

	`# SPDX-License-Identifier: GPL-2.0+`

	`obj-y += mem_map.o`