Skip to content

Conversation

rusty1968
Copy link
Collaborator

  • Document new slave operations: ConfigureSlaveAddress, EnableSlaveReceive, DisableSlaveReceive, CheckSlaveBuffer
  • Define architecture for MCTP driver as I2C server client
  • Add comprehensive API documentation with usage examples
  • Include error handling patterns and response codes
  • Document multi-address slave support and hardware considerations
  • Provide complete MCTP-over-I2C integration example
  • Add glossary of I2C, Hubris, and protocol terms

Enables peer-to-peer management protocols while maintaining clean separation between transport (I2C server) and protocol (MCTP driver) layers.

- Document new slave operations: ConfigureSlaveAddress, EnableSlaveReceive,
  DisableSlaveReceive, CheckSlaveBuffer
- Define architecture for MCTP driver as I2C server client
- Add comprehensive API documentation with usage examples
- Include error handling patterns and response codes
- Document multi-address slave support and hardware considerations
- Provide complete MCTP-over-I2C integration example
- Add glossary of I2C, Hubris, and protocol terms

Enables peer-to-peer management protocols while maintaining clean
separation between transport (I2C server) and protocol (MCTP driver) layers.

## Architecture Context

The I2C server provides transport services to multiple client tasks in the Hubris system:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add note that the following diagram is just an example for illustration purposes (to avoid confusion that these are all expected to be components in the final product)


**Usage Patterns**:

- **Sensor Manager**: Uses I2C **master** operations directly to read sensors, configure devices
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Eliminate all uses of Master/Slave terminology. Instead use HostController, HC, Controller, etc and TargetDevice or Device

@@ -0,0 +1,744 @@
# I2C IPC Protocol Extensions for MCTP Support
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the title here is good but please rename the file to make it more clear that this related to MCTP. Otherwise I could see this documentation easily being overlooked in the context of MCTP

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.

2 participants