diff options
author | Christophe Lombard <clombard@linux.ibm.com> | 2023-08-29 11:23:19 +0200 |
---|---|---|
committer | Reza Arbab <arbab@linux.ibm.com> | 2023-09-12 14:22:11 -0500 |
commit | 4fc06a6cb136a0acaef03e603bb906a6e6c48788 (patch) | |
tree | 4a532dbcbfd67687706350fa669fb2bbc579eae0 /Makefile | |
parent | 66c38f45e9fc079dc47c8865ee6a27da5e7cdc0f (diff) | |
download | skiboot-4fc06a6cb136a0acaef03e603bb906a6e6c48788.zip skiboot-4fc06a6cb136a0acaef03e603bb906a6e6c48788.tar.gz skiboot-4fc06a6cb136a0acaef03e603bb906a6e6c48788.tar.bz2 |
hw/ast-bmc: Initialize ast lpc mctp binding
The Management Component Transport Protocol (MCTP) defines a communication
model intended to facilitate communication.
This patch initialize MCTP binding over LPC Bus interface.
Several steps must be performed:
- Initialize the MCTP core (mctp_init()).
- Initialize a hardware binding as AST LPC mode host (mctp_astlpc_init()).
- Register the hardware binding with the core (mctp_register_bus()), using
a predefined EID (Host default is 9).
To transmit a MCTP message, mctp_message_tx() is used.
To receive a MCTP message, a callback need to be provided and registered
through mctp_set_rx_all().
For the transfer of MCTP messages, two basics components are used:
- A window of the LPC FW address space, where reads and writes are
forwarded to BMC memory.
- An interrupt mechanism using the KCS interface.
hw/ast-bmc/ast-mctp.c is compilated if the compiler flag CONFIG_PLDM is
set.
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 'Makefile')
0 files changed, 0 insertions, 0 deletions