arm64: rockchip: dts: rk3399: Add board -u-boot.dtsi files
authorJagan Teki <jagan@amarulasolutions.com>
Tue, 7 May 2019 18:21:50 +0000 (23:51 +0530)
committerKever Yang <kever.yang@rock-chips.com>
Wed, 8 May 2019 09:34:13 +0000 (17:34 +0800)
commitddf49cbf35c97d043c46e9bc9c3029053720a812
tree85f262f420d7da59d65ba4bd0528e6a1af9dceb6
parent82d08de9c5dba1b5dd0689570c74698aae307599
arm64: rockchip: dts: rk3399: Add board -u-boot.dtsi files

Devicetree files in RK3399 platform is synced from Linux, like other
platforms does. Apart from these u-boot in rk3399 would also require
some u-boot specific node like dmc.

dmc node has big chunk of DDR timing parameters which are specific
to specific board, and maintained with rk3399-sdram*.dtsi.

So, create board specific -u-boot.dtsi files and move these sdram dtsi
files accordingly. This would help of maintain u-boot specific changes
separately without touching Linux dts(i) files which indeed easy for
syncing from Linux between releases.

These board specific -u-boot.dtsi can be extendible to add more u-boot
specific nodes or properties in future.

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 [new file with mode: 0644]
arch/arm/dts/rk3399-evb.dts
arch/arm/dts/rk3399-ficus-u-boot.dtsi [new file with mode: 0644]
arch/arm/dts/rk3399-ficus.dts
arch/arm/dts/rk3399-firefly-u-boot.dtsi [new file with mode: 0644]
arch/arm/dts/rk3399-firefly.dts
arch/arm/dts/rk3399-gru-bob-u-boot.dtsi [new file with mode: 0644]
arch/arm/dts/rk3399-gru-bob.dts
arch/arm/dts/rk3399-rock960-u-boot.dtsi [new file with mode: 0644]
arch/arm/dts/rk3399-rock960.dts