-
Notifications
You must be signed in to change notification settings - Fork 214
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
Remove usages of raw register manipulation outside of PAC crates #1194
Comments
Maybe we could even avoid those functions and use something like https://crates.io/crates/tock-registers But I think such code originates from 1:1 translation of esp-idf code - but once such code is known working, we could improve it |
Maybe I'm missing something, but why are we going to all this effort instead of just fixing the PACs? |
That would certainly be the best solution for registers! I somehow thought of I2C_BBPLL which we also deal with in those places |
Good idea! Let's do that instead, I've updated the title. |
I don't think I will be able to do this any time soon unfortunately, but if somebody else wants to tackle it I can at least explain what needs to be done to them, so just lemme know. If nobody has tackled this in a month or two when I wrap up my currently projects then I will take care of it at that point. |
Just to have some part of an investigation here: |
Work has been done on this issue (see in PRs above). At the moment, most operations with raw register addresses are performed in |
We can track the regi2c stuff in #1740, so I think we can close this now. |
We currently have duplicates of these reg functions where the svd's don't have enough info, and we have to resort back to raw register writes. E.g: https://github.com/search?q=repo%3Aesp-rs%2Fesp-hal%20reg_set&type=code.
We should cleanup and modularise their usage/definitions across our chip line-up.
cc: @playfulFence who initially noticed the issue.
The text was updated successfully, but these errors were encountered: