From: Rob Herring <robh@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH 4/5 v3] dt-bindings: arm: Add Versatile Express and Juno YAML schema
Date: Tue, 3 Mar 2020 08:28:10 -0600 [thread overview]
Message-ID: <20200303142810.GA20466@bogus> (raw)
In-Reply-To: <20200226110714.134904-1-linus.walleij@linaro.org>
On Wed, 26 Feb 2020 12:07:14 +0100, Linus Walleij wrote:
> This implements the top-level schema for the ARM Versatile
> Express and Juno platforms.
>
> Cc: Sudeep Holla <sudeep.holla@arm.com>
> Acked-by: Sudeep Holla <sudeep.holla@arm.com>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ChangeLog v2->v3:
> - Rename the smb@nnnnnnnn node to bus@nnnnnnnn, on a side
> track in parallel proposed a patch to change this in all
> device trees so we get coverage as well.
> - Drop an dash in front of maximum as minimum/maximum is a tuple
> - Move the simple-bus reference under the SMB node with an allOf
> directive so we get the restrictions of simple-bus with the
> additions of our compatible (etc)
> - Rewrite the compatible schema to use one enum and one const
> item.
> - Duplicate the compatible schema for motherboard also directly
> under the smb node with the option of being "simple-bus" only
> and expand the text description so people understand what is
> going on.
> - Indent the -if directive for required top-level properties
> one step (syntactically incorrect but was incidentally working)
> ChangeLog v1->v2:
> - Add missing platforms: VE RTSM, FVP, foundation model
> - Properly define the arm,vexpress,site arm,vexpress,position
> and arm,vexpress,dcc attributes. Maybe these are not the most
> elegant bindings but they are used so we need to contain it
> properly.
> - Add a patternProperty for the SMB (Static Memory Bus) which
> was only described in text in the Vexpress bindings. It is a
> "simple-bus" so just reference the existing bindings.
> - Define the layout of the "motherboard" node sometimes but
> not always found below the SMB node, using two address-cells
> with one for chipselect.
> - Make the arm,hbi property required on the ARMv7 variants.
> ---
> .../bindings/arm/arm,vexpress-juno.yaml | 223 ++++++++++++++++++
> 1 file changed, 223 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/arm,vexpress-juno.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2020-03-03 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 11:07 [PATCH 4/5 v3] dt-bindings: arm: Add Versatile Express and Juno YAML schema Linus Walleij
2020-03-03 14:28 ` 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=20200303142810.GA20466@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).