From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: qemu-devel@nongnu.org
Cc: edgar.iglesias@xilinx.com, peter.maydell@linaro.org,
luc@lmichel.fr, sai.pavan.boddu@xilinx.com,
frasse.iglesias@gmail.com, alistair@alistair23.me,
richard.henderson@linaro.org, f4bug@amsat.org,
francisco.iglesias@xilinx.com, frederic.konrad@adacore.com,
qemu-arm@nongnu.org
Subject: [PATCH v2 0/6] hw/arm: zynqmp: Add CRF and APU control to support PSCI
Date: Thu, 3 Feb 2022 15:01:35 +0100 [thread overview]
Message-ID: <20220203140141.310870-1-edgar.iglesias@gmail.com> (raw)
From: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>
This adds the necessary modeling to support some of our firmware
tests at EL3 implementing PSCI (TBM). These are the test-cases
that were previously relying on QEMU's builtin PSCI emulation.
I've only tested this on top of Peter's recent PSCI emulation fixes.
Cheers,
Edgar
ChangeLog:
v1 -> v2:
* crf: Change APU_MAX_CPU to CRF_MAX_CPU
* crf: Remove empty interfaces
* crf: Add include guards
* apu-ctrl: Change NUM_CPUS to APU_MAX_CPU
* apu-ctrl: Fix indentation
* apu-ctrl: Remove empty interfaces
* apu-ctrl: Add include guards
* xlnx-zynqmp: Add comment clarifying SER/DESerializer
Edgar E. Iglesias (6):
hw/arm/xlnx-zynqmp: Add an unimplemented SERDES area
target/arm: Make rvbar settable after realize
hw/misc: Add a model of the Xilinx ZynqMP CRF
hw/arm/xlnx-zynqmp: Connect the ZynqMP CRF
hw/misc: Add a model of the Xilinx ZynqMP APU Control
hw/arm/xlnx-zynqmp: Connect the ZynqMP APU Control
include/hw/arm/xlnx-zynqmp.h | 4 +
include/hw/misc/xlnx-zynqmp-apu-ctrl.h | 95 +++++++++
include/hw/misc/xlnx-zynqmp-crf.h | 213 ++++++++++++++++++++
hw/arm/xlnx-zynqmp.c | 46 ++++-
hw/misc/xlnx-zynqmp-apu-ctrl.c | 254 +++++++++++++++++++++++
hw/misc/xlnx-zynqmp-crf.c | 267 +++++++++++++++++++++++++
target/arm/cpu.c | 7 +-
hw/misc/meson.build | 2 +
8 files changed, 882 insertions(+), 6 deletions(-)
create mode 100644 include/hw/misc/xlnx-zynqmp-apu-ctrl.h
create mode 100644 include/hw/misc/xlnx-zynqmp-crf.h
create mode 100644 hw/misc/xlnx-zynqmp-apu-ctrl.c
create mode 100644 hw/misc/xlnx-zynqmp-crf.c
--
2.25.1
next reply other threads:[~2022-02-03 14:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 14:01 Edgar E. Iglesias [this message]
2022-02-03 14:01 ` [PATCH v2 1/6] hw/arm/xlnx-zynqmp: Add an unimplemented SERDES area Edgar E. Iglesias
2022-02-03 14:01 ` [PATCH v2 2/6] target/arm: Make rvbar settable after realize Edgar E. Iglesias
2022-02-03 20:33 ` Luc Michel
2022-02-03 14:01 ` [PATCH v2 3/6] hw/misc: Add a model of the Xilinx ZynqMP CRF Edgar E. Iglesias
2022-02-15 17:20 ` Peter Maydell
2022-02-18 13:37 ` Peter Maydell
2022-02-18 22:00 ` Edgar E. Iglesias
2022-02-03 14:01 ` [PATCH v2 4/6] hw/arm/xlnx-zynqmp: Connect the " Edgar E. Iglesias
2022-02-03 14:01 ` [PATCH v2 5/6] hw/misc: Add a model of the Xilinx ZynqMP APU Control Edgar E. Iglesias
2022-02-03 20:44 ` Luc Michel
2022-02-03 14:01 ` [PATCH v2 6/6] hw/arm/xlnx-zynqmp: Connect the " Edgar E. Iglesias
2022-02-03 20:46 ` Luc Michel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220203140141.310870-1-edgar.iglesias@gmail.com \
--to=edgar.iglesias@gmail.com \
--cc=alistair@alistair23.me \
--cc=edgar.iglesias@xilinx.com \
--cc=f4bug@amsat.org \
--cc=francisco.iglesias@xilinx.com \
--cc=frasse.iglesias@gmail.com \
--cc=frederic.konrad@adacore.com \
--cc=luc@lmichel.fr \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sai.pavan.boddu@xilinx.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).