Repository navigation
test[i2c]: add framework utest with simulated bus - #11982
Conversation
|
👋 感谢您对 RT-Thread 的贡献!Thank you for your contribution to RT-Thread! 为确保代码符合 RT-Thread 的编码规范,请在你的仓库中执行以下步骤运行代码格式化工作流(如果格式化CI运行失败)。 🛠 操作步骤 | Steps
完成后,提交将自动更新至 如有问题欢迎联系我们,再次感谢您的贡献!💐 |
📌 Code Review Assignment🏷️ Tag: componentsReviewers: @Maihuanyi Changed Files (Click to expand)
🏷️ Tag: components_driver_i2cReviewers: @wdfk-prog Changed Files (Click to expand)
📊 Current Review Status (Last Updated: 2026-11-03 20:15 CST)
📝 Review Instructions
|
|
Rbb666
left a comment
There was a problem hiding this comment.
已复核本次改动及相关调用路径。覆盖消息转发、10 位地址、错误传播、锁释放和收发返回值。 当前提交的全部检查及 CLA 已通过,未发现阻塞合并的问题。
|
@usualtreee 这份测试用例也麻烦加入到qemu的ci看护中吧,可以参考 #11979 |
覆盖消息转发、10 位地址、错误传播、锁释放和收发返回值。
Summary
Refs #11972.
This covers only the I2C framework utest item. It uses a simulated bus and does not add a QEMU I2C peripheral model.
Verification
qemu-vexpress-a9:scons -j4passed.utest_run components.drivers.i2c.framework 2: both loops passed, with 6 units per loop and 12 unit runs in total.clang-format 22.1.8 --dry-run --Werror: passed fori2c_tc.c.scons -npassed.git diff --check: passed.No physical I2C hardware was used.