Skip to content

doc: shields: document convention for zephyr_[protocol] DT nodelabels #92355

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

JarmouniA
Copy link
Contributor

Add guidance on using extra devicetree nodelabels (zephyr_i2c, zephyr_spi, zephyr_mipi_dsi) in board DTS files for common communication protocols.
This convention enables shields to reference standard bus nodes in a portable and generic way.

This follows #89725 and #37474.

@JarmouniA JarmouniA added this to the v4.2.0 milestone Jun 28, 2025
@JarmouniA JarmouniA added area: Documentation area: Shields Shields (add-on boards) labels Jun 28, 2025
@JarmouniA JarmouniA force-pushed the doc_shield_comm_node_label branch 2 times, most recently from b93b136 to af0c589 Compare June 28, 2025 22:00
Add guidance on using extra devicetree nodelabels (zephyr_i2c,
zephyr_spi, zephyr_mipi_dsi) in board DTS files for common communication
protocols.
This convention enables shields to reference standard bus nodes in a
portable and generic way.

Signed-off-by: Abderrahmane JARMOUNI <git@jarmouni.me>
@JarmouniA JarmouniA force-pushed the doc_shield_comm_node_label branch from af0c589 to 05919f7 Compare June 28, 2025 23:12
Copy link

@JarmouniA JarmouniA marked this pull request as ready for review June 29, 2025 12:10
@kartben kartben requested a review from fabiobaltieri June 29, 2025 12:17
Comment on lines +174 to +176
- I2C (``zephyr_i2c``)
- MIPI DSI (``zephyr_mipi_dsi``)
- SPI (``zephyr_spi``)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

zephyr_i2c was actually meant to be the case above though: a well known connector (or connector family in this case), though I see how one could put it anywhere and then use a header to qwiic adapter or something, but that's not the case I had in mind. For SPI there's been no use case yet (I'm aware of one used in keyboards can't recall the name, but nothing landed upstream). Works well for dsi and udc.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I need to think about this a little bit more.

@JarmouniA JarmouniA marked this pull request as draft June 30, 2025 15:40
@JarmouniA JarmouniA removed this from the v4.2.0 milestone Jul 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants