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/st,stm32-spi.yaml

24 lines
370 B
YAML
Raw 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-06 01:03:21 +08: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 06:03:49 +08: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-06 01:03:21 +08:00
title: STM32 SPI
description: >
This binding gives a base representation of the STM32 SPI controller
inherits:
dts: bindings: Rename spi.yaml to spi-controller.yaml Renaming bindings to consistently be called foo-controller.yaml for controllers and foo-device.yaml for devices (last one mostly makes sense for devices on buses and the like). I was thinking of having a plain foo.yaml be the controller as well, but !include interrupt.yaml reads much worse than !include interrupt-controller.yaml Another advantage of this approach is that no binding changes meaning (which could be risky). It's just adding suffixes to filenames. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-08-16 16:14:17 +08:00
!include spi-controller.yaml
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-06 01:03:21 +08:00
properties:
compatible:
constraint: "st,stm32-spi"
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 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-06 01:03:21 +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