From: Jagan Teki <jagan@amarulasolutions.com>
To: u-boot@lists.denx.de
Subject: [PATCH v2 0/7] rockchip: Add RockPI N8/N10 support
Date: Wed, 8 Jul 2020 15:35:21 +0530 [thread overview]
Message-ID: <20200708100528.419035-1-jagan@amarulasolutions.com> (raw)
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.
Rock Pi N8 is a Rockchip RK3288 based SBC, which has
- VMARC RK3288 SOM (as per SMARC standard) from Vamrs.
- Compatible carrier board from Radxa.
All the required dts(i) files are synced from linux-next
v5.7-rc1 since the current sync available for rk3399 is
the same.
All the N8 dts patches are in Linux mainling list.
Changes for v2:
- rebase on master
- collect Kever review tags
Any inputs?
Jagan.
Jagan Teki (7):
arm64: dts: rockchip: Sync v5.7-rc1 rk3399pro.dtsi
arm64: dts: rockchip: Sync v5.7-rc1 VMARC RK3399Pro SOM
ARM: dts: rockchip: Sync v5.7-rc1 Radxa Dalang Carrier
arm64: dts: rockchip: Add Radxa Rock Pi N10 initial support
arm64: dts: rockchip: Trivial cleanups for RockPI N10
ARM: dts: rockchip: Add VMARC RK3288 SOM initial support
ARM: dts: rockchip: Add Radxa Rock Pi N8 initial support
arch/arm/dts/Makefile | 4 +-
arch/arm/dts/rk3288-rock-pi-n8-u-boot.dtsi | 39 ++
arch/arm/dts/rk3288-rock-pi-n8.dts | 17 +
arch/arm/dts/rk3288-vmarc-som.dtsi | 261 ++++++++++++++
.../arm/dts/rk3399pro-rock-pi-n10-u-boot.dtsi | 7 +
arch/arm/dts/rk3399pro-rock-pi-n10.dts | 18 +
arch/arm/dts/rk3399pro-u-boot.dtsi | 6 +
arch/arm/dts/rk3399pro-vmarc-som.dtsi | 339 ++++++++++++++++++
arch/arm/dts/rk3399pro.dtsi | 22 ++
.../dts/rockchip-radxa-dalang-carrier.dtsi | 78 ++++
board/rockchip/evb_rk3288/MAINTAINERS | 6 +
board/rockchip/evb_rk3399/MAINTAINERS | 6 +
configs/rock-pi-n10-rk3399pro_defconfig | 46 +++
configs/rock-pi-n8-rk3288_defconfig | 66 ++++
14 files changed, 914 insertions(+), 1 deletion(-)
create mode 100644 arch/arm/dts/rk3288-rock-pi-n8-u-boot.dtsi
create mode 100644 arch/arm/dts/rk3288-rock-pi-n8.dts
create mode 100644 arch/arm/dts/rk3288-vmarc-som.dtsi
create mode 100644 arch/arm/dts/rk3399pro-rock-pi-n10-u-boot.dtsi
create mode 100644 arch/arm/dts/rk3399pro-rock-pi-n10.dts
create mode 100644 arch/arm/dts/rk3399pro-u-boot.dtsi
create mode 100644 arch/arm/dts/rk3399pro-vmarc-som.dtsi
create mode 100644 arch/arm/dts/rk3399pro.dtsi
create mode 100644 arch/arm/dts/rockchip-radxa-dalang-carrier.dtsi
create mode 100644 configs/rock-pi-n10-rk3399pro_defconfig
create mode 100644 configs/rock-pi-n8-rk3288_defconfig
--
2.25.1
next reply other threads:[~2020-07-08 10:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 10:05 Jagan Teki [this message]
2020-07-08 10:05 ` [PATCH v2 1/7] arm64: dts: rockchip: Sync v5.7-rc1 rk3399pro.dtsi Jagan Teki
2020-07-08 10:05 ` [PATCH v2 2/7] arm64: dts: rockchip: Sync v5.7-rc1 VMARC RK3399Pro SOM Jagan Teki
2020-07-08 10:05 ` [PATCH v2 3/7] ARM: dts: rockchip: Sync v5.7-rc1 Radxa Dalang Carrier Jagan Teki
2020-07-08 10:05 ` [PATCH v2 4/7] arm64: dts: rockchip: Add Radxa Rock Pi N10 initial support Jagan Teki
2020-07-08 10:05 ` [PATCH v2 5/7] arm64: dts: rockchip: Trivial cleanups for RockPI N10 Jagan Teki
2020-07-08 10:05 ` [PATCH v2 6/7] ARM: dts: rockchip: Add VMARC RK3288 SOM initial support Jagan Teki
2020-07-08 10:05 ` [PATCH v2 7/7] ARM: dts: rockchip: Add Radxa Rock Pi N8 " 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=20200708100528.419035-1-jagan@amarulasolutions.com \
--to=jagan@amarulasolutions.com \
--cc=u-boot@lists.denx.de \
/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