From: Jagan Teki <jagan@amarulasolutions.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v7 0/4] arm64: rockchip: dts: Add rk3399 -u-boot.dtsi files
Date: Tue, 7 May 2019 23:51:48 +0530 [thread overview]
Message-ID: <20190507182152.4254-1-jagan@amarulasolutions.com> (raw)
Unfortunately initial version of creating rk3399-u-boot.dtsi
has been merged, so this series is rework of previous v6 set[1]
on top of u-boot-rockchip/master
All these changes are updating rk3399-u-boot.dtsi and rk3399
board -u-boot.dtsi files and u-boot specific dts changes like
- sdram dtsi
- sdmmc, u-boot,dm-pre-reloc
- spi1, u-boot,dm-pre-reloc
Changes for v7:
- rebase on u-boot-rockchip/master
- recreate patches based on v1 series merge
- add patch for dtb build based on SoC type
Changes for v6:
- spilt the existing patch[2] into multiple patches
and send as a separate series.
[2] https://patchwork.ozlabs.org/patch/1091720/
[1] https://patchwork.ozlabs.org/cover/1091909/
Any inputs?
Jagan.
Jagan Teki (4):
dts: Makefile: Build rockchip dtbs based on SoC types
arm64: rockchip: dts: rk3399: Add board -u-boot.dtsi files
rockchip: dts: rk3399-u-boot: Add u-boot,dm-pre-reloc for spi1
arm64: rockchip: dts: rk3399: Use rk3399-u-boot.dtsi
arch/arm/dts/Makefile | 35 ++++++++++++++++++-------
arch/arm/dts/rk3399-evb-u-boot.dtsi | 7 +++++
arch/arm/dts/rk3399-evb.dts | 1 -
arch/arm/dts/rk3399-ficus-u-boot.dtsi | 6 +++++
arch/arm/dts/rk3399-ficus.dts | 1 -
arch/arm/dts/rk3399-firefly-u-boot.dtsi | 7 +++++
arch/arm/dts/rk3399-firefly.dts | 1 -
arch/arm/dts/rk3399-gru-bob-u-boot.dtsi | 7 +++++
arch/arm/dts/rk3399-gru-bob.dts | 1 -
arch/arm/dts/rk3399-gru-u-boot.dtsi | 6 +++++
arch/arm/dts/rk3399-gru.dtsi | 1 -
arch/arm/dts/rk3399-puma-ddr1600.dts | 1 +
arch/arm/dts/rk3399-puma.dtsi | 2 --
arch/arm/dts/rk3399-rock960-u-boot.dtsi | 6 +++++
arch/arm/dts/rk3399-rock960.dts | 1 -
arch/arm/dts/rk3399-u-boot.dtsi | 4 +++
16 files changed, 70 insertions(+), 17 deletions(-)
create mode 100644 arch/arm/dts/rk3399-evb-u-boot.dtsi
create mode 100644 arch/arm/dts/rk3399-ficus-u-boot.dtsi
create mode 100644 arch/arm/dts/rk3399-firefly-u-boot.dtsi
create mode 100644 arch/arm/dts/rk3399-gru-bob-u-boot.dtsi
create mode 100644 arch/arm/dts/rk3399-gru-u-boot.dtsi
create mode 100644 arch/arm/dts/rk3399-rock960-u-boot.dtsi
--
2.18.0.321.gffc6fa0e3
next reply other threads:[~2019-05-07 18:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 18:21 Jagan Teki [this message]
2019-05-07 18:21 ` [U-Boot] [PATCH v7 1/4] dts: Makefile: Build rockchip dtbs based on SoC types Jagan Teki
2019-05-08 3:38 ` Kever Yang
2019-05-09 3:00 ` [U-Boot] [PATCH v7 1/4] dts: Makefile: Build rockchip dtbs based on SoC types【请注意,邮件由linux-rockchip-bounces+kever.yang=rock-chips.com@lists.infradead.org代发】 Kever Yang
2019-05-07 18:21 ` [U-Boot] [PATCH v7 2/4] arm64: rockchip: dts: rk3399: Add board -u-boot.dtsi files Jagan Teki
2019-05-08 3:39 ` [U-Boot] [PATCH v7 2/4] arm64: rockchip: dts: rk3399: Add board -u-boot.dtsi files【请注意,邮件由linux-rockchip-bounces+kever.yang=rock-chips.com@lists.infradead.org代发】 Kever Yang
2019-05-09 3:01 ` [U-Boot] [PATCH v7 2/4] arm64: rockchip: dts: rk3399: Add board -u-boot.dtsi files Kever Yang
2019-05-07 18:21 ` [U-Boot] [PATCH v7 3/4] rockchip: dts: rk3399-u-boot: Add u-boot, dm-pre-reloc for spi1 Jagan Teki
2019-05-08 3:39 ` [U-Boot] [PATCH v7 3/4] rockchip: dts: rk3399-u-boot: Add u-boot, dm-pre-reloc for spi1【请注意,邮件由linux-rockchip-bounces+kever.yang=rock-chips.com@lists.infradead.org代发】 Kever Yang
2019-05-09 3:01 ` [U-Boot] [PATCH v7 3/4] rockchip: dts: rk3399-u-boot: Add u-boot, dm-pre-reloc for spi1 Kever Yang
2019-05-07 18:21 ` [U-Boot] [PATCH v7 4/4] arm64: rockchip: dts: rk3399: Use rk3399-u-boot.dtsi Jagan Teki
2019-05-08 3:39 ` [U-Boot] [PATCH v7 4/4] arm64: rockchip: dts: rk3399: Use rk3399-u-boot.dtsi【请注意,邮件由linux-rockchip-bounces+kever.yang=rock-chips.com@lists.infradead.org代发】 Kever Yang
2019-05-09 3:02 ` [U-Boot] [PATCH v7 4/4] arm64: rockchip: dts: rk3399: Use rk3399-u-boot.dtsi Kever Yang
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=20190507182152.4254-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