fix(i2c): Fix I2c::probe
timeout not using configured timeout
#414
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.
Description
I2c::probe
to useconfig_.timeout_ms
to determine number of ticks for i2c transaction timeout instead of hardcoded 1000 ticks.Motivation and Context
Ensures the configured i2c timeout is used properly when probing the bus, instead of a hardcoded timeout
How has this been tested?
i2c/example
on ESP32S3 and ensure it probes the bus quickly as it should (~1 second total for all addresses)Screenshots (if appropriate, e.g. schematic, board, console logs, lab pictures):
Types of changes
Checklist:
Software
.github/workflows/build.yml
file to add my new test to the automated cloud build github action.