add support for the phandle property; we could for example offer an API for setting the phandle of a node (once we clean up the abstractions to have a clear ownership between nodes & properties), and in the set function we can check for uniqueness. This would imply denying adding properties with the name phandle, or just check the name of the property, and in case it is phandle, check for uniqueness. It looks like this adds branching in the code, and we should discuss if we just want to go ahead with documenting this, or enforcing it.
andreeaflorescu
commented
3 years ago
The phandle property can be used to reference another node within the FDT uniquely: https://devicetree-specification.readthedocs.io/en/stable/devicetree-basics.html?#phandle
Right now we are not checking the uniqueness of the phandle, and I think there are a few things that we can do:
phandleproperty; we could for example offer an API for setting the phandle of a node (once we clean up the abstractions to have a clear ownership between nodes & properties), and in the set function we can check for uniqueness. This would imply denying adding properties with the namephandle, or just check the name of the property, and in case it isphandle, check for uniqueness. It looks like this adds branching in the code, and we should discuss if we just want to go ahead with documenting this, or enforcing it.