-
Notifications
You must be signed in to change notification settings - Fork 8.2k
Fix few missing memory region names on stm32 boards #41049
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
Fix few missing memory region names on stm32 boards #41049
Conversation
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.
Thanks @fabiobaltieri. Only minor comments
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.
Looking at this (and not related to this PR):
@mbolivar-nordic: device_type prop is nowhere documented in bindings. Shouldn't it be removed ?
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.
Curious as well, shows up in edtlib.py but I don't think it's used anywhere and it's declared as deprecated in the specs https://github.com/devicetree-org/devicetree-specification/blob/main/source/chapter2-devicetree-basics.rst#device_type-deprecated.
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.
it's declared as deprecated in the specs https://github.com/devicetree-org/devicetree-specification/blob/main/source/chapter2-devicetree-basics.rst#device_type-deprecated.
@fabiobaltieri the link you pasted says (emphasis mine):
new use of the property is deprecated, and it should be included only on cpu and memory nodes for compatibility with IEEE 1275–derived devicetrees.
So from a specification point of view, it seems fine to keep this as is.
@galak asked about this on the spec mailing list, but the results were inconclusive: https://www.spinics.net/lists/devicetree-spec/msg00800.html
Take from that what you will.
Add the compatible property to the board level sdram nodes in few stm32 dts files so that the zephyr,memory-region name is used correctly in the linker script. Signed-off-by: Fabio Baltieri <[email protected]>
Include the mem-region bindings for the stm32 ccm nodes and set the name in the current dtsi files. Signed-off-by: Fabio Baltieri <[email protected]>
Fix the zephyr_linker_dts_memory to lookup the correct property name when trying to figre the region name. Signed-off-by: Fabio Baltieri <[email protected]>
6b03425 to
9347d78
Compare
Hey hi, found few missing region names after #37279 on SDRAM and CCM nodes for some stm32 boards. One had no compatible, the other missed the binding, tested with
west build -p -b stm32f429i_disc1 samples/basic/blinky.Before:
after:
Also fix the property name used in
zephyr_linker_dts_memory, right now it's always using the fallback.@JordanYates