-
Notifications
You must be signed in to change notification settings - Fork 52
Use fugit #68
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
Use fugit #68
Conversation
| @@ -1,170 +1,114 @@ | |||
| use core::ops::{Add, Div}; | |||
| pub use fugit::{ | |||
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 contents of this file is now more or less identical with the one from stm32g0xx-hal
| impl CountDown for CountDownTimer<SYST> { | ||
| type Time = Hertz; | ||
| impl embedded_hal::timer::CountDown for CountDownTimer<SYST> { | ||
| type Time = MicroSecond; |
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 realize Hertz -> MicroSecond is quite a big change, it felt more natural in my mind. However I am fine with reverting that...
* Use fugit for time related types to make the crate more consistent with stm32g0xx-hal * fmt
|
Any thoughts on this? Is this something that is wanted or should I close this PR? Also please let me know if you want me to change anything :) |
|
Thanks a lot :) @no111u3 |
This first started with me trying to implement rtc for this crate by stealing it from stm32g0xx-hal. I noticed there were some differences.
This PR changes the time related types to use fugit to make the crate a bit more consistent with stm32g0xx-hal.
Is this at all something we want?
(Not at all tested on real hardware yet)- Some testing done