diff options
| author |   Thomas Petazzoni <thomas.petazzoni@free-electrons.com> | 2014-02-17 15:23:27 +0100 |
|---|---|---|
| committer |   Jason Cooper <jason@lakedaemon.net> | 2014-02-22 00:43:59 +0000 |
| commit | 9aa30f1c13d1df2fc82ef0d0fd506306d8c8cef2 (patch) | |
| tree | 839c1d5c4622ad6a35ea281273bdd7628ebb3f9e /Documentation/devicetree/bindings/arm | |
| parent | ARM: mvebu: add workaround for data abort issue on Armada 375 (diff) | |
| download | linux-dev-9aa30f1c13d1df2fc82ef0d0fd506306d8c8cef2.tar.xz linux-dev-9aa30f1c13d1df2fc82ef0d0fd506306d8c8cef2.zip | |
ARM: mvebu: add initial support for the Armada 380/385 SOCs
This commit adds the basic support for the Armada 380 and Armada 385
SOCs. These SoCs share most of their IP with the Armada 370/XP
SoCs. The main difference is the use of a Cortex A9 CPU instead of the
PJ4B CPU. The Armada 380 is a single core Cortex-A9, while the Armada
385 is a dual-core Cortex-A9.
The support is introduced in board-v7.c, together with Armada 370/XP,
but a separate DT structure is added, because Armada 38x will need a
different set of SMP operations when the SMP support is introduced.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Jason Cooper <jason@lakedaemon.net>
Diffstat (limited to 'Documentation/devicetree/bindings/arm')
| -rw-r--r-- | Documentation/devicetree/bindings/arm/armada-38x.txt | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/Documentation/devicetree/bindings/arm/armada-38x.txt b/Documentation/devicetree/bindings/arm/armada-38x.txt new file mode 100644 index 000000000000..11f2330a6554 --- /dev/null +++ b/Documentation/devicetree/bindings/arm/armada-38x.txt @@ -0,0 +1,10 @@ +Marvell Armada 38x Platforms Device Tree Bindings +------------------------------------------------- + +Boards with a SoC of the Marvell Armada 38x family shall have the +following property: + +Required root node property: + + - compatible: must contain either "marvell,armada380" or + "marvell,armada385" depending on the variant of the SoC being used. |