Repository navigation
i2c: Add support for two-slave transactions - #96
Merged
Merged
Conversation
PP5020 supports two-slave transactions: two transactions sent back-to-back. The intended use-case is when you want to perform a register readout: you first need to issue an I2C transaction at the device write address then a second transaction at a read address. RetailOS on iPod photo uses this feature (first slave address is 0x54, second slave address is 0x55).
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
PP5020 supports two-slave transactions: two transactions sent back-to-back. The intended use-case is when you want to perform a register readout: you first need to issue an I2C transaction at the device write address then a second transaction at a read address.
RetailOS on iPod photo uses this feature (first slave address is 0x54, second slave address is 0x55).
There are very few details on two-slave transactions in Nvidia TRM, but you can find bits of it in DVC_I2C_CNFG_0.