| Message ID | 8a0c6d6641e7e9a932bb62ec4f4d700339234398.1578302491.git.michal.simek@xilinx.com |
|---|---|
| State | Accepted |
| Commit | ddb55ff8a66dabe3365735eff9f901bb259c223f |
| Headers | show |
| Series | [v2] arm64: versal: Enable board_late_init calling | expand |
diff --git a/configs/xilinx_versal_virt_defconfig b/configs/xilinx_versal_virt_defconfig index 11428e1e03c1..6488bca2c004 100644 --- a/configs/xilinx_versal_virt_defconfig +++ b/configs/xilinx_versal_virt_defconfig @@ -9,7 +9,6 @@ CONFIG_FIT_VERBOSE=y # CONFIG_ARCH_FIXUP_FDT_MEMORY is not set CONFIG_BOOTDELAY=5 CONFIG_SUPPORT_RAW_INITRD=y -# CONFIG_BOARD_LATE_INIT is not set # CONFIG_DISPLAY_CPUINFO is not set CONFIG_BOARD_EARLY_INIT_R=y CONFIG_HUSH_PARSER=y
Qemu v4.2.0 maps bootmode registers to address space which was the reason why board_late_init() was disabled and accesses were failing. With new Qemu board_late_init() can be called without any issue. Signed-off-by: Michal Simek <michal.simek at xilinx.com> --- Changes in v2: - Remove QEMU version just for versal_virt because v4.2.0 was setup globally - Change subject to target just Versal configs/xilinx_versal_virt_defconfig | 1 - 1 file changed, 1 deletion(-)