Support finding nodes by name without address.#11
Merged
Merged
Conversation
m4tx
requested changes
Dec 15, 2025
| } | ||
|
|
||
| /// Finds a node by its path. | ||
| /// |
Collaborator
There was a problem hiding this comment.
Please include some documentation that will explain that the address component is optional, and an example based on test_children.dtb that will show that looking for /child2@42 and /child2 yields the same result.
m4tx
reviewed
Dec 15, 2025
| } | ||
|
|
||
| /// Returns a child node by its name. | ||
| /// |
Many device tree nodes have names containing both a node-name and a unit-address component, like memory@40000000. It should be possible to find them by just the node-name.
m4tx
approved these changes
Dec 15, 2025
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.
Many device tree nodes have names containing both a node-name and a unit-address component, like memory@40000000. It should be possible to find them by just the node-name.