ARM: mvebu: Add BootROM to Armada 370/XP device tree
In order to access the SoC BootROM, we need to declare a mapping (through a ranges property). The mbus driver will use this property to allocate a suitable address decoding window. Signed-off-by:Ezequiel Garcia <ezequiel.garcia@free-electrons.com> Tested-by:
Andrew Lunn <andrew@lunn.ch> Tested-by:
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> Signed-off-by:
Jason Cooper <jason@lakedaemon.net>
Showing
- arch/arm/boot/dts/armada-370-db.dts 2 additions, 1 deletionarch/arm/boot/dts/armada-370-db.dts
- arch/arm/boot/dts/armada-370-mirabox.dts 2 additions, 1 deletionarch/arm/boot/dts/armada-370-mirabox.dts
- arch/arm/boot/dts/armada-370-rd.dts 2 additions, 1 deletionarch/arm/boot/dts/armada-370-rd.dts
- arch/arm/boot/dts/armada-370.dtsi 5 additions, 0 deletionsarch/arm/boot/dts/armada-370.dtsi
- arch/arm/boot/dts/armada-xp-db.dts 2 additions, 1 deletionarch/arm/boot/dts/armada-xp-db.dts
- arch/arm/boot/dts/armada-xp-gp.dts 2 additions, 1 deletionarch/arm/boot/dts/armada-xp-gp.dts
- arch/arm/boot/dts/armada-xp-openblocks-ax3-4.dts 2 additions, 1 deletionarch/arm/boot/dts/armada-xp-openblocks-ax3-4.dts
- arch/arm/boot/dts/armada-xp.dtsi 5 additions, 0 deletionsarch/arm/boot/dts/armada-xp.dtsi
Loading
Please register or sign in to comment