From mboxrd@z Thu Jan 1 00:00:00 1970 From: gregory.clement@free-electrons.com (Gregory CLEMENT) Date: Fri, 25 Apr 2014 16:07:14 +0200 Subject: [PATCH v2 16/18] ARM: mvebu: add USB3 controller Device Tree details for Armada 375 In-Reply-To: <1398434836-18908-1-git-send-email-gregory.clement@free-electrons.com> References: <1398434836-18908-1-git-send-email-gregory.clement@free-electrons.com> Message-ID: <1398434836-18908-17-git-send-email-gregory.clement@free-electrons.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 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 --- 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 = , + ; + interrupts = ; + clocks = <&gateclk 16>; + status = "disabled"; + }; }; }; -- 1.8.1.2