ad48c51651
In Linux, checkpatch.pl relies on the vendor-prefixes.yaml file to validate manufacturers in compatible strings. In addition to the vendors defined in vendor-prefixes.txt, the YAML file includes expressions for "prefixes which are not vendors": these expressions do NOT define special manufacturers that may appear in compatible strings, and are never involved as such in DTS files. We can rather see them as bulk-definitions of JSON/YAML properties suitable for the dt-schema tools. OTHO, in Zephyr, checkpatch.pl relies on the vendor-prefixes.txt file, which does not include these additional prefixes, but edtlib.EDT adds them as hard-coded special values. This is confusing, if not incorrect: - the fact that edtlib.EDT (and thus its client code in the zephyr/scripts directory) actually allows these vendors in compatible strings is buried in the source code - checkpatch.pl (with vendor-prefixes.txt) in Zephyr behaves neither like checkpatch.pl (with vendor-prefixes.yaml) in Linux, nor like edtlib.EDT (with _VENDOR_PREFIX_ALLOWED) - Zephyr should not treat these "prefixes which are not vendors" as valid manufacturers in compatible strings to begin with 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.