cpu/stm32f1: add unified rtt configuration#13907
Conversation
99b4f22 to
f1deca1
Compare
|
Re-worked to leave only |
benpicco
left a comment
There was a problem hiding this comment.
Looks good to me, the math works out the same as before.
|
Seems there is a naming conflict.. |
Oh no, its because those |
Seem like they both have a LSE oscilator. But I'll guard the definition against |
And add rtt in a follow-up. |
f1deca1 to
45f2c86
Compare
Actually, does it make sense enabling right away? the bluepill config already has |
I wouldn't have any board to test though. |
|
@MrKevinWeiss do you have some blxxxpill? |
I actually had a PR in the pipe line enabling |
45f2c86 to
07ff619
Compare
I added |
07ff619 to
9d74173
Compare
9d74173 to
c0d1884
Compare
Seem that with the github issues, my comment got lost. I wanted to provide |
|
Seems github issues got in the way here. |
c0d1884 to
e07a862
Compare
|
Ajjj is starting to be more annoying than I though, because |
e07a862 to
c081ab7
Compare
c081ab7 to
4d398ab
Compare
|
@benpicco does your ACK still stand? |
aabadie
left a comment
There was a problem hiding this comment.
Looks good to me now.
ACK
|
Thanks for the review! |
Contribution description
This PR is split from #13874. It unifies
rttconfiguration forstm32f1and make theRTT_FREQYENCYconfigurable.As in #13874 max and min values for the RTT are documented.
Testing procedure
tests/periph_rttshould still pass onstm32f1boards with different frequenciesBOARD=iotlab-m3 make -C tests/periph_rtt flash test --no-print-directory -j3CFLAGS+=-DRTT_FREQUENCY=1 BOARD=iotlab-m3 make -C tests/periph_rtt clean flash test --no-print-directory -j3Issues/PRs references
Split from #13874