From: Ezequiel Garcia <ezequiel@collabora.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
heiko@sntech.de, robh+dt@kernel.org
Cc: vicencb@gmail.com, shawn.lin@rock-chips.com,
enric.balletbo@collabora.com, pbrobinson@gmail.com,
tom@vamrs.com, dev@vamrs.com, stephen@vamrs.com,
amit.kucheria@linaro.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] Add 96Boards Rock960 CE board support
Date: Fri, 14 Sep 2018 14:42:51 -0300 [thread overview]
Message-ID: <a40ed76f22fd43f68af07d9bb56a0ff38171eef9.camel@collabora.com> (raw)
In-Reply-To: <20180913180545.29756-1-manivannan.sadhasivam@linaro.org>
On Thu, 2018-09-13 at 23:35 +0530, Manivannan Sadhasivam wrote:
> This patchset adds 96Boards Rock960 CE board support. Rock960 CE
> (Consumer Edition) board is one of the member of 96Boards Consumer
> Edition and AI platform and is manufactured by Vamrs Limited. Most of
> the board configuration is shared with the Ficus board manufactured by
> vamrs, which is an Enterprise 96Board.
>
> For the sake of avoiding code duplication, a common rock960.dtsi file
> with common DT nodes for both boards and separate board specific DTS
> files has been added.
>
> To be specific, below are some of the key differences between both
> boards:
>
> 1. Different host enable GPIO for USB
> 2. Different power and reset GPIO for PCI-E
> 3. No Ethernet port on Rock960
>
> While adding the board support, SD card Chip detection support is also
> added to the common dtsi file, shared by both boards.
>
> This series has been tested on Rock960 CE v1.2 board.
>
> Thanks,
> Mani
>
> Changes in v3:
>
> * Moved usb and pcie nodes to common dtsi and kept only the properties
> which differ in board specific dts.
> * Updated the common dtsi commit description.
>
> Changes in v2:
>
> * Changed the board compatible to "vamrs,rock960"
>
> Manivannan Sadhasivam (4):
> arm64: dts: rockchip: Split out common nodes for Rock960 based boards
> dt-bindings: arm: rockchip: Add binding for Rock960 board
> arm64: boot: dts: rockchip: Add support for Rock960 board
> arm64: dts: rockchip: Enable SD card detection for Rock960 boards
>
> .../devicetree/bindings/arm/rockchip.txt | 4 +
> arch/arm64/boot/dts/rockchip/Makefile | 1 +
> arch/arm64/boot/dts/rockchip/rk3399-ficus.dts | 524 +----------------
> .../boot/dts/rockchip/rk3399-rock960.dts | 52 ++
> .../boot/dts/rockchip/rk3399-rock960.dtsi | 542 ++++++++++++++++++
> 5 files changed, 604 insertions(+), 519 deletions(-)
> create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-rock960.dts
> create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-rock960.dtsi
>
Looks pretty good!
When applying this series, I noticed that it conflicts with
commit 8bb878cf20ae10809c36db96993bfce7026d062b
Author: Levin Du <djw@t-chip.com.cn>
Date: Mon Jul 30 10:12:01 2018 +0800
arm64: dts: rockchip: add support for ROC-RK3399-PC board
resolution is trivial, but you might want to rebase and resend,
to make Heiko's life easier.
Thanks,
Eze
next prev parent reply other threads:[~2018-09-14 17:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 18:05 [PATCH v3 0/4] Add 96Boards Rock960 CE board support Manivannan Sadhasivam
2018-09-13 18:05 ` [PATCH v3 1/4] arm64: dts: rockchip: Split out common nodes for Rock960 based boards Manivannan Sadhasivam
2018-09-13 18:05 ` [PATCH v3 2/4] dt-bindings: arm: rockchip: Add binding for Rock960 board Manivannan Sadhasivam
2018-09-26 21:06 ` Rob Herring
2018-09-13 18:05 ` [PATCH v3 3/4] arm64: boot: dts: rockchip: Add support " Manivannan Sadhasivam
2018-09-13 18:05 ` [PATCH v3 4/4] arm64: dts: rockchip: Enable SD card detection for Rock960 boards Manivannan Sadhasivam
2018-09-14 17:42 ` Ezequiel Garcia [this message]
2018-09-14 17:55 ` [PATCH v3 0/4] Add 96Boards Rock960 CE board support Heiko Stuebner
2018-09-22 20:57 ` Heiko Stuebner
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=a40ed76f22fd43f68af07d9bb56a0ff38171eef9.camel@collabora.com \
--to=ezequiel@collabora.com \
--cc=amit.kucheria@linaro.org \
--cc=dev@vamrs.com \
--cc=devicetree@vger.kernel.org \
--cc=enric.balletbo@collabora.com \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=pbrobinson@gmail.com \
--cc=robh+dt@kernel.org \
--cc=shawn.lin@rock-chips.com \
--cc=stephen@vamrs.com \
--cc=tom@vamrs.com \
--cc=vicencb@gmail.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).