-
Notifications
You must be signed in to change notification settings - Fork 2k
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
cpu/stm32/periph/i2c: export PERIPH_I2C_MAX_BYTES_PER_FRAME #19279
cpu/stm32/periph/i2c: export PERIPH_I2C_MAX_BYTES_PER_FRAME #19279
Conversation
Maybe someone remembers why this is not the case for |
It uses start(i2c, (addr << 1) | (length << I2C_CR2_NBYTES_Pos) | cr2_flags, flags); so this must be some sort of hardware limitation. |
I have seen this too but |
Maybe @aabadie knows why this limit exists? |
Why not putting it to the corresponding |
bors merge |
Nevermind its exactly those as in the Makefile and stm32h7 |
It would be more lines of change, and it seems to be equal for all according to the current code
At least it is what was there before. What would be better? |
To be honest I don't know^^ But I thought we are requesting multiple frames and not a single big one. But I really don't know I2C internals so I can't give a proposal on that |
Build succeeded: |
Contribution description
This exports the previously internally defined
MAX_BYTES_PER_FRAME
incpu/stm32/periph/i2c_1.c
.If such a limit exists, a driver must know about it.
Testing procedure
CI
Issues/PRs references
The problem came up in #19270.