Conversation
xuchang-vivo
force-pushed
the
xc/i2c_core
branch
from
73e6c68 to
222a0d2
Compare
|
build_prs vivoblueos/external#12 #178 vivoblueos/build#44 |
|
Job is started, see https://github.com/vivoblueos/kernel/actions/runs/19958036843. |
|
❌ Job failed. Failed jobs: check_format (failure), build_and_check_boards (failure), see https://github.com/vivoblueos/kernel/actions/runs/19958036843. |
|
build_prs vivoblueos/external#12 #178 vivoblueos/build#44 |
|
Job is started, see https://github.com/vivoblueos/kernel/actions/runs/19958506531. |
|
✅ All jobs completed successfully, see https://github.com/vivoblueos/kernel/actions/runs/19958506531. |
|
build_prs vivoblueos/external#12 #178 vivoblueos/build#44 |
|
Job is started, see https://github.com/vivoblueos/kernel/actions/runs/19958987260. |
|
✅ All jobs completed successfully, see https://github.com/vivoblueos/kernel/actions/runs/19958987260. |
|
build_prs vivoblueos/external#12 #178 vivoblueos/build#44 |
|
Job is started, see https://github.com/vivoblueos/kernel/actions/runs/19959313447. |
|
✅ All jobs completed successfully, see https://github.com/vivoblueos/kernel/actions/runs/19959313447. |
lawkai-vivo
left a comment
lawkai-vivo
left a comment
There was a problem hiding this comment.
Please include runnable tests on at least one qemu platform.
Writing an I2C test on QEMU isn't that straightforward, because I2C is a master–slave protocol: besides the host controller you also need a slave device to establish communication. To test an I2C driver on QEMU you therefore need to emulate an I2C slave device in QEMU. |
|
build_prs vivoblueos/external#12 #178 vivoblueos/build#44 |
|
Job is started, see https://github.com/vivoblueos/kernel/actions/runs/20356945916. |
|
❌ Job failed. Failed jobs: setup (failure). Skipped jobs: check_format (skipped), check_license (skipped), build_host (skipped), build_and_check_boards (skipped), see https://github.com/vivoblueos/kernel/actions/runs/20356945916. |
|
build_prs vivoblueos/external#12 #178 vivoblueos/build#44 |
|
Job is started, see https://github.com/vivoblueos/kernel/actions/runs/20357174959. |
|
❌ Job failed. Failed jobs: setup (failure). Skipped jobs: check_format (skipped), check_license (skipped), build_host (skipped), build_and_check_boards (skipped), see https://github.com/vivoblueos/kernel/actions/runs/20357174959. |
|
build_prs vivoblueos/external#12 #178 vivoblueos/build#44 |
|
Job is started, see https://github.com/vivoblueos/kernel/actions/runs/20357219455. |
xuchang-vivo
force-pushed
the
xc/i2c_core
branch
from
81ea9c5 to
2f43003
Compare
|
✅ All jobs completed successfully, see https://github.com/vivoblueos/kernel/actions/runs/20357219455. |
Another way to test the I2C & sensor drivers is to use Renode together with the Robot test framework. See: https://renode.readthedocs.io/en/latest/basic/sensors.html |
Co-authored-by: Kai Law <lawkai@vivo.com>
Co-authored-by: Kai Law <lawkai@vivo.com>
Co-authored-by: Kai Law <lawkai@vivo.com>
Co-authored-by: Kai Law <lawkai@vivo.com>
xuchang-vivo
force-pushed
the
xc/i2c_core
branch
from
69a8245 to
62d5b0b
Compare
|
build_prs vivoblueos/external#12 #178 vivoblueos/build#44 |
|
Job is started, see https://github.com/vivoblueos/kernel/actions/runs/20591419535. |
|
build_prs vivoblueos/external#12 #178 vivoblueos/build#44 |
|
Job is started, see https://github.com/vivoblueos/kernel/actions/runs/20591458461. |
|
✅ All jobs completed successfully, see https://github.com/vivoblueos/kernel/actions/runs/20591419535. |
|
✅ All jobs completed successfully, see https://github.com/vivoblueos/kernel/actions/runs/20591458461. |
|
build_prs vivoblueos/external#12 #178 vivoblueos/build#44 |
|
Job is started, see https://github.com/vivoblueos/kernel/actions/runs/20592791813. |
|
✅ All jobs completed successfully, see https://github.com/vivoblueos/kernel/actions/runs/20592791813. |
3 participants
No description provided.