zephyr/scripts/dts/test-bindings/foo-required.yaml

properties:
    foo:
        type: int
        required: true
scripts: edtlib: Make order irrelevant when including multiple files When foo.yaml set some property 'required: true' and bar.yaml set the same property 'required: false', the check for changing 'required: false' to 'required: true' would raise an error for include: [bar.yaml, foo.yaml] (with that particular order due to implementation details). The order files are included in shouldn't matter. To fix it, change the logic so that 'required' values are ORed together between included files (so that 'required: true' is always respected), and remove the 'required' true-to-false check when merging included files. Keep the true-to-false check when merging the (merged) included files into the main binding (the binding with the 'include:' in it). This might give a good organization, and the old scripts do it too. Piggyback two fixes/cleanups: - 'compatible' should be allowed to appear in included files - No need to allow an 'inherits' key in _check_binding(), because it has been removed before then, when merging bindings Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no> 2019-09-11 01:17:29 +08:00			`properties:`
			`foo:`
			`type: int`
			`required: true`