From: "Xiong Yining" <xiongyining1480@phytium.com.cn>
To: devel@edk2.groups.io
Cc: Xiong Yining <xiongyining1480@phytium.com.cn>
Subject: [edk2-devel] [PATCH v5 0/7] get rid of DeviceTree from SbsaQemu
Date: Wed, 31 Jan 2024 13:24:00 +0000 [thread overview]
Message-ID: <20240131132400.3022662-1-xiongyining1480@phytium.com.cn> (raw)
Many thanks to Marcin Juszkiewicz for his previous work on get rid of DeviceTree from
SbsaQemu https://openfw.io/edk2-devel/20240124-no-dt-for-cpu-v3-0-5375fcf09037@linaro.org/.
To stop the use of DeviceTree on the EDK2 , we add the support for getting the memory
information via SMC calls based on his patch.
TF-A part: https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/25891.
To be compatible with old TF-A, if the SMC calls failed, we can pase DeviceTree data
directly.
Changes in v4:
-patch 6 add the support for getting the hardware information of memory via SMC calls.
-patch 7 add the fallbacks of DeviceTree when SMC calls defined on patch 6 failled.
-replace FdtHelperGetMpidr() with SbsaQemuGetMpidr() on patch 4 to compile successfully.
Changes in v5:
-add the patch "Platform/SbsaQemu: add SbsaQemuHardwareInfoLib" provided by Marcin Juszkiewicz.
Marcin Juszkiewicz (5):
Platform/SbsaQemu: add SbsaQemuHardwareInfoLib
Platform/SbsaQemu: read amount of cpus during init
Platform/SbsaQemu: use PcdCoreCount directly
Platform/SbsaQemu: move FdtHandlerLib to SbsaQemuHardwareInfoLib
Platform/SbsaQemu: hang if there is no cpu information
Xiong Yining (2):
Platform/SbsaQemu: get the information of memory via SMC calls
Platform/SbsaQemu: add DeviceTree fallbacks to parse memory
information
Platform/Qemu/SbsaQemu/SbsaQemu.dsc | 4 +-
.../Qemu/SbsaQemu/OemMiscLib/OemMiscLib.inf | 6 +-
.../SbsaQemuAcpiDxe/SbsaQemuAcpiDxe.inf | 4 +-
.../SbsaQemuPlatformDxe.inf | 4 +-
.../Library/FdtHelperLib/FdtHelperLib.inf | 33 --
.../SbsaQemuHardwareInfoLib.inf | 34 ++
.../Library/SbsaQemuLib/SbsaQemuLib.inf | 2 +-
.../Include/IndustryStandard/SbsaQemuSmc.h | 17 +-
.../SbsaQemu/Include/Library/FdtHelperLib.h | 36 --
.../Include/Library/SbsaQemuHardwareInfoLib.h | 73 ++++
.../Qemu/SbsaQemu/OemMiscLib/OemMiscLib.c | 10 +-
.../Drivers/SbsaQemuAcpiDxe/SbsaQemuAcpiDxe.c | 15 +-
.../SbsaQemuPlatformDxe/SbsaQemuPlatformDxe.c | 9 +-
.../Library/FdtHelperLib/FdtHelperLib.c | 98 -----
.../SbsaQemuHardwareInfoLib.c | 354 ++++++++++++++++++
.../Library/SbsaQemuLib/SbsaQemuMem.c | 54 +--
16 files changed, 511 insertions(+), 242 deletions(-)
delete mode 100644 Silicon/Qemu/SbsaQemu/Library/FdtHelperLib/FdtHelperLib.inf
create mode 100644 Silicon/Qemu/SbsaQemu/Library/SbsaQemuHardwareInfoLib/SbsaQemuHardwareInfoLib.inf
delete mode 100644 Silicon/Qemu/SbsaQemu/Include/Library/FdtHelperLib.h
create mode 100644 Silicon/Qemu/SbsaQemu/Include/Library/SbsaQemuHardwareInfoLib.h
delete mode 100644 Silicon/Qemu/SbsaQemu/Library/FdtHelperLib/FdtHelperLib.c
create mode 100644 Silicon/Qemu/SbsaQemu/Library/SbsaQemuHardwareInfoLib/SbsaQemuHardwareInfoLib.c
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#114896): https://edk2.groups.io/g/devel/message/114896
Mute This Topic: https://groups.io/mt/104074475/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
reply other threads:[~2024-01-31 13:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-list 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=20240131132400.3022662-1-xiongyining1480@phytium.com.cn \
--to=devel@edk2.groups.io \
/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