arm64: rockchip: dts: rk3399: Use rk3399-u-boot.dtsi
authorJagan Teki <jagan@amarulasolutions.com>
Tue, 7 May 2019 18:21:52 +0000 (23:51 +0530)
committerKever Yang <kever.yang@rock-chips.com>
Wed, 8 May 2019 09:34:13 +0000 (17:34 +0800)
commit90430fa895a197206da93a601607809998dc5a74
tree059db2c4032d69e8ea5ccde49bf329e16cf00576
parentb5f88913a661a668ae6da1e7c82bc9e654347ce5
arm64: rockchip: dts: rk3399: Use rk3399-u-boot.dtsi

Now we have
- board specific -u-boot.dtsi files for board specific u-boot
  dts changes.
- soc specific rk3399-u-boot.dtsi for soc specific u-boot
  dts changes.

So, include the rk3399-u-boot-dtsi on respective board -u-boot.dtsi
and drop the properties which are globally available in rk3399-u-boot.dtsi

Right now rk3399-u-boot.dtsi has sdmmc, spi1 u-boot,dm-pre-reloc
property and more properties and nodes can be move further based
on the requirements.

This would fix, the -u-boot.dtsi inclusion for evb, firefly, puma
boards that was accidentally merged on below commit.
"rockchip: dts: rk3399: Create initial rk3399-u-boot.dtsi"
(sha1: e05b4a4fa84b65a0c8873e8f34721741fe2bc09d)

Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
Reviewed-by: Kever Yang <kever.yang@rock-chips.com>
arch/arm/dts/rk3399-evb-u-boot.dtsi
arch/arm/dts/rk3399-firefly-u-boot.dtsi
arch/arm/dts/rk3399-gru-bob-u-boot.dtsi
arch/arm/dts/rk3399-gru-u-boot.dtsi [new file with mode: 0644]
arch/arm/dts/rk3399-gru.dtsi
arch/arm/dts/rk3399-puma-ddr1600.dts
arch/arm/dts/rk3399-puma.dtsi