b3b5ad8156
Although the PropertySpec.path attribute is documented as "the file where the property was last modified", all property specs in Binding.prop2specs will claim they were last modified by the top-level binding itself. Consider: - I1 is a base binding that specifies properties x and y - I2 is an "intermediate" binding that includes I1, modifying the specification for property x - B is a top-level bindings that includes I2, and specifies an additional property p When enumerating the properties of B, we expect the values of PropertySpec.path to tell us: - y was last modified by I1 - x was last modified by I2 - p was last modified by B However, the Binding constructor: - first merges all included bindings into the top-level one - eventually initializes specifications for all the defined properties As a consequence, all defined properties claim they were last modified by the top-level binding file. We should instead: - first, take into account their own specifications for the included properties - eventually update these specifications with the properties the top-level binding adds or modifies Signed-off-by: Christophe Dufaza <chris@openmarl.org> |
||
|---|---|---|
| .. | ||
| python-devicetree | ||
| gen_defines.py | ||
| gen_driver_kconfig_dts.py | ||
| gen_dts_cmake.py | ||
| README.txt | ||
This directory used to contain the edtlib.py and dtlib.py libraries
and tests, alongside the gen_defines.py script that uses them for
converting DTS to the C macros used by Zephyr.
The libraries and tests have now been moved to the 'python-devicetree'
subdirectory.
We are now in the process of extracting edtlib and dtlib into a
standalone source code library that we intend to share with other
projects.
Links related to the work making this standalone:
https://pypi.org/project/devicetree/
https://python-devicetree.readthedocs.io/en/latest/
https://github.com/zephyrproject-rtos/python-devicetree
The 'python-devicetree' subdirectory you find here next to this
README.txt matches the standalone python-devicetree repository linked
above.
For now, the 'main' copy will continue to be hosted here in the zephyr
repository. We will mirror changes into the standalone repository as
needed; you can just ignore it for now.
Code in the zephyr repository which needs these libraries will import
devicetree.edtlib from now on, but the code will continue to be found
by manipulating sys.path for now.
Eventually, as APIs stabilize, the python-devicetree code in this
repository will disappear, and a standalone repository will be the
'main' one.