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 v3 0/4] arm64: dts: rockchip: Add Rock Pi N10 support Date: Mon, 16 Dec 2019 23:17:07 +0530 [thread overview] Message-ID: <20191216174711.17856-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. patch 0001: dt-bindings for Rock Pi N10 patch 0002: VMARC RK3399Pro SOM dtsi support patch 0003: Radxa Dalang carrier board dtsi support patch 0004: Rock Pi N10 dts support Tested basic peripherals and will all more in future patches. Any inputs? Jagan. Jagan Teki (4): dt-bindings: arm: rockchip: Add Rock Pi N10 binding arm64: dts: rockchip: Add VMARC RK3399Pro SOM initial support ARM: dts: rockchip: Add Radxa Dalang Carrier board arm64: dts: rockchip: Add Radxa Rock Pi N10 initial support .../devicetree/bindings/arm/rockchip.yaml | 6 + .../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, 438 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
WARNING: multiple messages have this Message-ID (diff)
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 v3 0/4] arm64: dts: rockchip: Add Rock Pi N10 support Date: Mon, 16 Dec 2019 23:17:07 +0530 [thread overview] Message-ID: <20191216174711.17856-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. patch 0001: dt-bindings for Rock Pi N10 patch 0002: VMARC RK3399Pro SOM dtsi support patch 0003: Radxa Dalang carrier board dtsi support patch 0004: Rock Pi N10 dts support Tested basic peripherals and will all more in future patches. Any inputs? Jagan. Jagan Teki (4): dt-bindings: arm: rockchip: Add Rock Pi N10 binding arm64: dts: rockchip: Add VMARC RK3399Pro SOM initial support ARM: dts: rockchip: Add Radxa Dalang Carrier board arm64: dts: rockchip: Add Radxa Rock Pi N10 initial support .../devicetree/bindings/arm/rockchip.yaml | 6 + .../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, 438 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 _______________________________________________ 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-12-16 17:47 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-12-16 17:47 Jagan Teki [this message] 2019-12-16 17:47 ` [PATCH v3 0/4] arm64: dts: rockchip: Add Rock Pi N10 support Jagan Teki 2019-12-16 17:47 ` [PATCH v3 1/4] dt-bindings: arm: rockchip: Add Rock Pi N10 binding Jagan Teki 2019-12-16 17:47 ` Jagan Teki 2019-12-18 22:15 ` Rob Herring 2019-12-18 22:15 ` Rob Herring 2019-12-18 22:15 ` Rob Herring 2019-12-16 17:47 ` [PATCH v3 2/4] arm64: dts: rockchip: Add VMARC RK3399Pro SOM initial support Jagan Teki 2019-12-16 17:47 ` Jagan Teki 2019-12-16 17:47 ` [PATCH v3 3/4] ARM: dts: rockchip: Add Radxa Dalang Carrier board Jagan Teki 2019-12-16 17:47 ` Jagan Teki 2019-12-16 17:47 ` [PATCH v3 4/4] arm64: dts: rockchip: Add Radxa Rock Pi N10 initial support Jagan Teki 2019-12-16 17:47 ` Jagan Teki 2019-12-21 12:15 ` [PATCH v3 0/4] arm64: dts: rockchip: Add Rock Pi N10 support Heiko Stuebner 2019-12-21 12:15 ` Heiko Stuebner 2019-12-21 12:15 ` 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=20191216174711.17856-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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.