From: Jagan Teki <jagan@amarulasolutions.com>
To: u-boot@lists.denx.de
Subject: [PATCH v2 0/6] rk3399: Sync linux v5.7-rc1 dts(i)
Date: Tue, 28 Apr 2020 15:30:13 +0530 [thread overview]
Message-ID: <20200428100019.19155-1-jagan@amarulasolutions.com> (raw)
This would help to add new boards along with new drivers
like DWC3, PCIe on rk3399 platform.
So, add v5.7-rc1 linux-next dts(i) files on rk3399 platform.
Changes for v2:
- keep roc-rk3399-pc dc_12v changes to -u-boot.dtsi
[1] https://patchwork.ozlabs.org/project/uboot/cover/20200425105319.12009-1-jagan at amarulasolutions.com/
Any inputs?
Jagan.
Jagan Teki (5):
arm64: dts: rk3399-puma: Move u-boot properties into -u-boot.dtsi
arm64: dts: rk3399-evb: Move u-boot properties into -u-boot.dtsi
clk: rk3399: Set empty for HCLK_SD assigned-clocks
arm64: dts: rk3399: Sync v5.7-rc1 from Linux
arm: dts: rk3399: Sync roc-pc-mezzanine from v5.7-rc1
Suniel Mahesh (1):
rk3399: Add ROC-RK3399-PC Mezzanine board
arch/arm/dts/Makefile | 1 +
arch/arm/dts/cros-ec-keyboard.dtsi | 10 +-
arch/arm/dts/cros-ec-sbs.dtsi | 39 +-
arch/arm/dts/rk3399-evb-u-boot.dtsi | 8 +
arch/arm/dts/rk3399-evb.dts | 522 ++++++++----
arch/arm/dts/rk3399-ficus.dts | 6 +
arch/arm/dts/rk3399-firefly.dts | 251 ++++--
arch/arm/dts/rk3399-gru-bob.dts | 16 +-
arch/arm/dts/rk3399-gru-chromebook.dtsi | 40 +-
arch/arm/dts/rk3399-gru-kevin.dts | 34 +-
arch/arm/dts/rk3399-gru.dtsi | 90 +-
arch/arm/dts/rk3399-khadas-edge.dtsi | 3 +
arch/arm/dts/rk3399-leez-p710.dts | 36 +-
arch/arm/dts/rk3399-nanopc-t4.dts | 47 +-
arch/arm/dts/rk3399-nanopi4.dtsi | 66 +-
arch/arm/dts/rk3399-orangepi.dts | 79 +-
arch/arm/dts/rk3399-puma-u-boot.dtsi | 31 +-
arch/arm/dts/rk3399-puma.dtsi | 578 +++++--------
.../dts/rk3399-roc-pc-mezzanine-u-boot.dtsi | 6 +
arch/arm/dts/rk3399-roc-pc-mezzanine.dts | 93 ++
arch/arm/dts/rk3399-roc-pc-u-boot.dtsi | 36 +
arch/arm/dts/rk3399-roc-pc.dts | 3 +-
arch/arm/dts/rk3399-roc-pc.dtsi | 35 +-
arch/arm/dts/rk3399-rock-pi-4.dts | 129 +++
arch/arm/dts/rk3399-rock960.dts | 49 ++
arch/arm/dts/rk3399-rock960.dtsi | 13 +-
arch/arm/dts/rk3399-rockpro64.dts | 751 +----------------
arch/arm/dts/rk3399-rockpro64.dtsi | 797 ++++++++++++++++++
arch/arm/dts/rk3399-u-boot.dtsi | 1 +
arch/arm/dts/rk3399.dtsi | 583 ++++++++-----
board/firefly/roc-pc-rk3399/MAINTAINERS | 2 +
configs/roc-pc-mezzanine-rk3399_defconfig | 67 ++
drivers/clk/rockchip/clk_rk3399.c | 1 +
33 files changed, 2763 insertions(+), 1660 deletions(-)
create mode 100644 arch/arm/dts/rk3399-roc-pc-mezzanine-u-boot.dtsi
create mode 100644 arch/arm/dts/rk3399-roc-pc-mezzanine.dts
create mode 100644 arch/arm/dts/rk3399-rockpro64.dtsi
create mode 100644 configs/roc-pc-mezzanine-rk3399_defconfig
--
2.17.1
next reply other threads:[~2020-04-28 10:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 10:00 Jagan Teki [this message]
2020-04-28 10:00 ` [PATCH v2 1/6] arm64: dts: rk3399-puma: Move u-boot properties into -u-boot.dtsi Jagan Teki
2020-04-28 14:12 ` Kever Yang
2020-04-28 14:12 ` [PATCH v2 1/6] arm64: dts: rk3399-puma: Move u-boot properties into -u-boot.dtsi【请注意，邮件由linux-rockchip-bounces+kever.yang=rock-chips.com@lists.infradead.org代发】 Kever Yang
2020-04-28 10:00 ` [PATCH v2 2/6] arm64: dts: rk3399-evb: Move u-boot properties into -u-boot.dtsi Jagan Teki
2020-04-28 14:12 ` Kever Yang
2020-04-28 10:00 ` [PATCH v2 3/6] clk: rk3399: Set empty for HCLK_SD assigned-clocks Jagan Teki
2020-04-28 14:13 ` Kever Yang
2020-04-28 10:00 ` [PATCH v2 4/6] arm64: dts: rk3399: Sync v5.7-rc1 from Linux Jagan Teki
2020-04-28 14:13 ` Kever Yang
2020-04-28 10:00 ` [PATCH v2 5/6] arm: dts: rk3399: Sync roc-pc-mezzanine from v5.7-rc1 Jagan Teki
2020-04-28 14:14 ` Kever Yang
2020-04-28 10:00 ` [PATCH v2 6/6] rk3399: Add ROC-RK3399-PC Mezzanine board Jagan Teki
2020-04-28 14:14 ` 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=20200428100019.19155-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