michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/dts/bindings/serial/nordic,nrf-uart.yaml

33 lines
479 B
YAML
Raw Permalink Normal View History

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 08:39:11 +01:00
description: Nordic UART
arm: dts: Add DTS support for NRF52832 SoC Add plumbing to build system and SoC level dtsi for the NRF52832 SoC. We additionally add the necessary yaml files for the UART on the NRF52 SoCs. Change-Id: I3b4a821b2993827e33d8e84bdbbc759d1521f8bd Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2017-04-11 10:05:42 -05: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-19 20:32:25 +02:00
compatible: "nordic,nrf-uart"
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-21 18:10:12 -05:00
include: uart-controller.yaml
arm: dts: Add DTS support for NRF52832 SoC Add plumbing to build system and SoC level dtsi for the NRF52832 SoC. We additionally add the necessary yaml files for the UART on the NRF52 SoCs. Change-Id: I3b4a821b2993827e33d8e84bdbbc759d1521f8bd Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2017-04-11 10:05:42 -05:00
properties:
yaml: fix properties syntax to 'mapping' instead of 'series' According to yaml syntaxic rules, 'properties' described in dts bindings yaml files could be seen as 'mapping'(key/value couple), instead of 'series' (list of single elements). yaml 'mappings' will then be converted by yaml python library as python 'dict' which will ease treatment (instead of current list as were before this commit). Same treatment is applied to 'inherits'. script extract_dts_inlcude is updated to take change of yaml_list structre into account. This allows some code simplification. Largest impact is yaml_collapse function which works now allow complete overload method on all the attributes of a yaml nodes. Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>
2017-11-23 08:48:10 +01:00
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 00:22:01 +02:00
required: true
arm: dts: Add DTS support for NRF52832 SoC Add plumbing to build system and SoC level dtsi for the NRF52832 SoC. We additionally add the necessary yaml files for the UART on the NRF52 SoCs. Change-Id: I3b4a821b2993827e33d8e84bdbbc759d1521f8bd Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2017-04-11 10:05:42 -05:00
yaml: fix properties syntax to 'mapping' instead of 'series' According to yaml syntaxic rules, 'properties' described in dts bindings yaml files could be seen as 'mapping'(key/value couple), instead of 'series' (list of single elements). yaml 'mappings' will then be converted by yaml python library as python 'dict' which will ease treatment (instead of current list as were before this commit). Same treatment is applied to 'inherits'. script extract_dts_inlcude is updated to take change of yaml_list structre into account. This allows some code simplification. Largest impact is yaml_collapse function which works now allow complete overload method on all the attributes of a yaml nodes. Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>
2017-11-23 08:48:10 +01: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 00:22:01 +02:00
required: true
boards: nrf: uart: Moved UART pin configuration to DTS (nRF boards) UART pins (TX, RX, RTS, CTS) are now configured in DTS files. RTS and CTS definitions are optional. If flow control is enabled and RTS/CTS pins are not defined, then compiler will issue an error message. Signed-off-by: Paweł Zadrożniak <pawel.zadrozniak@nordicsemi.no>
2018-08-28 16:24:22 +02:00
tx-pin:
type: int
description: TX pin
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 00:22:01 +02:00
required: true
boards: nrf: uart: Moved UART pin configuration to DTS (nRF boards) UART pins (TX, RX, RTS, CTS) are now configured in DTS files. RTS and CTS definitions are optional. If flow control is enabled and RTS/CTS pins are not defined, then compiler will issue an error message. Signed-off-by: Paweł Zadrożniak <pawel.zadrozniak@nordicsemi.no>
2018-08-28 16:24:22 +02:00
rx-pin:
type: int
description: RX pin
drivers: serial: nrfx_uart: Allow TX only mode Extended nrf_uart driver to support TX only. When RX pin is not provided then RX is not started at all. This allows to achieve low power with logging/console enabled. Signed-off-by: Krzysztof Chruscinski <krzysztof.chruscinski@nordicsemi.no>
2020-02-19 11:46:05 +01:00
required: false
boards: nrf: uart: Moved UART pin configuration to DTS (nRF boards) UART pins (TX, RX, RTS, CTS) are now configured in DTS files. RTS and CTS definitions are optional. If flow control is enabled and RTS/CTS pins are not defined, then compiler will issue an error message. Signed-off-by: Paweł Zadrożniak <pawel.zadrozniak@nordicsemi.no>
2018-08-28 16:24:22 +02:00
rts-pin:
type: int
description: RTS pin
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 00:22:01 +02:00
required: false
boards: nrf: uart: Moved UART pin configuration to DTS (nRF boards) UART pins (TX, RX, RTS, CTS) are now configured in DTS files. RTS and CTS definitions are optional. If flow control is enabled and RTS/CTS pins are not defined, then compiler will issue an error message. Signed-off-by: Paweł Zadrożniak <pawel.zadrozniak@nordicsemi.no>
2018-08-28 16:24:22 +02:00
cts-pin:
type: int
description: CTS pin
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 00:22:01 +02:00
required: false
Copy permalink