From: Maxime Ripard <maxime@cerno.tech>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>, Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
"maintainer:BROADCOM IPROC ARM ARCHITECTURE"
<bcm-kernel-feedback-list@broadcom.com>,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Sugaya Taichi <sugaya.taichi@socionext.com>,
Andrew Jeffery <andrew@aj.id.au>, Arnd Bergmann <arnd@arndb.de>,
Joel Stanley <joel@jms.id.au>, Vinod Koul <vkoul@kernel.org>,
"james.tai" <james.tai@realtek.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
<linux-rpi-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 12/12] dt-bindings: arm: bcm: Convert BCM2835 firmware binding to YAML
Date: Mon, 23 Mar 2020 09:40:44 +0100 [thread overview]
Message-ID: <20200323084044.dziwbk7pugoy73yh@gilmour.lan> (raw)
In-Reply-To: <47e12841-d9bb-3204-76c0-5bc0ef74b094@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2928 bytes --]
Hi Florian,
On Sun, Mar 22, 2020 at 02:35:17PM -0700, Florian Fainelli wrote:
>
>
> On 2/6/2020 11:23 AM, Rob Herring wrote:
> > On Tue, Feb 04, 2020 at 03:55:52PM -0800, Florian Fainelli wrote:
> >> Convert the Raspberry Pi BCM2835 firmware binding document to YAML.
> >> Verified with dt_binding_check and dtbs_check.
> >>
> >> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> >> ---
> >> .../arm/bcm/raspberrypi,bcm2835-firmware.txt | 14 --------
> >> .../arm/bcm/raspberrypi,bcm2835-firmware.yaml | 33 +++++++++++++++++++
> >> 2 files changed, 33 insertions(+), 14 deletions(-)
> >> delete mode 100644 Documentation/devicetree/bindings/arm/bcm/raspberrypi,bcm2835-firmware.txt
> >> create mode 100644 Documentation/devicetree/bindings/arm/bcm/raspberrypi,bcm2835-firmware.yaml
> >>
> >> diff --git a/Documentation/devicetree/bindings/arm/bcm/raspberrypi,bcm2835-firmware.txt b/Documentation/devicetree/bindings/arm/bcm/raspberrypi,bcm2835-firmware.txt
> >> deleted file mode 100644
> >> index 6824b3180ffb..000000000000
> >> --- a/Documentation/devicetree/bindings/arm/bcm/raspberrypi,bcm2835-firmware.txt
> >> +++ /dev/null
> >> @@ -1,14 +0,0 @@
> >> -Raspberry Pi VideoCore firmware driver
> >> -
> >> -Required properties:
> >> -
> >> -- compatible: Should be "raspberrypi,bcm2835-firmware"
> >> -- mboxes: Phandle to the firmware device's Mailbox.
> >> - (See: ../mailbox/mailbox.txt for more information)
> >> -
> >> -Example:
> >> -
> >> -firmware {
> >> - compatible = "raspberrypi,bcm2835-firmware";
> >> - mboxes = <&mailbox>;
> >> -};
> >> diff --git a/Documentation/devicetree/bindings/arm/bcm/raspberrypi,bcm2835-firmware.yaml b/Documentation/devicetree/bindings/arm/bcm/raspberrypi,bcm2835-firmware.yaml
> >> new file mode 100644
> >> index 000000000000..db355d970f2b
> >> --- /dev/null
> >> +++ b/Documentation/devicetree/bindings/arm/bcm/raspberrypi,bcm2835-firmware.yaml
> >> @@ -0,0 +1,33 @@
> >> +# SPDX-License-Identifier: GPL-2.0
> >> +%YAML 1.2
> >> +---
> >> +$id: http://devicetree.org/schemas/arm/bcm/raspberrypi,bcm2835-firmware.yaml#
> >> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> >> +
> >> +title: Raspberry Pi VideoCore firmware driver
> >> +
> >> +maintainers:
> >> + - Eric Anholt <eric@anholt.net>
> >> + - Stefan Wahren <wahrenst@gmx.net>
> >> +
> >> +properties:
> >> + compatible:
> >> + const: raspberrypi,bcm2835-firmware simple-bus
> > ^
> >
> > I need to check for spaces with the meta-schema...
>
> I believe I had tried to use:
>
> const: raspberrypi,bcm2835-firmware
> const: simple-bus
>
> but this did not work, and I had to resort to doing this.
That would be:
compatible:
items:
- const: raspberrypi,bcm2835-firmware
- const: simple-bus
It changes slightly from what the initial binding was saying though,
since it wasn't mentionning simple-bus at all? Is that on purpose?
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2020-03-23 8:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 23:55 [PATCH v2 00/12] dt-bindings: arm: bcm: Convert boards to YAML Florian Fainelli
2020-02-04 23:55 ` [PATCH v2 01/12] dt-bindings: arm: bcm: Convert Cygnus " Florian Fainelli
2020-02-04 23:55 ` [PATCH v2 02/12] dt-bindings: arm: bcm: Convert Hurricane 2 " Florian Fainelli
2020-02-04 23:55 ` [PATCH v2 03/12] dt-bindings: arm: bcm: Convert Northstar Plus " Florian Fainelli
2020-02-04 23:55 ` [PATCH v2 04/12] dt-bindings: arm: bcm: Convert Northstar 2 " Florian Fainelli
2020-02-04 23:55 ` [PATCH v2 05/12] dt-bindings: arm: bcm: Convert Stingray " Florian Fainelli
2020-02-04 23:55 ` [PATCH v2 06/12] dt-bindings: arm: bcm: Convert BCM21664 " Florian Fainelli
2020-02-04 23:55 ` [PATCH v2 07/12] dt-bindings: arm: bcm: Convert BCM23550 " Florian Fainelli
2020-02-04 23:55 ` [PATCH v2 08/12] dt-bindings: arm: bcm: Convert BCM4708 " Florian Fainelli
2020-02-04 23:55 ` [PATCH v2 09/12] dt-bindings: arm: bcm: Convert BCM11351 " Florian Fainelli
2020-02-04 23:55 ` [PATCH v2 10/12] dt-bindings: arm: bcm: Convert Vulcan " Florian Fainelli
2020-02-04 23:55 ` [PATCH v2 11/12] dt-bindings: arm: Document Broadcom SoCs 'secondary-boot-reg' Florian Fainelli
2020-02-05 7:49 ` Maxime Ripard
2020-02-05 17:48 ` Florian Fainelli
2020-02-04 23:55 ` [PATCH v2 12/12] dt-bindings: arm: bcm: Convert BCM2835 firmware binding to YAML Florian Fainelli
2020-02-06 19:23 ` Rob Herring
2020-03-22 21:35 ` Florian Fainelli
2020-03-23 8:40 ` Maxime Ripard [this message]
2020-03-23 10:42 ` Nicolas Saenz Julienne
2020-02-05 17:39 ` [PATCH v2 00/12] dt-bindings: arm: bcm: Convert boards " Scott Branden
2020-02-06 19:24 ` Rob Herring
2020-03-10 19:47 ` Florian Fainelli
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=20200323084044.dziwbk7pugoy73yh@gilmour.lan \
--to=maxime@cerno.tech \
--cc=andrew@aj.id.au \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=james.tai@realtek.com \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=nsaenzjulienne@suse.de \
--cc=rjui@broadcom.com \
--cc=robh@kernel.org \
--cc=sbranden@broadcom.com \
--cc=sugaya.taichi@socionext.com \
--cc=vkoul@kernel.org \
/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).