a0fceff1a2
Instead of
properties:
compatible:
constraint: "foo"
, just have
compatible: "foo"
at the top level of the binding.
For backwards compatibility, the old 'properties: compatible: ...' form
is still accepted for now, and is treated the same as a single-element
'compatible:'.
The old syntax was inspired by dt-schema (though it isn't
dt-schema-compatible), which is in turn a thin wrapper around
json-schema (the idea is to transform .dts files into YAML and then
verify them).
Maybe the idea was to gradually switch the syntax over to dt-schema and
then be able to use unmodified dt-schema bindings, but dt-schema is
really a different kind of tool (a completely standalone linter), and
works very differently from our stuff (see schemas/dt-core.yaml in the
dt-schema repo to get an idea of just how differently).
Better to keep it simple.
This commit also piggybacks some clarifications to the binding template
re. '#cells:'.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
22 lines
447 B
YAML
22 lines
447 B
YAML
#
|
|
# Copyright (c) 2018, Linaro Limited
|
|
#
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
#
|
|
|
|
title: GPIO KEYS
|
|
|
|
description: >
|
|
This is a representation of the GPIO KEYS nodes
|
|
|
|
compatible: "gpio-keys"
|
|
|
|
sub-node:
|
|
properties:
|
|
gpios:
|
|
type: phandle-array
|
|
required: true
|
|
label:
|
|
required: true
|
|
type: string
|
|
description: Human readable string describing the device (used by Zephyr for API name)
|