docs/designs/pldm-stack.md

19 designed to run on standard transport protocols, for e.g. MCTP (also designed by
20 the DMTF). MCTP provides for a common transport layer over several physical
21 channels, by defining hardware bindings. The solution of PLDM over MCTP also
66 The plan is to run PLDM over MCTP. MCTP is defined in a spec of its own, and a
67 proposal on the MCTP design is in discussion already. There's going to be an
68 intermediate PLDM over MCTP binding layer, which lets us send PLDM messages over
69 MCTP. This is defined in a spec of its own, and the design for this binding will
213   message, over MCTP (the blocking send() will return a PLDM response). This
220   talk to the MCTP demux daemon.
236 … |init(non_block=false)          |MCTP daemon                   |                                 |
255 … |                               |write msg to MCTP socket      |                                 |
290 …    |init(non_block=true            |MCTP daemon                   |                              |
310 …    |         non_block=true)       |write msg to MCTP socket      |                              |
355 channels. While a level of abstraction might be provided by MCTP, the PLDM
396 ### MCTP endpoint discovery
399 [MCTP D-Bus interfaces](https://github.com/openbmc/phosphor-dbus-interfaces/tree/master/yaml/xyz/op…
400 to enumerate all MCTP endpoints in the system. The MCTP D-Bus interface
409 When `pldmd` received the updated EID table from MCTP D-Bus interface, `pldmd`
412 MCTP D-Bus interface, `pldmd` should also clean up the removed endpoint from the
435 DSP0248 1.2.1) or in the MCTP Entity-manager endpoint EID configuration file