Skip to content

Conversation

@teburd
Copy link
Contributor

@teburd teburd commented Oct 24, 2025

Adds bindings for communicating with the MCTP protocol over I3C.

Note

In draft until I get this working on hardware, in particular the npcx4

@teburd teburd requested review from dkalowsk and nashif October 24, 2025 18:26
@teburd
Copy link
Contributor Author

teburd commented Oct 24, 2025

Realizing now that the i3c attach device is optional and i3c as a whole really wants to know about all the devices attached to it, so I need to create child nodes for each mctp endpoint on the i3c bus with a pseudo compatible I guess, then link those to the mctp controller in some manner with I guess phandles. Really I just wanted a list of id pairs but this isn't doable with devicetree and i3c today.

@nashif nashif requested a review from dcpleung October 24, 2025 21:31
Adds bindings for communicating with the MCTP protocol over I3C.

Signed-off-by: Tom Burdick <[email protected]>
Upon further reading its clear to support i3c and mctp I need to support
hot joining.

There's still work to verify the i3c device is an MCTP device by
checking its DCR and watching for the correct IBI response.
@teburd
Copy link
Contributor Author

teburd commented Oct 27, 2025

In discussion with @dcpleung I should be able to always use the provisional id, so I can always know then what devices should exist on the bus with devicetree statically even if they are dynamically hot joining later. Makes sense to me! This isn't USB though in some ways its kind of acting like it.

@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant