-
Notifications
You must be signed in to change notification settings - Fork 226
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
Refactor SPI MISO setup #2557
Refactor SPI MISO setup #2557
Conversation
I'll come back to this once I figure out how to craft up a good migration guide. But I'll close this for now as there's already enough (almost 30) lingering PRs that aren't being updated. |
Would you mind reopening this? We've got through most of the backlog now, sorry about that 😅 |
Sure! I still need to figure the migration guide so it might still linger for a while. |
Small poke @Dominaezzz, would you mind rebasing and adding changelogs etc? |
# Conflicts: # esp-hal/src/spi/master.rs # hil-test/tests/spi_full_duplex.rs
Not sure what's going on with the HIL test, seeing as it times out rather than fails the assertion... I don't have time to investigate this weekend. |
@Dominaezzz that issue is independent from this PR, we have some timing difficulties in ESP32. |
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.
Besides the changelog, LGTM.
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.
Thanks!
Thank you for your contribution!
We appreciate the time and effort you've put into this pull request.
To help us review it efficiently, please ensure you've gone through the following checklist:
Submission Checklist 📝
cargo xtask fmt-packages
command to ensure that all changed code is formatted correctly.CHANGELOG.md
in the proper section.Extra:
Pull Request Details 📖
Description
Fixes #2511 .
Not everyone wants to configure the "output part" of the MISO signal.
My thinking here is, most users see "MISO" as an input pin/signal. If they want the bidirectional variant, they should use
with_sio1
to signify they want "Serial Input/Output" rather than "MISO".This also allows setting up loopback without
unsafe
.For aesthetics, it might be worth having a
with_sio0
(alongsidewith_miso
), just so it reads better when also usingsio2
,sio3
, etc.Testing
CI