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/gpio/gpio-leds.yaml

27 lines
391 B
YAML
Raw Normal View History

dts: provide yaml bindings for led and gpio keys Provide yaml bindings for led and gpio keys (buttons). These are based on gpio bindings. Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>
2017-12-18 22:19:40 +08:00
#
# Copyright (c) 2018, Linaro Limited
#
# 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: provide yaml bindings for led and gpio keys Provide yaml bindings for led and gpio keys (buttons). These are based on gpio bindings. Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>
2017-12-18 22:19:40 +08:00
title: GPIO LED
version: 0.1
description: >
This is a representation of the LED GPIO nodes
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: provide yaml bindings for led and gpio keys Provide yaml bindings for led and gpio keys (buttons). These are based on gpio bindings. Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>
2017-12-18 22:19:40 +08:00
properties:
compatible:
constraint: "gpio-leds"
gpios:
type: compound
category: required
generation: define
label:
category: required