This commit adds the support for the USB3 controller in the Armada 375
SoC. The following things have been taken in consideration:
- The usb3-controller node has to be *outside* of the internal-regs{}
node, because this device needs to access special windows.
- The usb3-controller node has one ranges to describe the special
window to be created but it must be done at the board level in the
dts.
- The usb3-controller node has two entries in the reg property, the
first for XHCI, the second for the internal registers
Signed-off-by: Gregory CLEMENT <gregory.clem...@free-electrons.com>
---
arch/arm/boot/dts/armada-375.dtsi | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/armada-375.dtsi
b/arch/arm/boot/dts/armada-375.dtsi
index 0e0036800071..cbe64ba9eb65 100644
--- a/arch/arm/boot/dts/armada-375.dtsi
+++ b/arch/arm/boot/dts/armada-375.dtsi
@@ -465,5 +465,23 @@
};
};
+
+ /*
+ * On Armada 375, USB2 host controller and USB3 host
+ * controller are incompatible. That means that in the
+ * dts of your board, you can either select the USB2
+ * controller: marvell,orion-ehci or the USB3
+ * controller: marvell,armada-375-xhci, but not
+ * both. If both controllers are selected, then the
+ * kernel will select the USB3 by default.
+ */
+ usb3-controller {
+ compatible = "marvell,armada-375-xhci";
+ reg = <MBUS_ID(0x05, 0x00) 0 0x20000>,
+ <MBUS_ID(0xf0, 0x01) 0x5ff80 0x80>;
+ interrupts = <GIC_SPI 16 IRQ_TYPE_LEVEL_HIGH>;
+ clocks = <&gateclk 16>;
+ status = "disabled";
+ };
};
};
--
1.8.1.2
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
