From: Michal Simek <michal.simek@xilinx.com>
To: Luis Araneda <luaraneda@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Michal Simek <michal.simek@xilinx.com>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 2/5] dt-bindings: xilinx: Add missing zynq boards
Date: Thu, 28 Jun 2018 08:44:06 +0200 [thread overview]
Message-ID: <eda7ca2a-e2de-8939-0784-89b619f6035e@xilinx.com> (raw)
In-Reply-To: <20180628054205.17737-3-luaraneda@gmail.com>
On 28.6.2018 07:42, Luis Araneda wrote:
> The bindings were missing when adding the device-tree files
> Also, improve description of existing boards
>
> Signed-off-by: Luis Araneda <luaraneda@gmail.com>
> ---
> .../devicetree/bindings/arm/xilinx.txt | 22 +++++++++++++++++--
> 1 file changed, 20 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/arm/xilinx.txt b/Documentation/devicetree/bindings/arm/xilinx.txt
> index b9043bc35..f1e911058 100644
> --- a/Documentation/devicetree/bindings/arm/xilinx.txt
> +++ b/Documentation/devicetree/bindings/arm/xilinx.txt
> @@ -8,15 +8,33 @@ Required root node properties:
>
> Additional compatible strings:
>
> -- Xilinx internal board cc108
> +- Xilinx CC108 board
No reason to remove internal word from here.
> "xlnx,zynq-cc108"
>
> -- Xilinx internal board zc770 with different FMC cards
> +- Avnet MicroZed board
> + "avnet,zynq-microzed"
> +
> +- Adapteva Parallella board
> + "adapteva,parallella"
> +
> +- Xilinx ZC702 board
> + "xlnx,zynq-zc702"
> +
> +- Xilinx ZC706 board
> + "xlnx,zynq-zc706"
> +
> +- Xilinx ZC770 board, with different FMC cards
> "xlnx,zynq-zc770-xm010"
> "xlnx,zynq-zc770-xm011"
> "xlnx,zynq-zc770-xm012"
> "xlnx,zynq-zc770-xm013"
>
> +- Avnet ZedBoard board
> + "avnet,zynq-zed"
> +
> +- Digilent Zybo board
> + "digilent,zynq-zybo"
> +
> - Digilent Zybo Z7 board
> "digilent,zynq-zybo-z7"
>
>
Not a problem to add missing strings.
Thanks,
Michal
next prev parent reply other threads:[~2018-06-28 6:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 5:42 [RFC PATCH 0/5] arm: dts: zynq: improvements and cleanup Luis Araneda
2018-06-28 5:42 ` [RFC PATCH 1/5] arm: dts: zynq: Set correct manufacturer for ZedBoard and MicroZed boards Luis Araneda
2018-06-28 6:36 ` Michal Simek
2018-07-03 6:51 ` Luis Araneda
2018-06-28 5:42 ` [RFC PATCH 2/5] dt-bindings: xilinx: Add missing zynq boards Luis Araneda
2018-06-28 6:44 ` Michal Simek [this message]
2018-07-03 6:53 ` Luis Araneda
2018-07-03 23:04 ` Rob Herring
2018-07-05 21:10 ` Luis Araneda
2018-06-28 5:42 ` [RFC PATCH 3/5] arm: dts: zynq: correct and improve the model property of dt files Luis Araneda
2018-06-28 6:39 ` Michal Simek
2018-06-28 5:42 ` [RFC PATCH 4/5] arm: dts: zynq: rename board zed to zedboard Luis Araneda
2018-06-28 6:40 ` Michal Simek
2018-07-03 6:56 ` Luis Araneda
2018-06-28 5:42 ` [RFC PATCH 5/5] arm: dts: zynq: remove "zynq" prefix from compatible property Luis Araneda
2018-06-28 6:41 ` Michal Simek
2018-07-03 7:18 ` Luis Araneda
2018-07-03 23:07 ` Rob Herring
2018-07-05 21:12 ` Luis Araneda
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=eda7ca2a-e2de-8939-0784-89b619f6035e@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luaraneda@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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