On 27.01.22 16:46, Peter Maydell wrote:
Change the Xilinx ZynqMP-based board xlnx-zcu102 to use the new
boot.c functionality to allow us to enable psci-conduit only if
the guest is being booted in EL1 or EL2, so that if the user runs
guest EL3 firmware code our PSCI emulation doesn't get in its
way.
To do this we stop setting the psci-conduit property on the CPU
objects in the SoC code, and instead set the psci_conduit field in
the arm_boot_info struct to tell the common boot loader code that
we'd like PSCI if the guest is starting at an EL that it makes
sense with.
Note that this means that EL3 guest code will have no way
to power on secondary cores, because we don't model any
kind of power controller that does that on this SoC.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
It's been a while since I worked with ZynqMP, but typically your ATF in
EL3 will want to talk to a microblaze firmware blob on the PMU.
I only see a stand alone PMU machine for microblaze and a PMU IRQ
handling I/O block in QEMU, but nothing that would listen to the events.
So I'm fairly sure it will be broken after this patch - and really only
worked by accident before.