[spi] Document ESP32-S31 octal SPI support#6847
Open
swoboda1337 wants to merge 1 commit into
Open
Conversation
18 tasks
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the SPI Bus documentation to reflect that ESP32-S31 also supports octal SPI, keeping the docs aligned with the corresponding ESPHome core change.
Changes:
- Add ESP32-S31 to the documented list of ESP32 variants supporting octal SPI.
esphome
Bot
added
component: esp32
component: i2c
component: spi
has-parent
next
labels
✅ Deploy Preview for esphome ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds ESP32-S31 to the list of variants that support octal SPI.
Split out of a previously combined docs PR so each docs change maps 1-1 to its esphome code PR, making merges independent.
Related issue (if applicable): N/A
Pull request in esphome with YAML changes (if applicable):
Checklist
I am merging into
nextbecause this is new documentation that has a matching pull-request in esphome as linked above.or
I am merging into
currentbecause this is a fix, change and/or adjustment in the current documentation and is not for a new component or feature.Link added in
/src/content/docs/components/index.mdxwhen creating new documents for new components or cookbook.