From: Rob Herring <robh@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH 1/5 v2] dt-bindings: arm: Add Integrator YAML schema
Date: Tue, 25 Feb 2020 12:27:15 -0600 [thread overview]
Message-ID: <20200225182715.GA15214@bogus> (raw)
In-Reply-To: <20200225084627.24825-1-linus.walleij@linaro.org>
On Tue, Feb 25, 2020 at 09:46:23AM +0100, Linus Walleij wrote:
> This implements the top-level schema for the ARM Integrator
> platforms.
>
> Cc: Sudeep Holla <sudeep.holla@arm.com>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ChangeLog v1->v2:
> - Collapse the compatible three items with two const in each to an
> enum with three possible values and a const syscon
> - Add reg with maxItems: 1 for syscon
> - Add reg as a required property of syscon
> - Make syscon a patternProperty and make sure it has a unit address
> - Add reg with maxItems: 1 for the core module
> - Require core module to be @10000000 and have all three compatibles.
> ---
> .../bindings/arm/arm,integrator.yaml | 87 +++++++++++++++++++
> 1 file changed, 87 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/arm,integrator.yaml
>
> diff --git a/Documentation/devicetree/bindings/arm/arm,integrator.yaml b/Documentation/devicetree/bindings/arm/arm,integrator.yaml
> new file mode 100644
> index 000000000000..2690491c1294
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/arm,integrator.yaml
> @@ -0,0 +1,87 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/arm/arm,integrator.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: ARM Integrator Boards Device Tree Bindings
> +
> +maintainers:
> + - Linus Walleij <linus.walleij@linaro.org>
> +
> +description: |+
> + These were the first ARM platforms officially supported by ARM Ltd.
> + They are ARMv4, ARMv5 and ARMv6-capable using different core tiles,
> + so the system is modular and can host a variety of CPU tiles called
> + "core tiles" and referred to in the device tree as "core modules".
> +
> +properties:
> + $nodename:
> + const: '/'
> + compatible:
> + oneOf:
> + - description: ARM Integrator Application Platform, this board has a PCI
> + host and several PCI slots, as well as a number of slots for logical
> + expansion modules, it is referred to as an "ASIC Development
> + Motherboard" and is extended with custom FPGA and is intended for
> + rapid prototyping. See ARM DUI 0098B. This board can physically come
> + pre-packaged in a PC Tower form factor called Integrator/PP1 or a
> + special metal fixture called Integrator/PP2, see ARM DUI 0169A.
> + items:
> + - const: arm,integrator-ap
> + - description: ARM Integrator Compact Platform (HBI-0086), this board has
> + a compact form factor and mainly consists of the bare minimum
> + peripherals to make use of the core module. See ARM DUI 0159B.
> + items:
> + - const: arm,integrator-cp
> + - description: ARM Integrator Standard Development Board (SDB) Platform,
> + this board is a PCI-based board conforming to the Microsoft SDB
> + (HARP) specification. See ARM DUI 0099A.
> + items:
> + - const: arm,integrator-sp
> +
> + core-module@10000000:
> + type: object
> + description: the root node in the Integrator platforms must contain
> + a core module child node. They are always at physical address
> + 0x10000000 in all the Integrator variants.
> + properties:
> + compatible:
> + items:
> + - const: arm,core-module-integrator
> + - const: syscon
> + - const: simple-mfd
> + reg:
> + maxItems: 1
> +
> + required:
> + - compatible
> + - reg
> +
> +patternProperties:
> + "^syscon@[0-9a-f]+$":
> + description: All Integrator boards must provide a system controller as a
> + node in the root of the device tree.
> + type: object
> + properties:
> + compatible:
> + items:
> + - enum:
> + - arm,integrator-ap-syscon
> + - arm,integrator-cp-syscon
> + - arm,integrator-sp-syscon
> + - const: syscon
> + reg:
> + maxItems: 1
> +
> + required:
> + - compatible
> + - reg
> +
> +
> +required:
> + - compatible
> + - syscon
This will fail to match anything if you have 'syscon@...' Unfortunately,
not yet any way to have required patterns in json-schema, though that is
being discussed.
With that dropped,
Reviewed-by: Rob Herring <robh@kernel.org>
> + - core-module@10000000
> +
> +...
> --
> 2.24.1
>
prev parent reply other threads:[~2020-02-25 18:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 8:46 [PATCH 1/5 v2] dt-bindings: arm: Add Integrator YAML schema Linus Walleij
2020-02-25 8:46 ` [PATCH 2/5 v2] dt-bindings: arm: Add Versatile " Linus Walleij
2020-02-25 18:30 ` Rob Herring
2020-02-25 8:46 ` [PATCH 3/5 v2] dt-bindings: arm: Add RealView " Linus Walleij
2020-02-25 18:31 ` Rob Herring
2020-02-25 8:46 ` [PATCH 4/5 v2] dt-bindings: arm: Add Versatile Express and Juno " Linus Walleij
2020-02-25 18:40 ` Rob Herring
2020-02-25 8:46 ` [PATCH 5/5 v2] dt-bindings: arm: Drop the non-YAML bindings Linus Walleij
2020-02-25 18:41 ` Rob Herring
2020-02-25 18:27 ` Rob Herring [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200225182715.GA15214@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=mark.rutland@arm.com \
--cc=sudeep.holla@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).