History log of /openbmc/entity-manager/schemas/mctp.json (Results 1 – 2 of 2)
Revision Date Author Comments
# 2639e569 12-Feb-2025 Yikai Tsai <yikai.tsai.wiwynn@gmail.com>

schemas: mctp: Specify descriptions of MCTP I3C targets

8fd7afac1555 ("schemas: Specify descriptions of MCTP I2C targets")
introduced `MCTPI2CTarget` schema. According to this commit, add
`MCTPI3CTa

schemas: mctp: Specify descriptions of MCTP I3C targets

8fd7afac1555 ("schemas: Specify descriptions of MCTP I2C targets")
introduced `MCTPI2CTarget` schema. According to this commit, add
`MCTPI3CTarget` schema to support I3C targets.

Change-Id: I9fd2bcae9f39b9334107fb4b75c3ab5e837e0fec
Signed-off-by: Yikai Tsai <yikai.tsai.wiwynn@gmail.com>

show more ...


# e501cb71 19-Feb-2024 Andrew Jeffery <andrew@codeconstruct.com.au>

schemas: Specify descriptions of MCTP I2C targets

6fa0602db825 ("Add mctp eids configuration for Yosemite 4") introduced
an `EndpointId` property for assigning static MCTP endpoint IDs to an
exposed

schemas: Specify descriptions of MCTP I2C targets

6fa0602db825 ("Add mctp eids configuration for Yosemite 4") introduced
an `EndpointId` property for assigning static MCTP endpoint IDs to an
exposed device. This might work in very specific contexts, but
often more information is needed to configure a device for MCTP
communication.

Introduce the `MCTPI2CTarget` schema. Specifying `MCTPI2CTarget`
sets requirements such that a reactor can derive the physical address
encoding required to set up the endpoint.

For now we assume that all I2C controllers enabled for MCTP take the
role of bus owner.

Change-Id: I9d3f328262e99d405fc6e6dbdadff2306c254fa3
Signed-off-by: Andrew Jeffery <andrew@codeconstruct.com.au>

show more ...