18 Jan, 2020
1 commit
-
This function related to timer and most of the timer functions are in
time.h, so move this function there.Signed-off-by: Simon Glass
14 Jan, 2020
7 commits
-
Follow i.MX, Sunxi, RISC-V and Rockchip to generate u-boot.itb which
includes U-Boot proper, ATF and DTBs in FIT format. ZynqMP supports FIT for
quite a long time but with using out of tree solution. The patch is filling
this gap.Tested on zcu102, zcu104 and zcu100/Ultra96.
zcu100/Ultra96 v2.2 ATF build by:
make DEBUG=0 ZYNQMP_CONSOLE=cadence1 RESET_TO_BL31=1 PLAT=zynqmp bl31Signed-off-by: Michal Simek
-
handoff_setup() was used to generate fixed handoff structure for ATF on
ZynqMP platform.
Switching to bl2_plat_get_bl31_params() platform brings more flexibility
because information can be taken from fit image where /fit-images node is
created at run time.Signed-off-by: Michal Simek
-
Empty implementation should not return 0 (success) because that mean that
passed name matches the board configuration.Signed-off-by: Michal Simek
-
In past SPL_ZYNQMP_TWO_SDHCI symbol was introduced to handle boards with
two sdhci controllers. The problem was that U-Boot is registering
controllers based on aliases in DT but bootmode targets specific controller
ID. That's why on boards with one "second" sdhci controller bootmode was
pointing to second controller(MMC2) but alias was setup to mmc0 (the first
controller). And SPL requires to point to mmc0 in this case.Long time ago commit f101e4bd3703
("spl: add support for alternative boot device") added support for handling
multiple bootmodes in SPL. Use this functionality and setup second sdhci
controller as backup boot device.Below is table with behavior:
HW/bootmode bootorder
sd0/sd0 mmc0/mmc1 (mmc1 never called)
sd1/sd1 mmc1/mmc0 (mmc0 fails and mmc1 is called)
sd0+sd1/sd0 mmc0/mmc1 (mmc1 never called)
sd0+sd1/sd1 mmc1/mmc0 (mmc0 never called)All other bootmodes are not affected but order can be extended to cover
advance boot flows.Signed-off-by: Michal Simek
-
MIO34 is connected to POWER_KILL signal. When MIO configuration is done in
psu_init() and this pin is assigned to PMU but PMU configuration is not
loaded yet. PMU gpio output is high that means board is powered off
immediately.
The patch is fixing this sequence that MIO34 stays assing to ps gpio IP.
PMU config is loaded in SPL and then pin assigned to PMU through
psu_post_config_data().Signed-off-by: Michal Simek
-
There is no reason to clear bss and call board_init_r() from board_init_f()
beca it can be called directly from crt0_64.S with also support for SPL
stack relocation to SDRAM.
For more information please take a look at arch/arm/lib/crt0_64.SSigned-off-by: Michal Simek
-
Remove hardcoded base address of nand and replace it with the
value taken from device tree. Remove base address from header
file too.Signed-off-by: Ashok Reddy Soma
Signed-off-by: Michal Simek
03 Dec, 2019
2 commits
-
A number of board function belong in init.h with the others. Move them.
Signed-off-by: Simon Glass
Reviewed-by: Tom Rini -
These should be moved to driver model, but in the meantime, move them
out of the common header to help reduce its size.Signed-off-by: Simon Glass
Reviewed-by: Tom Rini
24 Oct, 2019
2 commits
-
Remove macros which use PM_SIP_SVC offset and convert invoke_smc() to
xilinx_pm_request() which do calculation with PM_SIP_SVC already.Signed-off-by: Michal Simek
-
versal_pm_request() and invoke_smc() are almost the same. Only one
difference is that versal_pm_request is adding PM_SIP_SVC offset to api_id.
The patch is moving platform implementation to firmware driver code for
synchronization.Signed-off-by: Michal Simek
Reviewed-by: Luca Ceresoli
08 Oct, 2019
5 commits
-
With new mailbox driver PMUFW configuration object can be loaded via the
same interface and there is no need to have pmu_ipc.c completely.Signed-off-by: Michal Simek
Reviewed-by: Luca Ceresoli -
Removes the old function to get the firmware version.
Signed-off-by: Ibai Erkiaga
Signed-off-by: Michal Simek -
New firmware header to place firmware specific macro and function
declarations. The patch also moves the macros defining PM operations as
well as some helper macros.Signed-off-by: Ibai Erkiaga
Signed-off-by: Michal Simek -
Cleanup PM ID handling by using enum values.
Signed-off-by: Michal Simek
Signed-off-by: Ibai Erkiaga
Signed-off-by: Michal Simek -
ZynqMP mailbox driver implementing IPI communication with PMU. This would
allow U-Boot SPL to communicate with PMUFW to request privileged
operations.Signed-off-by: Ibai Erkiaga
Signed-off-by: Michal Simek
30 Jul, 2019
1 commit
-
Optionally allow U-Boot to load a configuration object into the Power
Management Unit (PMU) firmware on Xilinx ZynqMP.The configuration object is required by the PMU FW to enable most SoC
peripherals. So far the only way to boot using U-Boot SPL was to hard-code
the configuration object in the PMU firmware. Allow a different boot
process, where the PMU FW is equal for any ZynqMP chip and its
configuration is passed at runtime by U-Boot SPL.All the code for Inter-processor communication with the PMU is isolated in
a new file (pmu_ipc.c). The code is inspired by the same feature as
implemented in the Xilinx First Stage Bootloader (FSBL) and Arm Trusted
Firmware:* https://github.com/Xilinx/embeddedsw/blob/fb647e6b4c00f5154eba52a88b948195b6f1dc2b/lib/sw_apps/zynqmp_fsbl/src/xfsbl_misc_drivers.c#L295
* https://github.com/ARM-software/arm-trusted-firmware/blob/c48d02bade88b07fa7f43aa44e5217f68e5d047f/plat/xilinx/zynqmp/pm_service/pm_api_sys.c#L357SPL logs on the console before loading the configuration object:
U-Boot SPL 2019.07-rc1-00511-gaec224515c87 (May 15 2019 - 08:43:41 +0200)
Loading PMUFW cfg obj (2008 bytes)
EL Level: EL3
...Signed-off-by: Luca Ceresoli
Signed-off-by: Michal Simek
16 Apr, 2019
2 commits
-
A missing CONFIG_ prefix while checking for this Kconfig variable makes the
check always fail. Fix it. While there also switch from the '#if defined'
form to the '#ifdef' form as the other checks in this function.Fixes: 35e2b92344b1 ("arm64: zynqmp: Fix logic around CONFIG_ZYNQ_SDHCI")
Signed-off-by: Luca Ceresoli
Signed-off-by: Michal Simek -
Just have better view on system.
Signed-off-by: Michal Simek
14 Feb, 2019
2 commits
-
Replace SDHCI controller listing by Kconfig symbol to let SPL know that
this board is using multiple SDHCIs controllers.
Kconfig help message should explain why this is needed.
Origin symbols were used in full u-boot but with moving to distro boot
this was fixed already.Signed-off-by: Michal Simek
-
All platforms have been converted to DM that's why there is no reason to
keep addresses in headers. They are all read from DT now.Signed-off-by: Michal Simek
Reviewed-by: Heiko Schocher
01 Feb, 2019
1 commit
-
Replace CONFIG_SPL_FAT_SUPPORT with CONFIG_SPL_FS_FAT so
obj-$(CONFIG_$(SPL_)FS_FAT) can be used to control the build in both
SPL and U-Boot.Signed-off-by: Tien Fong Chee
Reviewed-by: Simon Goldschmidt
Reviewed-by: Tom Rini
26 Jan, 2019
1 commit
-
The symbol CONFIG_SPL_DFU_SUPPORT in SPL build has the same
meaning as CONFIG_DFU in regular U-Boot. Drop the _SUPPORT
to allow for cleaner use in code.Signed-off-by: Andrew F. Davis
Reviewed-by: Tom Rini
Acked-by: Lukasz Majewski
24 Jan, 2019
2 commits
-
With DM in place there is no need to have GEM addresses in headers. None
is using them.Signed-off-by: Michal Simek
-
Similar changes was done for Zynq in past and this patch just follow
this pattern to separate cpu code from SoC code.Move arch/arm/cpu/armv8/zynqmp/* -> arch/arm/mach-zynqmp/*
And also fix references to these files.Based on
"ARM: zynq: move SoC sources to mach-zynq"
(sha1: 0107f2403669f764ab726d0d404e35bb9447bbcc)Signed-off-by: Michal Simek