Skip to content

shields: doc: allow to indicate supported hw features #90589

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

Merged
merged 2 commits into from
May 28, 2025

Conversation

kartben
Copy link
Collaborator

@kartben kartben commented May 26, 2025

Shield authors can now indicate an optional list of hardware features that the shield supports, in the form of the same kind of "binding type" already used for boards.

List of supported features for boards is dynamically computed based on the board DTS as the list may significantly evolve overtime and get out-of-sync. Shields are much more "static", plus, computing things automagically would likely be tricky, so using a hardcoded list should hopefully be acceptable :)

@kartben kartben force-pushed the shields_hw_capabilities branch 2 times, most recently from ecc8054 to 92e39c6 Compare May 26, 2025 11:09
Shield authors can now indicate an optional list of hardware features
that the shield supports, in the form of the same kind of "binding type"
already used for boards.

Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
@kartben kartben force-pushed the shields_hw_capabilities branch from 92e39c6 to 7342d22 Compare May 26, 2025 12:10
@kartben kartben self-assigned this May 26, 2025
@kartben kartben force-pushed the shields_hw_capabilities branch 2 times, most recently from 1c7aabb to 377673d Compare May 26, 2025 12:41
Sets the list of supported hardware features for all the shields
currently defined in the tree.

Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
@kartben kartben merged commit 688c3a5 into zephyrproject-rtos:main May 28, 2025
32 checks passed
@kartben kartben deleted the shields_hw_capabilities branch May 28, 2025 15:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants