Separate the I2C chip_id map for AFC devices and RTM devices #180
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gustavosr8
force-pushed
the
i2c-mapping-separation
branch
from
a805021
to
5c1c0f1
Compare
gustavosr8
force-pushed
the
i2c-mapping-separation
branch
9 times, most recently
from
c8bbc04
to
9ac65cc
Compare
gustavosr8
force-pushed
the
i2c-mapping-separation
branch
7 times, most recently
from
ed9a820
to
3dc488e
Compare
Create different i2c_chip_mapping_t arrays and reserve chip_id numbers between 0 and 63 to AFC devices and between 64 and 127 to the RTM devices.
gustavosr8
force-pushed
the
i2c-mapping-separation
branch
from
3dc488e
to
c3005c2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Create different
i2c_chip_mapping_tarrays and reservechip_idnumbers between 0 and 63 to AFC devices and between 64 and 127 to the RTM devices.