From: Tong Ho <tong.ho@xilinx.com>
To: <qemu-arm@nongnu.org>
Cc: edgar.iglesias@gmail.com, alistair@alistair23.me,
tong.ho@xilinx.com, qemu-devel@nongnu.org,
peter.maydell@linaro.org
Subject: [PATCH 0/9] hw/nvram: hw/arm: Introduce Xilinx eFUSE and BBRAM
Date: Wed, 18 Aug 2021 21:02:59 -0700 [thread overview]
Message-ID: <20210819040308.675057-1-tong.ho@xilinx.com> (raw)
This series implements the Xilinx eFUSE and BBRAM devices for
the Versal and ZynqMP product families.
Furthermore, both new devices are connected to the xlnx-versal-virt
board and the xlnx-zcu102 board.
See changes in docs/system/arm/xlnx-versal-virt.rst for detail.
Tong Ho (9):
docs/system/arm: xlnx-versal-virt: BBRAM and eFUSE Usage
hw/nvram: Introduce Xilinx eFuse QOM
hw/nvram: Introduce Xilinx Versal eFuse device
hw/nvram: Introduce Xilinx ZynqMP eFuse device
hw/nvram: Introduce Xilinx battery-backed ram
hw/arm: xlnx-versal: Add Xilinx BBRAM device
hw/arm: xlnx-versal: Add Xilinx eFUSE device
hw/arm: xlnx-zynqmp: Add Xilinx BBRAM device
hw/arm: xlnx-zynqmp: Add Xilinx eFUSE device
docs/system/arm/xlnx-versal-virt.rst | 49 ++
hw/arm/xlnx-versal-virt.c | 57 ++
hw/arm/xlnx-versal.c | 57 ++
hw/arm/xlnx-zynqmp.c | 50 ++
hw/nvram/Kconfig | 17 +
hw/nvram/meson.build | 11 +
hw/nvram/xlnx-bbram.c | 536 +++++++++++++++++
hw/nvram/xlnx-efuse-crc.c | 118 ++++
hw/nvram/xlnx-efuse.c | 253 ++++++++
hw/nvram/xlnx-versal-efuse-cache.c | 141 +++++
hw/nvram/xlnx-versal-efuse-ctrl.c | 786 ++++++++++++++++++++++++
hw/nvram/xlnx-zynqmp-efuse.c | 861 +++++++++++++++++++++++++++
include/hw/arm/xlnx-versal.h | 17 +
include/hw/arm/xlnx-zynqmp.h | 5 +
include/hw/nvram/xlnx-bbram.h | 55 ++
include/hw/nvram/xlnx-efuse.h | 80 +++
include/hw/nvram/xlnx-versal-efuse.h | 62 ++
include/hw/nvram/xlnx-zynqmp-efuse.h | 45 ++
18 files changed, 3200 insertions(+)
create mode 100644 hw/nvram/xlnx-bbram.c
create mode 100644 hw/nvram/xlnx-efuse-crc.c
create mode 100644 hw/nvram/xlnx-efuse.c
create mode 100644 hw/nvram/xlnx-versal-efuse-cache.c
create mode 100644 hw/nvram/xlnx-versal-efuse-ctrl.c
create mode 100644 hw/nvram/xlnx-zynqmp-efuse.c
create mode 100644 include/hw/nvram/xlnx-bbram.h
create mode 100644 include/hw/nvram/xlnx-efuse.h
create mode 100644 include/hw/nvram/xlnx-versal-efuse.h
create mode 100644 include/hw/nvram/xlnx-zynqmp-efuse.h
--
2.25.1
next reply other threads:[~2021-08-19 4:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 4:02 Tong Ho [this message]
2021-08-19 4:03 ` [PATCH 1/9] docs/system/arm: xlnx-versal-virt: BBRAM and eFUSE Usage Tong Ho
2021-08-19 4:03 ` [PATCH 2/9] hw/nvram: Introduce Xilinx eFuse QOM Tong Ho
2021-08-19 4:03 ` [PATCH 3/9] hw/nvram: Introduce Xilinx Versal eFuse device Tong Ho
2021-08-19 4:03 ` [PATCH 4/9] hw/nvram: Introduce Xilinx ZynqMP " Tong Ho
2021-08-19 4:03 ` [PATCH 5/9] hw/nvram: Introduce Xilinx battery-backed ram Tong Ho
2021-08-19 4:03 ` [PATCH 6/9] hw/arm: xlnx-versal: Add Xilinx BBRAM device Tong Ho
2021-08-19 4:03 ` [PATCH 7/9] hw/arm: xlnx-versal: Add Xilinx eFUSE device Tong Ho
2021-08-19 4:03 ` [PATCH 8/9] hw/arm: xlnx-zynqmp: Add Xilinx BBRAM device Tong Ho
2021-08-19 4:03 ` [PATCH 9/9] hw/arm: xlnx-zynqmp: Add Xilinx eFUSE device Tong Ho
2021-08-19 15:08 ` [PATCH 0/9] hw/nvram: hw/arm: Introduce Xilinx eFUSE and BBRAM Edgar E. Iglesias
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=20210819040308.675057-1-tong.ho@xilinx.com \
--to=tong.ho@xilinx.com \
--cc=alistair@alistair23.me \
--cc=edgar.iglesias@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).