-
Notifications
You must be signed in to change notification settings - Fork 2.1k
tests/periph_spi: add support for printing SPI clock rates on stm32 #14768
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
I think #14749 will provide a better solution to this, exposing registers to the API is a bad idea. |
#14749 will let you do If there is a shortcoming in the SPI API / driver we should fix that instead of hacking around it, otherwise we end up with an unmaintainable mess. |
ab3f51e
to
0785249
Compare
#14749 has been merged, can we close this? |
Hello @benpicco Is it currently possible to know the SPI clock speeds actually supported by a specific device with tests/periph_spi? I think it might be helpful. Can't you merge it ? Otherwise I can improve it. |
I'm afraid not
Yea that would be neat.
Merge what? :D You can add a stm32-specific test though if you so desire. |
To print the actual SPI clock you can enable debug output in the spi driver: Line 36 in ba67f6a
The each time the SPI is acquired the clock will be printed in stdout: Lines 215 to 219 in ba67f6a
|
0785249
to
b54627f
Compare
b54627f
to
a916cd7
Compare
Does this mean that I am not allowed to use
|
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions. |
Contribution description
cmd_init function help show possible speeds for each peripherals and directly store the clk argument in spiconf
Testing procedure
Issues/PRs references
See also #14731.
Depends on PR #14749.