aboutsummaryrefslogtreecommitdiff
path: root/hdata/memory.c
diff options
context:
space:
mode:
authorChristophe Lombard <clombard@linux.ibm.com>2023-08-29 11:23:21 +0200
committerReza Arbab <arbab@linux.ibm.com>2023-09-12 14:22:11 -0500
commit1bce20c438357cb5c122bbb103f62dfc8678fc41 (patch)
tree51fce7eec73ab205036dd37fcf890a031edf6686 /hdata/memory.c
parent1a3ba1ec80071a031e793fc51954c88bbdfca645 (diff)
downloadskiboot-1bce20c438357cb5c122bbb103f62dfc8678fc41.zip
skiboot-1bce20c438357cb5c122bbb103f62dfc8678fc41.tar.gz
skiboot-1bce20c438357cb5c122bbb103f62dfc8678fc41.tar.bz2
core/pldm: Add PLDM responder support
PLDM defines data representations and commands that abstract the platform management hardware. A PLDM Terminus (or responder) is defined as the point of communication termination for PLDM messages and the PLDM functions associated with those messages. A PLDM terminus is not required to process more than one request at a time (that is, it can be "single threaded" and does not have to accept and act on new requests until it has finished responding to any previous request). Some PLDM control and discovery requests (PLDM_TYPE = PLDM_BASE) are mandatory a PLDM terminus has to answer. These following mandatory PLDM command codes for PLDM messaging control and discovery will be defined in next patches. GetTID 0x02 GetPLDMVersion 0x03 GetPLDMTypes 0x04 GetPLDMCommands 0x05 Reviewed-by: Abhishek Singh Tomar <abhishek@linux.ibm.com> Signed-off-by: Christophe Lombard <clombard@linux.ibm.com> Signed-off-by: Reza Arbab <arbab@linux.ibm.com>
Diffstat (limited to 'hdata/memory.c')
0 files changed, 0 insertions, 0 deletions