diff options
| author | Jason Gunthorpe <jgunthorpe@obsidianresearch.com> | 2013-09-17 12:41:46 -0600 |
|---|---|---|
| committer | Jason Cooper <jason@lakedaemon.net> | 2013-10-01 16:28:03 +0000 |
| commit | 7f69f8a4997ad12e062ddac8d6f996a50b26ebc2 (patch) | |
| tree | 34ab73a188741fa994fe2cd6664bdeffb1d785b1 /arch/arm/boot/dts/kirkwood-nsa310.dts | |
| parent | 37078732998e51c2645db99e7434ccc6774dafed (diff) | |
| download | talos-op-linux-7f69f8a4997ad12e062ddac8d6f996a50b26ebc2.tar.gz talos-op-linux-7f69f8a4997ad12e062ddac8d6f996a50b26ebc2.zip | |
ARM: kirkwood: Remove kirkwood_setup_wins and rely on the DT binding
kirkwood_setup_wins is the last manual caller of mbus in kirkwood, don't
call it for DT boards and rely on the DT having a mbus node with
a proper ranges property to setup these windows.
Move all the mbus ranges properties for all boards into kirkwood.dtsi,
since they are currently all the same.
This makes the DT self consistent, since the physical address of the
NAND and CRYPTO are both referenced internally. The arbitary Linux
constants KIRKWOOD_NAND_MEM_PHYS_BASE and KIRKWOOD_SRAM_PHYS_BASE
no longer have to match the DT values.
Signed-off-by: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Acked-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Tested-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Signed-off-by: Jason Cooper <jason@lakedaemon.net>
Diffstat (limited to 'arch/arm/boot/dts/kirkwood-nsa310.dts')
| -rw-r--r-- | arch/arm/boot/dts/kirkwood-nsa310.dts | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/arch/arm/boot/dts/kirkwood-nsa310.dts b/arch/arm/boot/dts/kirkwood-nsa310.dts index 7aeae0c2c1f4..b5418bcaecce 100644 --- a/arch/arm/boot/dts/kirkwood-nsa310.dts +++ b/arch/arm/boot/dts/kirkwood-nsa310.dts @@ -15,7 +15,6 @@ }; mbus { - ranges = <MBUS_ID(0xf0, 0x01) 0 0xf1000000 0x100000>; pcie-controller { status = "okay"; |
