Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1422747AbbD2JZy (ORCPT ); Wed, 29 Apr 2015 05:25:54 -0400 Received: from mail-wi0-f173.google.com ([209.85.212.173]:37432 "EHLO mail-wi0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1031706AbbD2JZu (ORCPT ); Wed, 29 Apr 2015 05:25:50 -0400 Date: Wed, 29 Apr 2015 10:25:45 +0100 From: Lee Jones To: Andrew Bresticker Cc: Stephen Warren , Thierry Reding , Alexandre Courbot , linux-tegra@vger.kernel.org, linux-usb@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Samuel Ortiz Subject: Re: [PATCH V7 4/9] mfd: Add binding document for NVIDIA Tegra XUSB Message-ID: <20150429092545.GR9169@x1> References: <1430174242-29465-1-git-send-email-abrestic@chromium.org> <1430174242-29465-5-git-send-email-abrestic@chromium.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1430174242-29465-5-git-send-email-abrestic@chromium.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3256 Lines: 98 On Mon, 27 Apr 2015, Andrew Bresticker wrote: > Add a binding document for the XUSB host complex on NVIDIA Tegra124 > and later SoCs. The XUSB host complex includes a mailbox for > communication with the XUSB micro-controller and an xHCI host-controller. > > Signed-off-by: Andrew Bresticker > Cc: Rob Herring > Cc: Pawel Moll > Cc: Mark Rutland > Cc: Ian Campbell > Cc: Kumar Gala > Cc: Samuel Ortiz > Cc: Lee Jones > --- > New for v7. > --- > .../bindings/mfd/nvidia,tegra124-xusb.txt | 46 ++++++++++++++++++++++ > 1 file changed, 46 insertions(+) > create mode 100644 Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt > > diff --git a/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt b/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt > new file mode 100644 > index 0000000..6a46680 > --- /dev/null > +++ b/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt > @@ -0,0 +1,46 @@ > +NVIDIA Tegra XUSB host copmlex > +============================== > + > +The XUSB host complex on Tegra124 and later SoCs contains an xHCI host > +controller and a mailbox for communication with the XUSB micro-controller. > + > +Required properties: > +-------------------- > + - compatible: For Tegra124, must contain "nvidia,tegra124-xusb". > + Otherwise, must contain '"nvidia,-xusb", "nvidia,tegra124-xusb"' > + where is tegra132. Okay. Why? > + - reg: Must contain register base and length for each register set listed > + in reg-names. You've mentioned 2 of the cells, what about the remaining 2? > + - reg-names: Must include the following entries: > + - xhci > + - fpci > + - ipfs > + - interrupts: Must contain an interrupt for each entry in interrupt-names. > + - interrupt-names: Must include the following entries: > + - host > + - smi > + - pme > + > +Example: > +-------- > + usb@0,70090000 { > + compatible = "nvidia,tegra124-xusb"; > + reg = <0x0 0x70090000 0x0 0x8000>, > + <0x0 0x70098000 0x0 0x1000>, > + <0x0 0x70099000 0x0 0x1000>; > + reg-names = "xhci", "fpci", "ipfs"; > + interrupts = , > + , > + ; > + interrupt-names = "host", "smi", "pme"; Are these resources used by both children? If not, place them into the children and ioremap() them from the associated child drivers. Using an MFD driver to pull all of this out an disseminate it is a bit bonkers. > + usb-host { > + compatible = "nvidia,tegra124-xhci"; > + ... > + }; > + > + mailbox { > + compatible = "nvidia,tegra124-xusb-mbox"; > + ... > + }; > + }; -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/