From: Rob Herring <robh@kernel.org>
To: Michal Simek <michal.simek@xilinx.com>
Cc: devicetree@vger.kernel.org, monstr@monstr.eu,
Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Will Deacon <will.deacon@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 8/8] arm64: zynqmp: Add support for Xilinx zc1751
Date: Wed, 7 Mar 2018 14:33:01 -0600 [thread overview]
Message-ID: <20180307203301.kufwtfsnxtks2gps@rob-hp-laptop> (raw)
In-Reply-To: <9f84bb43ee3e57b1635250a59e7b588831374649.1520017397.git.michal.simek@xilinx.com>
On Fri, Mar 02, 2018 at 08:04:34PM +0100, Michal Simek wrote:
> Xilinx zc1751 boards is used for silicon validation. Board can be
> extended with 5 FMCs/DCs cards to connect various IPs. Describe all
> these combinations.
>
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> ---
>
> Changes in v3:
> - Remove aliases for can, usb, gpio
> - dc2 fix spi_flashes and partitions
>
> Changes in v2:
> - Record compatible string to xilinx.txt
>
> Documentation/devicetree/bindings/arm/xilinx.txt | 3 +
> arch/arm64/boot/dts/xilinx/Makefile | 5 +
> .../boot/dts/xilinx/zynqmp-zc1751-xm015-dc1.dts | 131 +++++++++++++++
> .../boot/dts/xilinx/zynqmp-zc1751-xm016-dc2.dts | 168 +++++++++++++++++++
> .../boot/dts/xilinx/zynqmp-zc1751-xm017-dc3.dts | 150 +++++++++++++++++
> .../boot/dts/xilinx/zynqmp-zc1751-xm018-dc4.dts | 178 +++++++++++++++++++++
> .../boot/dts/xilinx/zynqmp-zc1751-xm019-dc5.dts | 125 +++++++++++++++
> 7 files changed, 760 insertions(+)
> create mode 100644 arch/arm64/boot/dts/xilinx/zynqmp-zc1751-xm015-dc1.dts
> create mode 100644 arch/arm64/boot/dts/xilinx/zynqmp-zc1751-xm016-dc2.dts
> create mode 100644 arch/arm64/boot/dts/xilinx/zynqmp-zc1751-xm017-dc3.dts
> create mode 100644 arch/arm64/boot/dts/xilinx/zynqmp-zc1751-xm018-dc4.dts
> create mode 100644 arch/arm64/boot/dts/xilinx/zynqmp-zc1751-xm019-dc5.dts
Reviewed-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2018-03-07 20:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 19:04 [PATCH v3 0/8] arm64: zynqmp: Add support for existing Xilinx ZynqMP based boards Michal Simek
2018-03-02 19:04 ` [PATCH v3 1/8] dt-bindings: xilinx: Add description for ZynqMP Michal Simek
2018-03-02 19:04 ` [PATCH v3 2/8] arm64: zynqmp: Add support for Xilinx zcu100-revC Michal Simek
2018-03-02 19:04 ` [PATCH v3 3/8] arm64: zynqmp: Add support for Xilinx zcu102 Michal Simek
2018-03-02 19:04 ` [PATCH v3 4/8] arm64: zynqmp: Add support for Xilinx zcu104-revA Michal Simek
2018-03-07 20:31 ` Rob Herring
2018-03-02 19:04 ` [PATCH v3 5/8] arm64: zynqmp: Add support for Xilinx zcu106-revA Michal Simek
2018-03-07 20:32 ` Rob Herring
2018-03-02 19:04 ` [PATCH v3 6/8] arm64: zynqmp: Add support for Xilinx zcu111-revA Michal Simek
2018-03-02 19:04 ` [PATCH v3 7/8] arm64: zynqmp: Add support for Xilinx zc12XX boards Michal Simek
2018-03-02 19:04 ` [PATCH v3 8/8] arm64: zynqmp: Add support for Xilinx zc1751 Michal Simek
2018-03-07 20:33 ` 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=20180307203301.kufwtfsnxtks2gps@rob-hp-laptop \
--to=robh@kernel.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=will.deacon@arm.com \
--cc=yamada.masahiro@socionext.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