-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
subsys: Add MCTP as a subsystem, built on libmctp with bindings #75743
base: main
Are you sure you want to change the base?
Conversation
The following west manifest projects have changed revision in this Pull Request:
⛔ DNM label due to: 1 added project Note: This message is automatically posted and updated by the Manifest GitHub Action. |
e32c677
to
44752b4
Compare
bd7c893
to
153b02d
Compare
Need to work out some upstream stuff, but can then have the fork setup in the zephyrproject-rtos github org |
91652d2
to
f884e0d
Compare
In my original samples I had hacked up the serial binding to work with Zephyr natively, to better integrate with Zephyr however its useful to provide native bindings in a subsys so that's what I've begun to do. |
29717fb
to
e1f9cbd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've got a few minor suggestions, but nothing that should stop this from moving forward. Approving on that end.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We do .rst :) also please follow the code sample template https://github.com/zephyrproject-rtos/zephyr/blob/main/doc/templates/sample.tmpl so this properly shows in the documentation. You'll also need a page similar to https://github.com/zephyrproject-rtos/zephyr/blob/main/samples/modules/lvgl/lvgl.rst in the mctp folder to define a new sample category for MCTP samples
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The sample here is really the pair of firmwares being built and run on two boards. Do we have anything like that in the tree already that you know of?
Really this is one sample with two different firmwares. Really unsure of how best to structure it but documenting them separately actually doesn't make much sense.
Converting to rst is of course no problem, but do note we have markdown readme files in the tree for samples.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think its good now, let me know
8bac7a4
to
6ff9d90
Compare
b414f5c
to
437db75
Compare
seems to have picked up an extra commit for renaming |
Adds libmctp as a west module dependency Signed-off-by: Tom Burdick <thomas.burdick@intel.com>
libmctp provides interfaces for wiring up a MCTP bus it calls bus bindings. The bindings provided in libmctp however are not directly useful to Zephyr without some work. Provide an initial uart binding that directly uses Zephyr's async uart interface. Signed-off-by: Tom Burdick <thomas.burdick@intel.com>
437db75
to
20b84e5
Compare
Oops! yeah had committed that to my local main, and now all my rebases have it, argh, gotta go review other PRs as well. |
Samples work by sending MCTP encoded messages over a uart between two boards. Signed-off-by: Tom Burdick <thomas.burdick@intel.com>
Adds myself, nashif, and inteljiangwe1 to the maintainers file covering the libmctp module. Signed-off-by: Tom Burdick <thomas.burdick@intel.com>
20b84e5
to
7db91ef
Compare
Adds libmctp as a zephyr module from my fork with a few small changes I intend on trying to upstream along with a binding to Zephyr's
pollingasync UART API. Comes with a pair of sample applications that can be used on two boards connected via UART.