-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
examples: add usb-i2c mctp app #525
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
twilfredo
force-pushed
the
wilfred/usb-i2c-bridge
branch
from
December 20, 2023 06:43
87153a0
to
902fa5c
Compare
alistair23
requested changes
Jan 8, 2024
twilfredo
force-pushed
the
wilfred/usb-i2c-bridge
branch
from
January 9, 2024 03:01
902fa5c
to
9410653
Compare
alistair23
reviewed
Jan 9, 2024
twilfredo
force-pushed
the
wilfred/usb-i2c-bridge
branch
2 times, most recently
from
January 9, 2024 03:58
974cd01
to
7d3d35a
Compare
alistair23
reviewed
Jan 9, 2024
alistair23
reviewed
Jan 9, 2024
twilfredo
force-pushed
the
wilfred/usb-i2c-bridge
branch
2 times, most recently
from
January 9, 2024 04:48
c64694c
to
1d12a73
Compare
Signed-off-by: Wilfred Mallawa <wilfred.mallawa@wdc.com>
twilfredo
force-pushed
the
wilfred/usb-i2c-bridge
branch
from
January 9, 2024 04:51
1d12a73
to
1a99fbb
Compare
alistair23
approved these changes
Jan 9, 2024
jrvanwhy
added
the
upkeep
Indicates a PR is upkeep as defined by the code review policy.
label
Jan 10, 2024
ping! this is ready to merge |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Add a sample libtock-rs app that allows a host machine without exposed I2C/SMBus capabilities to communicate to an MCTP endpoint.
The following topology is used:
This app operates by first waiting for an MCTP request packet to be sent over UART from the host, which is then forwarded to the target endpoint (based on the target address) through the I2C bus. The endpoint must then master the I2C bus and write a response back to us, as we wait in target mode (Note: MCTP mandates writes only). This is then forwarded to the host machine via UART.
A sample use-case can be to communicate with an SPDM responder that uses MCTP/SMBus/I2C, directly from the host machine.
Host app requirements
The host app must attach a small packet header (metadata) that wraps the data message, the packet formatting is detailed in the rust-docs for the app. It must also parse the same packet upon reception of data.