-
Notifications
You must be signed in to change notification settings - Fork 73
Openamp cpu mask compat #828
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
zeddii
merged 5 commits into
devicetree-org:master
from
bentheredonethat:openamp-cpu-mask-compat
Sep 8, 2026
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
7b67278
domain: resolve legacy and relative CPU selections
bentheredonethat 0e3e7f8
yaml: resolve OpenAMP CPU metadata consistently
bentheredonethat c7eb882
openamp: use resolved CPUs for relation matching
bentheredonethat 0cbd4f6
openamp: fail when Libmetal output cannot be generated
bentheredonethat abb080e
tests: cover Libmetal generation with canonical and legacy metadata
bentheredonethat File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
propval()returns the['']sentinel when the property is absent, and['']is truthy. So when adomain-to-domainnode exists but carries nocluster_cpu, this hands the resolver a non-empty label list rather thanNone.Downstream that unwraps to
"", andcpu.labelis also""for an unlabelled CPU node, so the membership test inresolve_domain_cpusmatches on the first CPU child. Verified on a tree with an unlabelledcpu@1:So a domain with an out-of-range or zero mask and no
cluster_cpugets the cluster's first CPU returned as aLEGACY_CLUSTER_CPUresolution, complete with a migration warning suggesting it worked. That contradicts rule 5 in the resolver's docstring — "Otherwise report the selection as unresolved; never guess a CPU."You already have the correct guard in the sibling helper:
Same treatment here would fix it:
The new "zero and invalid masks remain unresolved" test won't catch this, because its fixture CPUs are labelled — the empty-string collision only happens when
cpu.labelis also''.