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/spi/nordic,nrf-spis.yaml

50 lines
898 B
YAML
Raw Normal View History

dts: bindings: Add separate binding for Nordic nRF Family SPI Slave Use separate bindings for nRF Family SPI Slaves and SPI Masters so that the properties "csn" and "def-char" can be made required for Slaves (for Masters such settings are not applicable), and to avoid confusion between the properties "csn" and "cs-gpios" for Master nodes. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2019-01-31 19:40:54 +08:00
#
# Copyright (c) 2019 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: bindings: Add separate binding for Nordic nRF Family SPI Slave Use separate bindings for nRF Family SPI Slaves and SPI Masters so that the properties "csn" and "def-char" can be made required for Slaves (for Masters such settings are not applicable), and to avoid confusion between the properties "csn" and "cs-gpios" for Master nodes. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2019-01-31 19:40:54 +08:00
title: Nordic nRF Family SPIS (SPI Slave)
description: >
This is a representation of the Nordic nRF SPIS node
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: spi-controller.yaml
dts: bindings: Add separate binding for Nordic nRF Family SPI Slave Use separate bindings for nRF Family SPI Slaves and SPI Masters so that the properties "csn" and "def-char" can be made required for Slaves (for Masters such settings are not applicable), and to avoid confusion between the properties "csn" and "cs-gpios" for Master nodes. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2019-01-31 19:40:54 +08:00
properties:
compatible:
constraint: "nordic,nrf-spis"
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: bindings: Add separate binding for Nordic nRF Family SPI Slave Use separate bindings for nRF Family SPI Slaves and SPI Masters so that the properties "csn" and "def-char" can be made required for Slaves (for Masters such settings are not applicable), and to avoid confusion between the properties "csn" and "cs-gpios" for Master nodes. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2019-01-31 19:40:54 +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
dts: bindings: Add separate binding for Nordic nRF Family SPI Slave Use separate bindings for nRF Family SPI Slaves and SPI Masters so that the properties "csn" and "def-char" can be made required for Slaves (for Masters such settings are not applicable), and to avoid confusion between the properties "csn" and "cs-gpios" for Master nodes. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2019-01-31 19:40:54 +08:00
sck-pin:
type: int
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: bindings: Add separate binding for Nordic nRF Family SPI Slave Use separate bindings for nRF Family SPI Slaves and SPI Masters so that the properties "csn" and "def-char" can be made required for Slaves (for Masters such settings are not applicable), and to avoid confusion between the properties "csn" and "cs-gpios" for Master nodes. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2019-01-31 19:40:54 +08:00
description: SCK pin
mosi-pin:
type: int
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: bindings: Add separate binding for Nordic nRF Family SPI Slave Use separate bindings for nRF Family SPI Slaves and SPI Masters so that the properties "csn" and "def-char" can be made required for Slaves (for Masters such settings are not applicable), and to avoid confusion between the properties "csn" and "cs-gpios" for Master nodes. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2019-01-31 19:40:54 +08:00
description: MOSI pin
miso-pin:
type: int
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: bindings: Add separate binding for Nordic nRF Family SPI Slave Use separate bindings for nRF Family SPI Slaves and SPI Masters so that the properties "csn" and "def-char" can be made required for Slaves (for Masters such settings are not applicable), and to avoid confusion between the properties "csn" and "cs-gpios" for Master nodes. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2019-01-31 19:40:54 +08:00
description: MISO pin
csn-pin:
type: int
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: bindings: Add separate binding for Nordic nRF Family SPI Slave Use separate bindings for nRF Family SPI Slaves and SPI Masters so that the properties "csn" and "def-char" can be made required for Slaves (for Masters such settings are not applicable), and to avoid confusion between the properties "csn" and "cs-gpios" for Master nodes. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2019-01-31 19:40:54 +08:00
description: CSN pin
def-char:
type: int
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: bindings: Add separate binding for Nordic nRF Family SPI Slave Use separate bindings for nRF Family SPI Slaves and SPI Masters so that the properties "csn" and "def-char" can be made required for Slaves (for Masters such settings are not applicable), and to avoid confusion between the properties "csn" and "cs-gpios" for Master nodes. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2019-01-31 19:40:54 +08:00
description: >
Default character. Character clocked out when the slave was not
provided with buffers and is ignoring the transaction.