OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/dts/bindings/watchdog/nordic,nrf-wdt.yaml

16 lines
269 B
YAML
Raw Normal View History

dts: nrf: Expand nRF DTS to support watchdog Commit introduces support for watchdog configuration for Nordic Semiconductor nRF SoCs in device tree. Signed-off-by: Karol Lasończyk <karol.lasonczyk@nordicsemi.no>
2018-04-17 21:29:12 +08:00
# Copyright (c) 2018, Nordic Semiconductor ASA
# SPDX-License-Identifier: Apache-2.0
yaml: Remove redundant document separators YAML document separators are needed e.g. when doing $ cat doc1.yaml doc2.yaml | <parser> For the bindings, we never parse concatenated documents. Assume we don't for any other .yaml files either. Having document separators in e.g. base.yaml makes !include a bit confusing, since the !included files are merged and not separate documents (the merging is done in Python code though, so it makes no difference for behavior). The replacement was done with $ git ls-files '*.yaml' | \ xargs sed -i -e '${/\s*\.\.\.\s*/d;}' -e 's/^\s*---\s*$//' First pattern removes ... at the end of files, second pattern clears a line with a lone --- on it. Some redundant blank lines at the end of files were cleared with $ git ls-files '*.yaml' | xargs sed -i '${/^\s*$/d}' This is more about making sure people can understand why every part of a binding is there than about removing some text. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-06-19 06:03:49 +08:00
dts: nrf: Rename "nordic,nrf-watchdog" compatible to "nordic,nrf-wdt" For consistency with the scheme used for other nRF peripherals, use the peripheral name that nRF Product Specifications use. In this case, it is WDT, not WATCHDOG. Also remove the requirement for the label property in the binding. It is no longer needed. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2022-03-30 17:05:39 +08:00
description: Nordic nRF family WDT (Watchdog Timer)
dts: nrf: Expand nRF DTS to support watchdog Commit introduces support for watchdog configuration for Nordic Semiconductor nRF SoCs in device tree. Signed-off-by: Karol Lasończyk <karol.lasonczyk@nordicsemi.no>
2018-04-17 21:29:12 +08:00
dts: nrf: Rename "nordic,nrf-watchdog" compatible to "nordic,nrf-wdt" For consistency with the scheme used for other nRF peripherals, use the peripheral name that nRF Product Specifications use. In this case, it is WDT, not WATCHDOG. Also remove the requirement for the label property in the binding. It is no longer needed. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2022-03-30 17:05:39 +08:00
compatible: "nordic,nrf-wdt"
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
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
dts/bindings: Move common properties into a base.yaml Move common properties like 'compatible', 'reg', 'reg-names', 'interrupts', 'interrupt-names', and 'label' into one common base.yaml that all the other yaml's can inherit from. This removes both duplication and inconsistent definition. The device specific yamls just need to say if a property is 'required' or not. NOTE: due to some generation conflicts we did not covert 'soc-nv-flash.yaml' to use base.yaml. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2019-06-08 00:12:49 +08:00
dts: nrf: Expand nRF DTS to support watchdog Commit introduces support for watchdog configuration for Nordic Semiconductor nRF SoCs in device tree. Signed-off-by: Karol Lasończyk <karol.lasonczyk@nordicsemi.no>
2018-04-17 21:29:12 +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:\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-08-28 06:22:01 +08:00
required: true
dts: nrf: Expand nRF DTS to support watchdog Commit introduces support for watchdog configuration for Nordic Semiconductor nRF SoCs in device tree. Signed-off-by: Karol Lasończyk <karol.lasonczyk@nordicsemi.no>
2018-04-17 21:29:12 +08:00
interrupts:
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-08-28 06:22:01 +08:00
required: true