-
Notifications
You must be signed in to change notification settings - Fork 3k
RFC HAL I2C: Reference implementations for K64F and STM32F0 #8682
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
Conversation
@scartmell-arm Something about this PR's comit history and files changed does not look right. Could you double check? |
@mbed-os-maintainers @ARMmbed/mbed-os-hal Readt for review when able. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have additional question to all HAL and DRIVERS API functions.
Whenever we passes device address it should be shifted left by 1 bit and filled by 1 or 0 (or LSB bit is ignored) depending of situation, it's valid for both 7bit and 10bit addressing?
{ | ||
int addr = (address & 0xFF) | 1; | ||
i2c_slave_address(&_i2c, 0, addr, 0); | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The line:
int addr = (address & 0xFF) | 1;
breaks 10bit addressing
@scartmell-arm You have questions/comments waiting for your attention. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Few comments or questions ...
@scartmell-arm Is it time to update this one and make sure reviewers find time to review? |
There were a few outstanding concerns I was working through, I'll push a resolution to all of them soon. |
@scartmell-arm Who should review , anyone from @ARMmbed/mbed-os-hal or @maciejbocianski is sufficient (still some comments not addressed). How can we progress i2c feature branch? |
@scartmell-arm @ARMmbed/mbed-os-hal How can we progress this PR? |
@ARMmbed/mbed-os-hal What do we need to move this forward? Or is this still being worked on? |
@maciejbocianski could you have another look at this please? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing implementation of async in the driver - @scartmell-arm @maciejbocianski would you be able to pick this up so that we get this merged soon?
#if DEVICE_I2C_ASYNCH | ||
|
||
int I2C::transfer(int address, const char *tx_buffer, int tx_length, char *rx_buffer, int rx_length, const event_callback_t &callback, int event, bool repeated) | ||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that shouldn't be empty!
} | ||
} | ||
|
||
int i2c_byte_read(i2c_t *obj, int last) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@scartmell-arm
i2c_byte_read
and i2c_byte_write
should be removed since it was removed from API
After last fixes tests were successful for both reference implementations Following limitations were made:
CI i2c test (#9564)
I2C communication test (#9573)
|
As most of issues was fixed can we move forward with this PR? |
seems something wrong with Travis? @0xc0170 |
Travis should be good now. |
@maciejbocianski @LMESTM @donatieng Any more comments for this PR? |
@scartmell-arm I take it this won't be making it in?
|
@donatieng @ARMmbed/mbed-os-hal Is this good to go? |
cc @ithinuel |
Description
This PR contains reference implementations of the I2C HAL RFC changes for the FRDM-K64F and NUCLEO_F070RB boards.
Tasks
Pull request type