-
Notifications
You must be signed in to change notification settings - Fork 172
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
Pull out shared bus #52
Conversation
Could you please provide a short summary of what this pull request exactly is doing? To me, it seems like you just renamed |
Sorry I took so long to get back to you. I've updated the first comment with a short summary. I didn't rename |
After reading the esp-idf doc on the SPI driver, I change my mind. |
Obsoleted by #61 |
* More ergonomic async traits * Use AtomicWaker * Get rid of the callback Result return * More work on async compat * Async work * Switch all traits to a single error type * Make Eth & Wifi API implementations fully async * Rename Service to Errors * New version * Fix non-experimental build * Fix non-experimental build * Merge fix from @anichno * Again clippy warnings * Again clippy warnings
…Waveshare board and 4.2" e-paper screen (esp-rs#52) Signed-off-by: simon <Simon Tropée> Co-authored-by: simon <Simon Tropée>
@Dominaezzz I've been trying to read files from an sd card using |
This allows users to create multiple devices on one bus.
The current SPI interface allows one to create a single
Master
struct which represents the spi bus and the device.This prevents one from communicating with multiple SPI devices on the same bus. In my case, I have an E-Ink display and an SD card on the same bus and I'm only able to use one at a time.
This PR pulls out the spi bus from the
Master
struct into aBus
struct, which allows one to create multipleMaster
s on the same bus.The one thing I wasn't too sure about is whether
Bus
should be a struct or trait. I've got with struct for the moment. I don't really see the need for a trait atm.