| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/MCTP/ |
| H A D | Endpoint.interface.yaml | 2 Describe an MCTP endpoint. It is an MCTP communication terminus. An MCTP
3 endpoint is a terminus or origin of MCTP packets or messages. The combined
4 functionality within a physical device that communicates using the MCTP
5 transport protocol and handles MCTP control commands. This includes
6 MCTP-capable management controllers and managed devices.
20 The logical address used to route MCTP messages to a specific MCTP
22 a particular MCTP endpoint within a system for MCTP communication and
24 that comprise an MCTP communication network within a system. MCTP EIDs
32 List of MCTP message types supported by the MCTP endpoint. MCTP
35 types are MCTP Control(0x00), PLDM(0x01), NC-SI over MCTP(0x02),
[all …]
|
| H A D | README.md | 3 MCTP D-Bus interfaces are implemented by the MCTP control process daemon alias
4 mcptd and aids in the discovery of MCTP enabled devices by application layer
7 `xyz.openbmc_project.MCTP.Endpoint` D-Bus interface to discover MCTP endpoints.
8 The supported MCTP message types in an endpoint are exposed by the
13 those endpoints. MCTP bridges are not modelled in the D-Bus.
21 The D-Bus object path for MCTP endpoints are named
30 An MCTP Network may provide an optional MCTP Network ID that can be used to
31 differentiate different MCTP Networks when more than one MCTP Network can be
33 one point of access to the MCTP Network. The MCTP Network ID enables the entity
35 different MCTP Networks. If the implementation supports the optional MCTP
[all …]
|
| /openbmc/linux/drivers/net/mctp/ |
| H A D | Kconfig | 2 if MCTP
4 menu "MCTP Device Drivers"
7 tristate "MCTP serial transport"
11 This driver provides an MCTP-over-serial interface, through a
13 MCTP Serial Transport Binding". By attaching the ldisc to a serial
14 device, we get a new net device to transport MCTP packets.
16 This allows communication with external MCTP endpoints which use
25 tristate "MCTP SMBus/I2C transport"
37 tristate "MCTP I3C transport"
40 Provides a driver to access MCTP devices over I3C transport,
[all …]
|
| /openbmc/docs/designs/mctp/ |
| H A D | mctp-userspace.md | 1 # OpenBMC platform communication channel: MCTP & PLDM in userspace
5 Please refer to the [MCTP Overview](mctp.md) document for general MCTP design
8 This document describes a userspace implementation of MCTP infrastructure,
14 The MCTP core specification just provides the packetisation, routing and
16 hardware binding of the MCTP transport.
24 handling local MCTP-stack configuration, like local EID assignments.
28 1. the core MCTP stack
68 socket. Each of these would register with the MCTP daemon to receive MCTP
115 The rest of the message data is the complete MCTP message, including MCTP
119 for the tag field in individual MCTP packets.
[all …]
|
| H A D | mctp.md | 1 # OpenBMC platform communication channel: MCTP & PLDM
13 This design aims to use the Management Component Transport Protocol (MCTP) to
15 platforms provide. Then, on top of MCTP, we have the opportunity to move to
31 layer bindings for the actual transport of MCTP packets. These are defined by
48 that communicates over MCTP - for example, the host device, the BMC, or any
56 As part of the design, the references to MCTP "messages" and "packets" are
57 intentional, to match the definitions in the MCTP standard. MCTP messages are
82 The MCTP infrastrcuture in OpenBMC is implemented in two approaches:
85 daemon. This is described in [MCTP Userspace](mctp-userspace.md).
91 in [MCTP Kernel](mctp-kernel.md)
[all …]
|
| H A D | mctp-kernel.md | 1 # OpenBMC in-kernel MCTP
5 Please refer to the [MCTP Overview](mctp.md) document for general MCTP design
38 mapping of the sockets API to MCTP usage
132 /* MCTP network values */
135 /* MCTP EID values */
139 /* MCTP type values. Only the least-significant 7 bits of
146 /* MCTP-spec-defined fields */
235 the MCTP broadcast EID (0xff).
338 /* We can expect addr to describe an MCTP address */
371 The following socket options are defined for MCTP sockets:
[all …]
|
| /openbmc/linux/net/mctp/ |
| H A D | Kconfig | 2 menuconfig MCTP config
4 bool "MCTP core protocol support"
6 Management Component Transport Protocol (MCTP) is an in-system
11 This option enables core MCTP support. For communicating with other
16 bool "MCTP core tests" if !KUNIT_ALL_TESTS
17 depends on MCTP=y && KUNIT=y
22 depends on MCTP
|
| /openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/state/phosphor-state-manager/ |
| H A D | rescan-cxl-eid | 23 …if ! busctl call xyz.openbmc_project.MCTP /xyz/openbmc_project/mctp au.com.CodeConstruct.MCTP Setu…
29 …if ! busctl call xyz.openbmc_project.MCTP /xyz/openbmc_project/mctp au.com.CodeConstruct.MCTP Setu…
|
| H A D | wait-until-mctp-EID-remove | 20 …=$(busctl get-property xyz.openbmc_project.MCTP /xyz/openbmc_project/mctp/1/"$SD_EID" xyz.openbmc_…
21 …=$(busctl get-property xyz.openbmc_project.MCTP /xyz/openbmc_project/mctp/1/"$WF_EID" xyz.openbmc_…
|
| H A D | wait-until-mctp-connection-done | 7 …busctl get-property xyz.openbmc_project.MCTP /xyz/openbmc_project/mctp/1/"$EID" xyz.openbmc_projec…
|
| /openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/gpio/phosphor-gpio-monitor/ |
| H A D | rescan-wf-bic | 23 …busctl get-property xyz.openbmc_project.MCTP /xyz/openbmc_project/mctp/1/"$wf_eid" xyz.openbmc_pro…
52 …busctl call xyz.openbmc_project.MCTP /xyz/openbmc_project/mctp au.com.CodeConstruct.MCTP SetupEndp…
|
| H A D | configure-nic-mctp-endpoint | 52 …busctl call xyz.openbmc_project.MCTP /xyz/openbmc_project/mctp au.com.CodeConstruct.MCTP AssignEnd…
58 …busctl call xyz.openbmc_project.MCTP /xyz/openbmc_project/mctp/1/${eid} au.com.CodeConstruct.MCTP.…
|
| /openbmc/linux/Documentation/devicetree/bindings/net/ |
| H A D | mctp-i2c-controller.yaml | 7 title: MCTP I2C transport
13 An mctp-i2c-controller defines a local MCTP endpoint on an I2C controller.
14 MCTP I2C is specified by DMTF DSP0237.
20 to the host system as a separate MCTP I2C instance.
56 // Mux topology with multiple MCTP-handling busses under
58 // i2c1 and i2c6 can have MCTP devices, i2c5 does not.
|
| /openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/MCTP/ |
| H A D | meson.build | 4 'xyz/openbmc_project/MCTP/Endpoint__markdown'.underscorify(),
5 input: [ '../../../../yaml/xyz/openbmc_project/MCTP/Endpoint.interface.yaml', ],
13 'xyz/openbmc_project/MCTP/Endpoint',
|
| /openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/MCTP/Endpoint/ |
| H A D | meson.build | 3 'xyz/openbmc_project/MCTP/Endpoint__cpp'.underscorify(),
4 input: [ '../../../../../yaml/xyz/openbmc_project/MCTP/Endpoint.interface.yaml', ],
12 'xyz/openbmc_project/MCTP/Endpoint',
|
| /openbmc/openbmc/meta-evb/meta-evb-arm/meta-evb-fvp-base/recipes-phosphor/mctp/files/ |
| H A D | mctp-local.service | 2 Description=MCTP configuration for serial ttyAMA1
15 ExecStartPost=busctl call xyz.openbmc_project.MCTP /xyz/openbmc_project/mctp au.com.CodeConstruct.M…
|
| /openbmc/linux/Documentation/networking/ |
| H A D | mctp.rst | 4 Management Component Transport Protocol (MCTP)
7 net/mctp/ contains protocol support for MCTP, as defined by DMTF standard
11 The core code provides a socket-based interface to send and receive MCTP
17 The kernel models the local MCTP topology through two items: interfaces and
24 A network defines a unique address space for MCTP endpoints by endpoint-ID
42 Since MCTP is message-based, only ``SOCK_DGRAM`` sockets are supported.
123 ``sendto()``, ``sendmsg()``, ``send()`` : transmit an MCTP message
176 ``recvfrom()``, ``recvmsg()``, ``recv()`` : receive an MCTP message
179 An MCTP message can be received by an application using one of the
195 /* We can expect addr to describe an MCTP address */
[all …]
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/libmctp/ |
| H A D | libmctp_git.bb | 1 SUMMARY = "MCTP stack"
2 DESCRIPTION = "MCTP library implementing the MCTP base specification"
|
| /openbmc/libmctp/ |
| H A D | README.md | 1 # libmctp: Implementation of MCTP (DTMF DSP0236)
4 Component Transport Protocol (MCTP), as defined by DMTF standard "DSP0236", plus
16 to present the MCTP protocol to firmware and applications. Please bear with us!
26 To initialise the MCTP stack with a single hardware bus:
28 - `mctp = mctp_init()`: Initialise the MCTP core
36 MCTP message is received
40 - `mctp_message_tx(mctp, message, len)`: Transmit a MCTP message
54 - `mctp = mctp_init()`: Initialise the MCTP core
|
| /openbmc/libmctp/docs/bindings/ |
| H A D | vendor-ibm-astlpc.md | 5 This design provides an efficient method to transfer MCTP packets between the
13 1. DMTF DSP0236, Management Component Transport Protocol (MCTP) Base
28 Defined by the MCTP base specification as the smallest maximum packet size all
29 MCTP-compliant endpoints must accept.
94 ## MCTP over LPC Transport
118 3. Read the MCTP packet from the LPC FW window
191 of "MCTP":
208 immediately by the MCTP packet data to be transferred. The full MCTP packet,
458 ### The KCS MCTP Binding (DSP0254)
464 ### The MCTP Serial Binding (DSP0253)
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/PLDM/ |
| H A D | Requester.interface.yaml | 9 MCTP) can be found at https://www.dmtf.org/standards/pmci.
14 Obtain a new PLDM instance id, for the input MCTP EID, to be used in a
21 The instance id starts at 0 and can go upto 31 (5 bits), for each MCTP
43 The MCTP endpoint, specified by 'eid' (endpoint id), for which
|
| /openbmc/docs/designs/ |
| H A D | ncsi-coredump.md | 18 NC-SI over MCTP:
45 NC-SI over RBT or NC-SI over MCTP protocol. All NC-SI dump procedure will be
89 | DumpFile <-------+ NCSI-NetLink | | NCSI-MCTP +--------> DumpFile |
94 Kernel |Netlink |MCTP
|
| H A D | 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
213 message, over MCTP (the blocking send() will return a PLDM response). This
220 talk to the MCTP demux daemon.
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…
[all …]
|
| H A D | redfish-spdm-attestation.md | 113 be MCTP, PCIe-DOE, or even TCP socket. For MCTP, the lower physical layer can be
117 for SPDM daemon to implement If the transport layer is using standard MCTP or
119 design, we only consider SPDM over standard MCTP and PCIe-DOE connection.
121 For SPDM-over-MCTP, SPDM daemon can query the mctpd for information about MCTP
147 For MCTP devices detection, the community has been working on `mctpreactor`
152 `xyz.openbmc_project.MCTP.Endpoint` interface, which exposes the message types
171 | |MCTP |
182 1. Check transport layer protocol. For MCTP, it queries mctpd to gather all eids
185 2. For each endpoint, which could be MCTP or PCIe-DOE, SPDM daemon query Entity
274 over PCIe DOE or MCTP.
|
| /openbmc/openbmc/meta-evb/meta-evb-arm/meta-evb-fvp-base/ |
| H A D | README.md | 7 with the Manageability Control Processor (MCP) over PLDM over MCTP over UART.
18 | | MCTP over +-------+ +-------+
61 - PLDM + MCTP Specifications https://www.dmtf.org/standards/pmci
|