spdm: limited implementation of SPDM1.3 GET_CSR support #42
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Wilfred Mallawa <wilfred.mallawa@wdc.com>
This implements the `libspdm_gen_csr_ex()` fn to allow us to continue to support a `GET_CSR` in libspdm 1.3. This is limited in the sense that we don't support CsrTrackingTags yet. That is, a responder will immediately process the request and return the CSR without needing a reset, as such, a requester must not request to seek a CsrTrackingTag. Assertions are in place to catch such a case. Signed-off-by: Wilfred Mallawa <wilfred.mallawa@wdc.com>
|
ping! |
alistair23
approved these changes
Feb 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This implements the
libspdm_gen_csr_ex()fn to allow usto continue to support a
GET_CSRin libspdm SPDM >= 1.3. This is limitedin the sense that we don't support CsrTrackingTags yet.
That is, a responder will immediately process the request and return the
CSR without needing a reset, as such, a requester must not request to
seek a CsrTrackingTag. Assertions are in place to catch such a case.