Home
last modified time | relevance | path

Searched refs:MCTP (Results 1 – 25 of 60) sorted by relevance

123

/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/MCTP/
H A DREADME.md3 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
9 `SupportedMessageTypes` property in the `xyz.openbmc_project.MCTP.Endpoint`
11 complete the PLDM discovery flow with the MCTP endpoint. Also mctpd discovers
12 the removal of the MCTP endpoints and removes the D-Bus objects corresponding to
13 those endpoints. MCTP bridges are not modelled in the D-Bus.
19 lifetime of the D-Bus object is the lifetime of the connected MCTP device.
21 The D-Bus object path for MCTP endpoints are named
[all …]
/openbmc/linux/drivers/net/mctp/
H A DKconfig2 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
18 provide MCTP connectivity between virtual machines, by forwarding
21 Say y here if you need to connect to MCTP endpoints over serial. To
25 tristate "MCTP SMBus/I2C transport"
[all …]
/openbmc/docs/designs/mctp/
H A Dmctp-userspace.md1 # 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,
9 allowing a straightforward mechanism of supporting MCTP messaging within an
14 The MCTP core specification just provides the packetisation, routing and
16 hardware binding of the MCTP transport.
18 For OpenBMC, we would introduce a MCTP daemon, which implements the transport
21 complete MCTP messages. This daemon is responsible for the packetisation and
22 routing of MCTP messages from external endpoints, and handling the forwarding
24 handling local MCTP-stack configuration, like local EID assignments.
[all …]
H A Dmctp.md1 # 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
30 MCTP defines a standard transport protocol, plus a number of separate physical
31 layer bindings for the actual transport of MCTP packets. These are defined by
43 physical layer bindings; this means that an MCTP "stack" may be using either a
47 by an Entity ID (MCTP EID). These entities may be any element of the platform
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
[all …]
H A Dmctp-kernel.md1 # OpenBMC in-kernel MCTP
5 Please refer to the [MCTP Overview](mctp.md) document for general MCTP design
8 This document describes a kernel-based implementation of MCTP infrastructure,
9 providing a sockets-based API for MCTP communication within an OpenBMC-based
14 - The MCTP messaging API should be an obvious application of the existing POSIX
17 - Configuration should be simple for a straightforward MCTP endpoint: a single
20 - Infrastructure should be flexible enough to allow for more complex MCTP
23 - each MCTP network (as defined by section 3.2.31 of DSP0236) may consist of
37 - An interface for userspace applications to send and receive MCTP messages: A
38 mapping of the sockets API to MCTP usage
[all …]
/openbmc/linux/net/mctp/
H A DKconfig2 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/libmctp/
H A DREADME.md1 # libmctp: Implementation of MCTP (DTMF DSP0236)
4 Component Transport Protocol (MCTP), as defined by DMTF standard "DSP0236", plus
9 `libmctp` is a library that implements a straightforward MCTP stack. It will be
12 - where you are implementing MCTP in an embedded device; or
14 - with no kernel MCTP support,
15 - need a single application implementing all of the MCTP stack; and
16 - you are providing your own hardware drivers for MCTP transports.
18 Notably, if you are implementing an MCTP application on Linux, you _almost
19 certainly_ want to use the in-kernel MCTP support, which gives you a standard
20 sockets-based interface to transmit and receive MCTP messages. When using the
[all …]
/openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/MCTP/
H A Dmeson.build4 sdbusplus_current_path = 'xyz/openbmc_project/MCTP'
7 'xyz/openbmc_project/MCTP/Endpoint__markdown'.underscorify(),
8 input: ['../../../../yaml/xyz/openbmc_project/MCTP/Endpoint.interface.yaml'],
21 'xyz/openbmc_project/MCTP/Endpoint',
/openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/MCTP/Endpoint/
H A Dmeson.build3 sdbusplus_current_path = 'xyz/openbmc_project/MCTP/Endpoint'
6 'xyz/openbmc_project/MCTP/Endpoint__cpp'.underscorify(),
8 '../../../../../yaml/xyz/openbmc_project/MCTP/Endpoint.interface.yaml',
28 'xyz/openbmc_project/MCTP/Endpoint',
/openbmc/linux/Documentation/networking/
H A Dmctp.rst4 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
20 An interface (or "link") is an instance of an MCTP physical transport binding
24 A network defines a unique address space for MCTP endpoints by endpoint-ID
41 MCTP uses ``AF_MCTP`` / ``PF_MCTP`` for the address- and protocol- families.
42 Since MCTP is message-based, only ``SOCK_DGRAM`` sockets are supported.
76 The following sections describe the MCTP-specific behaviours of the standard
98 This establishes the local address of the socket. Incoming MCTP messages that
[all …]
/openbmc/openbmc/meta-ampere/meta-mitchell/recipes-ampere/host/ampere-mctp-i2c-binding/
H A Dampere_mctp_i2c_binding.sh78 /au/com/codeconstruct/mctp1/interfaces/mctpi2c3 au.com.codeconstruct.MCTP.BusOwner1 \
106 /au/com/codeconstruct/mctp1/interfaces/mctpi2c3 au.com.codeconstruct.MCTP.BusOwner1 \
121 au.com.codeconstruct.MCTP.Endpoint1 Remove
130 au.com.codeconstruct.MCTP.Endpoint1 Remove
/openbmc/openbmc/meta-phosphor/recipes-phosphor/libmctp/
H A Dlibmctp_git.bb1 SUMMARY = "MCTP stack"
2 DESCRIPTION = "MCTP library implementing the MCTP base specification"
/openbmc/libmctp/docs/bindings/
H A Dvendor-ibm-astlpc.md1 # Management Component Transport Protocol (MCTP) LPC Transport Binding Specification for ASPEED BMC…
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":
203 MCTP packet data is transferred exactly as is presented, and no data escaping is
208 immediately by the MCTP packet data to be transferred. The full MCTP packet,
[all …]
/openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/gpio/phosphor-gpio-monitor/
H A Dconfigure-nic-mctp-endpoint17 …u/com/codeconstruct/mctp1/interfaces/"mctpi2c${bus}" au.com.codeconstruct.MCTP.BusOwner1 AssignEnd…
32 … /au/com/codeconstruct/mctp1/networks/1/endpoints/${eid} au.com.codeconstruct.MCTP.Endpoint1 Remove
H A Drescan-wf-bic24 …P1 /au/com/codeconstruct/mctp1/networks/1/endpoints/"$wf_eid" xyz.openbmc_project.MCTP.Endpoint EID
53 …/com/codeconstruct/mctp1/interfaces/mctpi2c${busnum} au.com.codeconstruct.MCTP.BusOwner1 SetupEndp…
/openbmc/openbmc/meta-ampere/meta-common/recipes-phosphor/mctp/files/
H A Dmctp-local.service2 Description=MCTP configuration for i2c bus 3
10 …CTP1 /au/com/codeconstruct/mctp1/interfaces/mctpi2c3 au.com.codeconstruct.MCTP.Interface1 Role s B…
/openbmc/openbmc/meta-evb/meta-evb-arm/meta-evb-fvp-base/recipes-phosphor/mctp/files/
H A Dmctp-local.service2 Description=MCTP configuration for serial ttyAMA1
15 …1 /au/com/codeconstruct/mctp1/interfaces/mctpserial0 au.com.codeconstruct.MCTP.BusOwner1 SetupEndp…
/openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/state/phosphor-state-manager/
H A Dwait-until-mctp-EID-remove20 …/com/codeconstruct/mctp1/networks/1/endpoints/"$SD_EID" xyz.openbmc_project.MCTP.Endpoint EID 2>&1)
21 …/com/codeconstruct/mctp1/networks/1/endpoints/"$WF_EID" xyz.openbmc_project.MCTP.Endpoint EID 2>&1)
H A Drescan-cxl-eid6 …u/com/codeconstruct/mctp1/networks/1/endpoints/"$eid" xyz.openbmc_project.MCTP.Endpoint EID >/dev/…
14 …/com/codeconstruct/mctp1/interfaces/mctpi2c${busnum} au.com.codeconstruct.MCTP.BusOwner1 SetupEndp…
/openbmc/docs/designs/
H A Dncsi-coredump.md18 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 Dpldm-stack.md19 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 | |
[all …]
H A Dredfish-spdm-attestation.md113 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 DREADME.md7 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
/openbmc/openbmc/meta-phosphor/recipes-kernel/linux/mctp/
H A Dmctp.scc1 define KFEATURE_DESCRIPTION "Enable MCTP"
/openbmc/libmctp/systemd/system/
H A Dmctp-demux.socket2 Description=MCTP demux Unix domain socket

123