[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200203083027.gdlrv7vcv5hir3g7@gilmour.lan>
Date: Mon, 3 Feb 2020 09:30:27 +0100
From: Maxime Ripard <maxime@...no.tech>
To: Florian Fainelli <f.fainelli@...il.com>
Cc: linux-arm-kernel@...r.kernel.org, devicetree@...r.kernel.org,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Ray Jui <rjui@...adcom.com>,
Scott Branden <sbranden@...adcom.com>,
"maintainer:BROADCOM IPROC ARM ARCHITECTURE"
<bcm-kernel-feedback-list@...adcom.com>,
Nicolas Saenz Julienne <nsaenzjulienne@...e.de>,
Sugaya Taichi <sugaya.taichi@...ionext.com>,
Olof Johansson <olof@...om.net>,
Andrew Jeffery <andrew@...id.au>,
Lubomir Rintel <lkundrak@...sk>,
"moderated list:BROADCOM IPROC ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>,
open list <linux-kernel@...r.kernel.org>,
"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
<linux-rpi-kernel@...ts.infradead.org>
Subject: Re: [PATCH 06/12] dt-bindings: arm: bcm: Convert BCM21664 to YAML
On Sun, Feb 02, 2020 at 01:18:21PM -0800, Florian Fainelli wrote:
> Update the Broadcom BCM21664 SoC binding document for boards/SoCs to use
> YAML. Verified with dt_binding_check and dtbs_check.
>
> Signed-off-by: Florian Fainelli <f.fainelli@...il.com>
> ---
> .../bindings/arm/bcm/brcm,bcm21664.txt | 15 ------------
> .../bindings/arm/bcm/brcm,bcm21664.yaml | 23 +++++++++++++++++++
> 2 files changed, 23 insertions(+), 15 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/arm/bcm/brcm,bcm21664.txt
> create mode 100644 Documentation/devicetree/bindings/arm/bcm/brcm,bcm21664.yaml
>
> diff --git a/Documentation/devicetree/bindings/arm/bcm/brcm,bcm21664.txt b/Documentation/devicetree/bindings/arm/bcm/brcm,bcm21664.txt
> deleted file mode 100644
> index e0774255e1a6..000000000000
> --- a/Documentation/devicetree/bindings/arm/bcm/brcm,bcm21664.txt
> +++ /dev/null
> @@ -1,15 +0,0 @@
> -Broadcom BCM21664 device tree bindings
> ---------------------------------------
> -
> -This document describes the device tree bindings for boards with the BCM21664
> -SoC.
> -
> -Required root node property:
> - - compatible: brcm,bcm21664
> -
> -Example:
> - / {
> - model = "BCM21664 SoC";
> - compatible = "brcm,bcm21664";
> - [...]
> - }
> diff --git a/Documentation/devicetree/bindings/arm/bcm/brcm,bcm21664.yaml b/Documentation/devicetree/bindings/arm/bcm/brcm,bcm21664.yaml
> new file mode 100644
> index 000000000000..8a38a6b68f60
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/bcm/brcm,bcm21664.yaml
> @@ -0,0 +1,23 @@
> +# SPDX-License-Identifier: GPL-2.0
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/arm/bcm/brcm,bcm21664.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Broadcom BCM21664 device tree bindings
> +
> +maintainers:
> + - Florian Fainelli <f.fainelli@...il.com>
> +
> +properties:
> + $nodename:
> + const: '/'
> + compatible:
> + oneOf:
> + - description: BCM21664 based boards
> + items:
> + - enum:
> + - brcm,bcm21664-garnet
> + - const: brcm,bcm21664
Do you really need the oneOf here?
Maxime
Powered by blists - more mailing lists