From: "Sunil V L" <sunilvl@ventanamicro.com>
To: devel@edk2.groups.io
Cc: Sunil V L <sunilvl@ventanamicro.com>
Subject: [PATCH 0/5] Add UEFI-SCT test cases for RISCV_EFI_BOOT_PROTOCOL
Date: Thu, 9 Jun 2022 15:57:04 +0530 [thread overview]
Message-ID: <20220609102709.957985-1-sunilvl@ventanamicro.com> (raw)
RISC-V platforms need to support new RISCV_EFI_BOOT_PROTOCOL
to communicate the boot hart ID to the OS. This patch series adds
the test cases to UEFI SCT for this protocol.
The protocol spec is maintained at:
https://github.com/riscv-non-isa/riscv-uefi
These tests are tested with u-boot and EDK2.
Sunil V L (5):
uefi-sct/SctPkg: Add header file for RISCV_EFI_BOOT_PROTOCOL
uefi-sct/SctPkg: Add test cases for RISCV_EFI_BOOT_PROTOCOL
uefi-sct/SctPkg: Build test cases of RISCV_EFI_BOOT_PROTOCOL
uefi-sct/SctPkg: Install RISCV_EFI_BOOT_PROTOCOL test module
uefi-sct/SctPkg: Add a category for RISCV_EFI_BOOT_PROTOCOL
uefi-sct/SctPkg/CommonGenFramework.sh | 4 +
uefi-sct/SctPkg/Config/Data/Category.ini | 6 +
.../EFI/Protocol/RiscV/BlackBoxTest/Guid.c | 38 ++++
.../EFI/Protocol/RiscV/BlackBoxTest/Guid.h | 50 +++++
.../BlackBoxTest/RiscVBootProtocolBBTest.inf | 50 +++++
.../RiscVBootProtocolBBTestConformance.c | 171 ++++++++++++++++++
.../RiscVBootProtocolBBTestFunction.c | 124 +++++++++++++
.../RiscVBootProtocolBBTestMain.c | 122 +++++++++++++
.../RiscVBootProtocolBBTestMain.h | 112 ++++++++++++
uefi-sct/SctPkg/UEFI/Protocol/RiscVBoot.h | 72 ++++++++
uefi-sct/SctPkg/UEFI/UEFI.dec | 1 +
uefi-sct/SctPkg/UEFI/UEFI_SCT.dsc | 3 +
12 files changed, 753 insertions(+)
create mode 100644 uefi-sct/SctPkg/TestCase/UEFI/EFI/Protocol/RiscV/BlackBoxTest/Guid.c
create mode 100644 uefi-sct/SctPkg/TestCase/UEFI/EFI/Protocol/RiscV/BlackBoxTest/Guid.h
create mode 100644 uefi-sct/SctPkg/TestCase/UEFI/EFI/Protocol/RiscV/BlackBoxTest/RiscVBootProtocolBBTest.inf
create mode 100644 uefi-sct/SctPkg/TestCase/UEFI/EFI/Protocol/RiscV/BlackBoxTest/RiscVBootProtocolBBTestConformance.c
create mode 100644 uefi-sct/SctPkg/TestCase/UEFI/EFI/Protocol/RiscV/BlackBoxTest/RiscVBootProtocolBBTestFunction.c
create mode 100644 uefi-sct/SctPkg/TestCase/UEFI/EFI/Protocol/RiscV/BlackBoxTest/RiscVBootProtocolBBTestMain.c
create mode 100644 uefi-sct/SctPkg/TestCase/UEFI/EFI/Protocol/RiscV/BlackBoxTest/RiscVBootProtocolBBTestMain.h
create mode 100644 uefi-sct/SctPkg/UEFI/Protocol/RiscVBoot.h
--
2.25.1
next reply other threads:[~2022-06-09 10:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 10:27 Sunil V L [this message]
2022-06-09 10:27 ` [PATCH 1/5] uefi-sct/SctPkg: Add header file for RISCV_EFI_BOOT_PROTOCOL Sunil V L
2022-09-07 14:28 ` [edk2-devel] " G Edhaya Chandran
2022-06-09 10:27 ` [PATCH 2/5] uefi-sct/SctPkg: Add test cases " Sunil V L
2022-09-07 14:28 ` [edk2-devel] " G Edhaya Chandran
2022-06-09 10:27 ` [PATCH 3/5] uefi-sct/SctPkg: Build test cases of RISCV_EFI_BOOT_PROTOCOL Sunil V L
2022-09-07 14:29 ` [edk2-devel] " G Edhaya Chandran
2022-06-09 10:27 ` [PATCH 4/5] uefi-sct/SctPkg: Install RISCV_EFI_BOOT_PROTOCOL test module Sunil V L
2022-09-07 14:29 ` [edk2-devel] " G Edhaya Chandran
2022-06-09 10:27 ` [PATCH 5/5] uefi-sct/SctPkg: Add a category for RISCV_EFI_BOOT_PROTOCOL Sunil V L
2022-09-07 14:29 ` [edk2-devel] " G Edhaya Chandran
2022-09-07 14:27 ` [edk2-devel] [PATCH 0/5] Add UEFI-SCT test cases " G Edhaya Chandran
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=20220609102709.957985-1-sunilvl@ventanamicro.com \
--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