michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/dts/bindings/spi/spi-controller.yaml

26 lines
501 B
YAML
Raw Permalink Normal View History

dts: bindings: Add yaml files for STM32 SPI support to DT Add yaml files to DT for initial support of STM32 SPI Origin: original Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2018-01-05 18:03:21 +01:00
# Copyright (c) 2018, I-SENSE group of ICCS
# 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 00:03:49 +02:00
dts: edtlib: Sanity-check the final merged binding only Sanity-checking each !included file separately was inherited from the old scripts. It makes it messy to check that combinations of fields make sense, e.g. to check 'const:' or 'default:' against 'type:', since those fields might come from different files (this is handy, since it makes sense to just add/change a 'const:' value, for example). Drop the requirement that each !included file is a complete binding in itself, and treat them as binding fragments instead. Only check the final merged binding. This also means that !included files no longer need to have a 'description:' or 'title:' (those have always been unused for !included files), so remove those, and add comments that explain what the fragments are for instead. That should demystify bindings a bit. Also fix the descriptions of i2c.yaml, i2s.yaml, spi.yaml, and uart.yaml. They're for controllers, not devices. These are copy-paste error from the corresponding device .yaml files. Piggyback some indentation consistency nits in binding-template.yaml. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-08-15 14:06:15 +02:00
# Common fields for SPI controllers
dts: bindings: Add yaml files for STM32 SPI support to DT Add yaml files to DT for initial support of STM32 SPI Origin: original Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2018-01-05 18:03:21 +01: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 01:10:12 +02: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-07 18:12:49 +02:00
dts: bindings: Replace 'child-bus:'/'parent-bus:' with 'bus:'/'on-bus:' 'child-bus:'/'parent-bus:' have been deprecated. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-11-27 03:04:05 +01:00
bus: spi
dts: bindings: provide generic yaml description for spi-devices Provide generic yaml description for spi-devices such as sensors. Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2018-01-14 13:14:32 +01:00
dts: bindings: Add yaml files for STM32 SPI support to DT Add yaml files to DT for initial support of STM32 SPI Origin: original Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2018-01-05 18:03:21 +01:00
properties:
drivers/spi: Generate clock-frequency for SPI bus Use DTS to generate the clock frequency driving the SPI peripheral. Signed-off-by: Nathaniel Graff <nathaniel.graff@sifive.com>
2018-11-21 21:59:12 +01:00
clock-frequency:
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 00:22:01 +02:00
required: false
drivers/spi: Generate clock-frequency for SPI bus Use DTS to generate the clock frequency driving the SPI peripheral. Signed-off-by: Nathaniel Graff <nathaniel.graff@sifive.com>
2018-11-21 21:59:12 +01:00
description: Clock frequency the SPI peripheral is being driven at
dts: bindings: Add yaml files for STM32 SPI support to DT Add yaml files to DT for initial support of STM32 SPI Origin: original Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2018-01-05 18:03:21 +01:00
"#address-cells":
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
dts/bindings: use const to validate #<FOO>-cells In most cases #<FOO>-cells should be a constant. For example in spi controller #address-cells should be 1, and #size-cells should be 0. Use the const attribute to specify such single known values. Add const value to missing bindings which have cells. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2019-08-09 21:54:26 +02:00
const: 1
dts: bindings: Add yaml files for STM32 SPI support to DT Add yaml files to DT for initial support of STM32 SPI Origin: original Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2018-01-05 18:03:21 +01:00
"#size-cells":
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
dts/bindings: use const to validate #<FOO>-cells In most cases #<FOO>-cells should be a constant. For example in spi controller #address-cells should be 1, and #size-cells should be 0. Use the const attribute to specify such single known values. Add const value to missing bindings which have cells. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2019-08-09 21:54:26 +02:00
const: 0
dts: bindings: Add yaml files for STM32 SPI support to DT Add yaml files to DT for initial support of STM32 SPI Origin: original Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2018-01-05 18:03:21 +01:00
label:
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
dts: spi: Add optional cs-gpios to the spi bus controller binding Now that we can generate gpio info from dts lets add optional support fot the cs-gpios property in the bus controller node. This matches the binding spec from Linux on how cs-gpios are handled. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2018-05-10 18:19:26 +02:00
cs-gpios:
dts/bindings: Convert compound to phandle-array type Convert type from compound to phandle-array for various bindings that have properties like like <FOO>-gpios, pwms, clocks, interrupt-extended, etc. that are phandle-array's. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2019-08-14 15:58:07 +02:00
type: phandle-array
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