SPI Refactoring #7667
mrengineer7777
started this conversation in
Ideas
SPI Refactoring
#7667
Replies: 2 comments 5 replies
-
@mrengineer7777 the SPI should not be refactored to use ESP-IDF's driver! We can accept fixes, but that is mostly it. The driver is thread-safe if transactions are used (which is the proper way). If we switch to ESP-IDF's SPI driver, we will experience huge slowdown on some uses and people will be very unhappy. |
Beta Was this translation helpful? Give feedback.
3 replies
-
It appears IDF 5.0 makes significant changes to the SPI library. Perhaps we should wait on refactoring until IDF 5 is stable. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@SuGlider @me-no-dev @PilnyTomas @VojtechBartoska
TLDR: I would love to chat with the maintainer for SPI, and any history I should be aware of before jumping into SPI refactoring.
I'm considering using a W5500 module for Ethernet support. I see a user has added support on #7163, but one of the major blockers is conflicts with the SPI bus. In fact, I see lots of issues linked to SPI. I'm considering a PR to start the refactoring myself. How hard could it be? Famous last words....
As you can see below I've already put a lot of time into researching SPI issues.
Goals:
Things to watch out for:
Beta Was this translation helpful? Give feedback.
All reactions