-
Notifications
You must be signed in to change notification settings - Fork 8.2k
Dt docs for 2.3 part 3, and some test cases as well #25685
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
Dt docs for 2.3 part 3, and some test cases as well #25685
Conversation
At some point, "child-binding:" apparently only worked up to 2 levels deep. That's not the case anymore, but add a regression test to make sure that doesn't break. 3 levels deep ought to be enough for anyone. Signed-off-by: Martí Bolívar <[email protected]>
Remove some deprecated or obsolete functionality: - the 'title:' key is now deprecated - more than 2 levels of child-binding are now supported Signed-off-by: Martí Bolívar <[email protected]>
This is preparation for an additional test suite specifically for the legacy API which will be added next. Signed-off-by: Martí Bolívar <[email protected]>
|
@hakonfam you originally proposed the migration guide, so any feedback on this effort would be welcome. Thanks! |
|
All checks are passing now. Tip: The bot edits this comment instead of posting a new one, so you can check the comment's history to see earlier messages. |
79a0c0c to
50b753d
Compare
galak
left a comment
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.
Looks good, beyond addition of samples/hello_world/app.overlay
5efe57c to
4bc1db8
Compare
galak
left a comment
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.
Not sure if you can add a license/copyright header to migration-example.inc to make scancode happy.
I tried that with the C file but I couldn't get the presentation to come out right using |
Add test cases that verify various bits and pieces of the legacy devicetree macros match the new APIs. Writing these test cases without giving rise to deprecated macro warnings which might break people's CI if they build with -Werror requires turning off the __WARN() generation in devicetree_legacy_unfixed.h. The entire file is deprecated at this point and must be explicitly enabled with an opt-in Kconfig option, so there isn't any harm in doing this. Nevertheless, take a minimally invasive approach to avoiding __WARN() generation in gen_legacy_defines.py, to avoid the possibility of breakage. This code is basically frozen anyway, so hacks like this won't cause maintainability problems since it isn't being actively maintained. Use the new tests as fodder for a migration guide from the old API in the documentation. Signed-off-by: Martí Bolívar <[email protected]>
I believe the devicetree documentation for the release is in good enough shape now. Add a few more links to the release notes to provide users with more hints for adapting to the new API. Signed-off-by: Martí Bolívar <[email protected]>
4bc1db8 to
45bb529
Compare
Along with #25633 and #25470 (already merged), this PR:
Fixes: #25469
By:
I wanted to make sure the migration guide doesn't regress and the bindings restriction is indeed lifted in perpetuity, so I added test cases as well. I did have to touch gen_legacy_defines.py to make those tests cases not throw warnings about deprecated macros.
With this PR, I also give my sign-off to the DT release notes for #22637.