From: Jagan Teki <jagan@amarulasolutions.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v6 0/3] arm64: rockchip: dts: Add rk3399 -u-boot.dtsi files
Date: Sat, 27 Apr 2019 17:11:59 +0530 [thread overview]
Message-ID: <20190427114202.7358-1-jagan@amarulasolutions.com> (raw)
This series is a rework of v5 patch that send it in separate series[1]
All these changes are creating an initial 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 v6:
- spilt the existing patch[1] into multiple patches
and send as a separate series.
[1] https://patchwork.ozlabs.org/patch/1091720/
Any inputs?
Jagan.
Jagan Teki (3):
arm64: rockchip: dts: rk3399: Add board -u-boot.dtsi files
arm64: rockchip: dts: Add initial rk3399-u-boot.dtsi file
arm64: rockchip: dts: rk3399: Use rk3399-u-boot.dtsi
arch/arm/dts/rk3399-evb-u-boot.dtsi | 7 +++++++
arch/arm/dts/rk3399-evb.dts | 2 --
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 | 2 --
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 | 3 ---
arch/arm/dts/rk3399-rock960-u-boot.dtsi | 6 ++++++
arch/arm/dts/rk3399-rock960.dts | 1 -
arch/arm/dts/rk3399-u-boot.dtsi | 12 ++++++++++++
15 files changed, 52 insertions(+), 11 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
create mode 100644 arch/arm/dts/rk3399-u-boot.dtsi
--
2.18.0.321.gffc6fa0e3
next reply other threads:[~2019-04-27 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-27 11:41 Jagan Teki [this message]
2019-04-27 11:42 ` [U-Boot] [PATCH v6 1/3] arm64: rockchip: dts: rk3399: Add board -u-boot.dtsi files Jagan Teki
2019-04-27 11:42 ` [U-Boot] [PATCH v6 2/3] arm64: rockchip: dts: Add initial rk3399-u-boot.dtsi file Jagan Teki
2019-04-27 11:42 ` [U-Boot] [PATCH v6 3/3] arm64: rockchip: dts: rk3399: Use rk3399-u-boot.dtsi Jagan Teki
2019-05-02 7:43 ` [U-Boot] [PATCH v6 0/3] arm64: rockchip: dts: Add rk3399 -u-boot.dtsi files Paul Kocialkowski
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=20190427114202.7358-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