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: devicetree@vger•kernel.org, Tom Cubie <tom@radxa•com>,
linux-kernel@vger•kernel.org, linux-rockchip@lists•infradead.org,
Akash Gajjar <akash@openedev•com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro•org>,
linux-amarula@amarulasolutions•com,
linux-arm-kernel@lists•infradead.org,
Jagan Teki <jagan@amarulasolutions•com>
Subject: [PATCH 0/5] arm64: dts: rockchip: Add Rock Pi N10 support
Date: Wed, 20 Nov 2019 17:09:18 +0530 [thread overview]
Message-ID: <20191120113923.11685-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.
- Compatible carrier board from Radxa.
This series add initial support for Rock Pi N10.
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 carrier board dtsi support
patch 0005: Rock Pi N10 dts support
Tested basic peripherals and will all more in future patches.
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 Carrier board
arm64: dts: rockchip: Add Radxa Rock Pi N10 initial support
.../devicetree/bindings/arm/rockchip.yaml | 10 +
.../boot/dts/rockchip-radxa-carrierboard.dtsi | 81 +++++
arch/arm64/boot/dts/rockchip/Makefile | 1 +
.../dts/rockchip/rk3399pro-rock-pi-n10.dts | 17 +
.../dts/rockchip/rk3399pro-vmarc-som.dtsi | 339 ++++++++++++++++++
5 files changed, 448 insertions(+)
create mode 100644 arch/arm/boot/dts/rockchip-radxa-carrierboard.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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-11-20 11:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 11:39 Jagan Teki [this message]
2019-11-20 11:39 ` [PATCH 1/5] dt-bindings: arm: rockchip: Add VMARC RK3399Pro SOM binding Jagan Teki
2019-11-20 11:39 ` [PATCH 2/5] arm64: dts: rockchip: Add VMARC RK3399Pro SOM initial support Jagan Teki
2019-11-20 13:28 ` Heiko Stübner
2019-11-20 15:51 ` Jagan Teki
2019-11-20 11:39 ` [PATCH 3/5] dt-bindings: arm: rockchip: Add Rock Pi N10 binding Jagan Teki
2019-11-20 11:39 ` [PATCH 4/5] ARM: dts: rockchip: Add Radxa Carrier board Jagan Teki
2019-11-20 13:25 ` Heiko Stübner
2019-11-20 13:45 ` Jagan Teki
2019-11-20 13:53 ` Heiko Stübner
2019-11-20 15:33 ` Jagan Teki
2019-11-20 11:39 ` [PATCH 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=20191120113923.11685-1-jagan@amarulasolutions.com \
--to=jagan@amarulasolutions$(echo .)com \
--cc=akash@openedev$(echo .)com \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=heiko@sntech$(echo .)de \
--cc=linux-amarula@amarulasolutions$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-rockchip@lists$(echo .)infradead.org \
--cc=manivannan.sadhasivam@linaro$(echo .)org \
--cc=mark.rutland@arm$(echo .)com \
--cc=robh+dt@kernel$(echo .)org \
--cc=tom@radxa$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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