zephyr/dts/bindings/arm/nordic,nrf-uicr.yaml

description: Nordic UICR (User Information Configuration Registers)

compatible: "nordic,nrf-uicr"

include: base.yaml

properties:
    reg:
      required: true
dts: bindings: Remove 'title:' and put all info. into 'description:' Add any useful information from 'title:' to the 'description:' strings (e.g. explanations of acronyms), and remove 'title:' as well as any copy-pasted "this binding gives a ..." boilerplate. Also clean some description strings up a bit. Some other things could probably be cleaned up (replacing 'GPIO node' with 'GPIO controller' on controllers for consistency, for example), but I kept things close to the original to avoid accidentally messing up. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no> 2019-11-19 15:39:11 +08:00			`description: Nordic UICR (User Information Configuration Registers)`
soc: arm: nrf9160: add missing NRF_UICR definition NRF_UICR needs to be defined for nRF9160 SoC in nrfx_config_nrf9160.h, because it is not defined in nrfx/hal/mdk/nrf9160.h (as it is a Secure-only peripheral). Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no> 2019-08-06 20:08:53 +08:00
scripts: dts: Simplify and improve 'compatible' matching Instead of properties: compatible: constraint: "foo" , just have compatible: "foo" at the top level of the binding. For backwards compatibility, the old 'properties: compatible: ...' form is still accepted for now, and is treated the same as a single-element 'compatible:'. The old syntax was inspired by dt-schema (though it isn't dt-schema-compatible), which is in turn a thin wrapper around json-schema (the idea is to transform .dts files into YAML and then verify them). Maybe the idea was to gradually switch the syntax over to dt-schema and then be able to use unmodified dt-schema bindings, but dt-schema is really a different kind of tool (a completely standalone linter), and works very differently from our stuff (see schemas/dt-core.yaml in the dt-schema repo to get an idea of just how differently). Better to keep it simple. This commit also piggybacks some clarifications to the binding template re. '#cells:'. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no> 2019-08-20 02:32:25 +08:00			`compatible: "nordic,nrf-uicr"`

dts/bindings: Convert bindings to new include syntax Convert from: inherits: !include spi-device.yaml to: include: spi-device.yaml Signed-off-by: Kumar Gala <kumar.gala@linaro.org> 2019-08-22 07:10:12 +08:00			`include: base.yaml`
soc: arm: nrf9160: add missing NRF_UICR definition NRF_UICR needs to be defined for nRF9160 SoC in nrfx_config_nrf9160.h, because it is not defined in nrfx/hal/mdk/nrf9160.h (as it is a Secure-only peripheral). Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no> 2019-08-06 20:08:53 +08:00
			`properties:`
			`reg:`
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:\srequired/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-08-28 06:22:01 +08:00			`required: true`