zephyr/scripts/dts/python-devicetree/tests/test-bindings-include
Christophe Dufaza 308b568219 Revert "edtlib: test filters set by including bindings"
This unit test was added specifically to cover a regression
reported by the CI while working on [1].

Further work on related issues [2] showed that:
- [1] and [2] are dead end: we need to first rethink
  how bindings (and especially child-bindings) are initialized
- the inclusion mechanism supported by Zephyr deserves more systematic
  testing in edtlib if we want to work with confidence

The approach we choose is to:
- revert all changes made in [1]
- from there, systematically add unit tests as we address
  the issues we identified (or the additional features we need)
  one after the other

[1] edtlib: fix last modified semantic in included property specs
[2] edtlib: Preserve paths of properties from included child bindings

See also: #65221, #78095

This reverts commit 33bb3b60d9.

Signed-off-by: Christophe Dufaza <chris@openmarl.org>
2024-11-06 14:43:19 -06:00
..
allow-and-blocklist-child.yaml
allow-and-blocklist-multilevel.yaml
allow-and-blocklist.yaml
allow-not-list.yaml
allowlist.yaml
base.yaml
block-not-list.yaml
blocklist.yaml
empty-allowlist.yaml
empty-blocklist.yaml
filter-child-bindings.yaml
include-2.yaml
include-invalid-keys.yaml
include-invalid-type.yaml
include-no-list.yaml
include-no-name.yaml
include.yaml
intermixed.yaml
modified.yaml edtlib: test "last modified" semantic for included property specs 2024-04-22 06:50:55 -07:00
README.rst
top.yaml

This directory contains bindings used to test the 'include:' feature.