From: Jagan Teki <jagan@amarulasolutions.com>
To: Heiko Stuebner <heiko@sntech.de>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Akash Gajjar <akash@openedev.com>, Tom Cubie <tom@radxa.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-amarula@amarulasolutions.com,
Jagan Teki <jagan@amarulasolutions.com>
Subject: [PATCH v2 0/5] arm64: dts: rockchip: Add Rock Pi N10 support
Date: Thu, 21 Nov 2019 19:44:40 +0530 [thread overview]
Message-ID: <20191121141445.28712-1-jagan@amarulasolutions.com> (raw)
Unlike, other Rock PI boards from radxa, Rock Pi N10 SBC is based
on SOM + Carrier board combination.
Rock Pi N10 is a Rockchip RK3399Pro based SBC, which has
- VMARC RK3399Pro SOM (as per SMARC standard) from Vamrs.
- Dalang carrier board from Radxa.
This series add initial support for Rock Pi N10 and fixes comments
from Heiko from v1[1].
patch 0001: dt-bindings for VMARC RK3399Pro SOM
patch 0002: VMARC RK3399Pro SOM dtsi support
patch 0003: dt-bindings for Rock Pi N10
patch 0004: Radxa Dalang carrier board dtsi support
patch 0005: Rock Pi N10 dts support
Tested basic peripherals and will all more in future patches.
[1] https://patchwork.kernel.org/cover/11253649/
Any inputs?
Jagan.
Jagan Teki (5):
dt-bindings: arm: rockchip: Add VMARC RK3399Pro SOM binding
arm64: dts: rockchip: Add VMARC RK3399Pro SOM initial support
dt-bindings: arm: rockchip: Add Rock Pi N10 binding
ARM: dts: rockchip: Add Radxa Dalang Carrier board
arm64: dts: rockchip: Add Radxa Rock Pi N10 initial support
.../devicetree/bindings/arm/rockchip.yaml | 10 +
.../dts/rockchip-radxa-dalang-carrier.dtsi | 81 +++++
arch/arm64/boot/dts/rockchip/Makefile | 1 +
.../dts/rockchip/rk3399pro-rock-pi-n10.dts | 17 +
.../dts/rockchip/rk3399pro-vmarc-som.dtsi | 333 ++++++++++++++++++
5 files changed, 442 insertions(+)
create mode 100644 arch/arm/boot/dts/rockchip-radxa-dalang-carrier.dtsi
create mode 100644 arch/arm64/boot/dts/rockchip/rk3399pro-rock-pi-n10.dts
create mode 100644 arch/arm64/boot/dts/rockchip/rk3399pro-vmarc-som.dtsi
--
2.18.0.321.gffc6fa0e3
next reply other threads:[~2019-11-21 14:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 14:14 Jagan Teki [this message]
2019-11-21 14:14 ` [PATCH v2 1/5] dt-bindings: arm: rockchip: Add VMARC RK3399Pro SOM binding Jagan Teki
2019-12-04 19:32 ` Rob Herring
2019-12-04 20:14 ` Heiko Stübner
2019-11-21 14:14 ` [PATCH v2 2/5] arm64: dts: rockchip: Add VMARC RK3399Pro SOM initial support Jagan Teki
2019-11-21 14:14 ` [PATCH v2 3/5] dt-bindings: arm: rockchip: Add Rock Pi N10 binding Jagan Teki
2019-11-21 14:14 ` [PATCH v2 4/5] ARM: dts: rockchip: Add Radxa Dalang Carrier board Jagan Teki
2019-11-21 14:14 ` [PATCH v2 5/5] arm64: dts: rockchip: Add Radxa Rock Pi N10 initial support Jagan Teki
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=20191121141445.28712-1-jagan@amarulasolutions.com \
--to=jagan@amarulasolutions.com \
--cc=akash@openedev.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-amarula@amarulasolutions.com \
--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=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=tom@radxa.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).