-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposed new I2C verb "i2c_repeated_transmit" #405
Conversation
This reverts commit ec27189.
# Conflicts: # host/greatfet/commands/greatfet_i2c.py # host/greatfet/sensors/lsm6ds33.py
@antoinevg is there any appetite to add this new verb? If not, happy to close PR and maintain out-of-tree. Just FYI, I was also looking at implementing same functionality for SPI. |
This looks great @krogozinski, thank you for contributing! I also think having the same functionality for SPI would be just as useful. I'm definitely up for putting some time aside to help you get this landed! |
OK thanks, I should have some time this week to work on the SPI side. I'll make sure to clean up my git commit history before pushing the changes to my fork. |
I2C verb "i2c_repeated_transmit" conducts a write/read sequence a specified number of times.
Use case: many inertial sensors e.g .ST LSM6DS33, employ a FIFO that can be read at a pre-determined time interval or when a certain number of samples have been taken. In order to read and flush this buffer expediently, a fast sequence of I2C operations is required:
A repeated transmit I2C verb could rapidly perform this sequence in comparison to a conventional I2CDevice.transmit(), which introduces USB latency between each write/read operation.
Example: