zephyr/dts/bindings/pinctrl
Ulf Magnusson fcd665a26c dts: bindings: Have 'required: true/false' instead of 'category: ...'
The 'category: required/optional' setting for properties is just a
yes/no thing. Using a boolean makes it clearer, so have
'required: true/false' instead.

Print a clear error when 'category:' is used:

    edtlib.EDTError: please put 'required: true' instead of 'category:
    required' in 'properties: foo: ...' in
    test-bindings/sub-node-parent.yaml - 'category' has been removed

The old scripts in scripts/dts/ ignore this setting, and only print a
warning if 'category: required' in an inherited binding is changed to
'category: optional'. Remove that code, since the new scripts already
have the same check.

The replacement was done with

    git ls-files 'dts/bindings/*.yaml' | xargs sed -i \
        -e 's/category:\s*required/required: true/' \
        -e 's/category:\s*optional/required: false/'

dts/binding-template.yaml is updated as well.

Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-09-07 10:25:02 -05:00
..
atmel,sam0-pinmux.yaml dts: bindings: Have 'required: true/false' instead of 'category: ...' 2019-09-07 10:25:02 -05:00
intel,s1000-pinmux.yaml dts: bindings: Have 'required: true/false' instead of 'category: ...' 2019-09-07 10:25:02 -05:00
nxp,kinetis-pinmux.yaml dts: bindings: Have 'required: true/false' instead of 'category: ...' 2019-09-07 10:25:02 -05:00
openisa,rv32m1-pinmux.yaml dts: bindings: Have 'required: true/false' instead of 'category: ...' 2019-09-07 10:25:02 -05:00
st,stm32-pinmux.yaml dts: bindings: Have 'required: true/false' instead of 'category: ...' 2019-09-07 10:25:02 -05:00
ti,cc13xx-cc26xx-pinmux.yaml dts: bindings: Have 'required: true/false' instead of 'category: ...' 2019-09-07 10:25:02 -05:00
ti,cc2650-pinmux.yaml dts: bindings: Have 'required: true/false' instead of 'category: ...' 2019-09-07 10:25:02 -05:00