zephyr/dts/bindings/spi/spi-device.yaml

#
# Copyright (c) 2018, I-SENSE group of ICCS
#
# SPDX-License-Identifier: Apache-2.0
#

title: SPI Device Base Structure

description: >
    This binding gives the base structures for all spi devices

inherits:
    !include base.yaml

parent:
    bus: spi

properties:
    reg:
      category: required
    spi-max-frequency:
      type: int
      category: required
      description: Maximum clock frequency of device's SPI interface in Hz
    label:
      category: required
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 20:14:32 +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: 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 20:14:32 +08:00			`title: SPI Device Base Structure`

			`description: >`
			`This binding gives the base structures for all spi devices`

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			`inherits:`
			`!include base.yaml`

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 20:14:32 +08:00			`parent:`
			`bus: spi`

			`properties:`
			`reg:`
			`category: required`
			`spi-max-frequency:`
dts/bindings: Fix type in spi-device.yaml Change type field in yaml binding to a valid choice. Should be 'int' Signed-off-by: Kumar Gala <kumar.gala@linaro.org> 2019-06-07 04:33:46 +08:00			`type: int`
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 20:14:32 +08:00			`category: required`
			`description: Maximum clock frequency of device's SPI interface in Hz`
			`label:`
			`category: required`