From: "Nickle Wang via groups.io" <nicklew=nvidia.com@groups.io>
To: <devel@edk2.groups.io>
Cc: Abner Chang <abner.chang@amd.com>,
Igor Kulchytskyy <igork@ami.com>,
"Nick Ramirez" <nramirez@nvidia.com>
Subject: [edk2-devel] [edk2-redfish-client][PATCH 0/3] introduce Redfish Resource Config2 protocol.
Date: Mon, 4 Mar 2024 21:26:34 +0800 [thread overview]
Message-ID: <20240304132634.41025-1-nicklew@nvidia.com> (raw)
Introduce EDKII Redfish Resource Config2 Protocol so that caller can
pass Redfish data to callee when caller uses "expand" query parameter
to get multiple Redfish resources all together. Then, callee does not
get Redfish resource from Redfish service again and save the communication
effort between BIOS and Redfish service.
EdkIIRedfishConfigLib is updated to select Redfish Resource Config2
Protocol as first priority. If there is no Config2 protocol supported,
library will use config protocol automatically.
Pull request is created:
https://github.com/tianocore/edk2-redfish-client/pull/80
Signed-off-by: Nickle Wang <nicklew@nvidia.com>
Cc: Abner Chang <abner.chang@amd.com>
Cc: Igor Kulchytskyy <igork@ami.com>
Cc: Nick Ramirez <nramirez@nvidia.com>
Nickle Wang (3):
RedfishClientPkg: introduce Redfish resource config2 protocol.
RedfishClientPkg/Edk2RedfishResourceConfigLib: support config2
protocol
RedfishClientPkg/Features: support config2 protocol
RedfishClientPkg/RedfishClientPkg.dec | 2 +
.../EdkIIRedfishResourceConfigLib.inf | 4 +-
.../Library/EdkIIRedfishResourceConfigLib.h | 33 +-
.../EdkIIRedfishResourceConfig2Protocol.h | 148 +++++++
.../EdkIIRedfishResourceConfigInternal.h | 44 ++
.../Features/Bios/v1_0_9/Common/BiosCommon.c | 14 +-
.../BootOptionCollectionDxe.c | 14 +-
.../ComputerSystemCollectionDxe.c | 16 +-
.../MemoryCollectionDxe/MemoryCollectionDxe.c | 16 +-
.../EdkIIRedfishResourceConfigLib.c | 391 ++++++++++++++----
10 files changed, 565 insertions(+), 117 deletions(-)
create mode 100644 RedfishClientPkg/Include/Protocol/EdkIIRedfishResourceConfig2Protocol.h
create mode 100644 RedfishClientPkg/Library/EdkIIRedfishResourceConfigLib/EdkIIRedfishResourceConfigInternal.h
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#116314): https://edk2.groups.io/g/devel/message/116314
Mute This Topic: https://groups.io/mt/104721505/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next reply other threads:[~2024-03-04 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 13:26 Nickle Wang via groups.io [this message]
2024-03-05 2:26 ` [edk2-devel] [edk2-redfish-client][PATCH 0/3] introduce Redfish Resource Config2 protocol Chang, Abner via groups.io
2024-03-05 3:22 ` Nickle Wang via groups.io
2024-03-05 6:31 ` Chang, Abner via groups.io
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=20240304132634.41025-1-nicklew@nvidia.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