linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 4/9] mfd: Add binding document for NVIDIA Tegra XUSB
Date: Thu, 14 May 2015 08:45:04 +0100	[thread overview]
Message-ID: <20150514074504.GB22418@x1> (raw)
In-Reply-To: <55544F91.4060402@nvidia.com>

On Thu, 14 May 2015, Jon Hunter wrote:

> 
> On 14/05/15 08:29, Lee Jones wrote:
> > On Wed, 13 May 2015, Andrew Bresticker wrote:
> > 
> >> On Wed, May 13, 2015 at 9:50 AM, Lee Jones <lee.jones@linaro.org> wrote:
> >>> On Wed, 13 May 2015, Andrew Bresticker wrote:
> >>>
> >>>> Lee,
> >>>>
> >>>> On Wed, May 13, 2015 at 7:39 AM, Lee Jones <lee.jones@linaro.org> wrote:
> >>>>> On Mon, 04 May 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 <abrestic@chromium.org>
> >>>>>> Cc: Rob Herring <robh+dt@kernel.org>
> >>>>>> Cc: Pawel Moll <pawel.moll@arm.com>
> >>>>>> Cc: Mark Rutland <mark.rutland@arm.com>
> >>>>>> Cc: Ian Campbell <ijc+devicetree@hellion.org.uk>
> >>>>>> Cc: Kumar Gala <galak@codeaurora.org>
> >>>>>> Cc: Samuel Ortiz <sameo@linux.intel.com>
> >>>>>> Cc: Lee Jones <lee.jones@linaro.org>
> >>>>>> ---
> >>>>>> Changes from v7:
> >>>>>>  - Move non-shared resources into child nodes.
> >>>>>> New for v7.
> >>>>>> ---
> >>>>>>  .../bindings/mfd/nvidia,tegra124-xusb.txt          | 37 ++++++++++++++++++++++
> >>>>>>  1 file changed, 37 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..bc50110
> >>>>>> --- /dev/null
> >>>>>> +++ b/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt
> >>>>>> @@ -0,0 +1,37 @@
> >>>>>> +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,<chip>-xusb", "nvidia,tegra124-xusb"'
> >>>>>> +   where <chip> is tegra132.
> >>>>>> + - reg: Must contain the base and length of the XUSB FPCI registers.
> >>>>>> + - ranges: Bus address mapping for the XUSB block.  Can be empty since the
> >>>>>> +   mapping is 1:1.
> >>>>>> + - #address-cells: Must be 2.
> >>>>>> + - #size-cells: Must be 2.
> >>>>>> +
> >>>>>> +Example:
> >>>>>> +--------
> >>>>>> +     usb at 0,70098000 {
> >>>>>> +             compatible = "nvidia,tegra124-xusb";
> >>>>>> +             reg = <0x0 0x70098000 0x0 0x1000>;
> >>>>>> +             ranges;
> >>>>>> +
> >>>>>> +             #address-cells = <2>;
> >>>>>> +             #size-cells = <2>;
> >>>>>> +
> >>>>>> +             usb-host at 0,70090000 {
> >>>>>> +                     compatible = "nvidia,tegra124-xhci";
> >>>>>> +                     ...
> >>>>>> +             };
> >>>>>> +
> >>>>>> +             mailbox {
> >>>>>> +                     compatible = "nvidia,tegra124-xusb-mbox";
> >>>>>> +                     ...
> >>>>>> +             };
> >>>>>
> >>>>> This doesn't appear to be a proper MFD.  I would have the USB and
> >>>>> Mailbox devices probe seperately and use a phandle to point the USB
> >>>>> device to its Mailbox.
> >>>>>
> >>>>> usb at xyz {
> >>>>>         mboxes = <&xusb-mailbox, [chan]>;
> >>>>> };
> >>>>
> >>>> Then what will set up the shared regmap?  The point of using an MFD
> >>>> here was to share a register set with both the mailbox and xHCI
> >>>> drivers and avoid having to map the same register set twice in two
> >>>> separate drivers.
> >>>
> >>> Can you share the mapping please?
> >>
> >> What do you mean?  That's what the MFD is doing now by setting up an
> >> MMIO regmap to be shared between the two devices.
> > 
> > I mean, can you share the documentation with me. :)
> 
> You can download the documentation from here [1]. See chapter 19 USB
> complex. However, I will warn you that unfortunately, you need to sign
> up for an account :-(

I'll give that a miss for the time being.  See my other mail for now.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2015-05-14  7:45 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-04 17:36 [PATCH v8 0/9] Tegra xHCI support Andrew Bresticker
2015-05-04 17:36 ` [PATCH v8 1/9] xhci: Set shared HCD's hcd_priv in xhci_gen_setup Andrew Bresticker
2015-05-19 18:39   ` Andrew Bresticker
2015-05-22 12:19     ` Mathias Nyman
2015-05-04 17:36 ` [PATCH v8 2/9] mailbox: Make mbox_chan_ops const Andrew Bresticker
2015-05-04 19:22   ` Suman Anna
2015-05-04 17:36 ` [PATCH v8 3/9] mailbox: Fix up error handling in mbox_request_channel() Andrew Bresticker
2015-05-04 17:36 ` [PATCH v8 4/9] mfd: Add binding document for NVIDIA Tegra XUSB Andrew Bresticker
2015-05-13 14:39   ` Lee Jones
2015-05-13 16:26     ` Andrew Bresticker
2015-05-13 16:50       ` Lee Jones
2015-05-13 17:03         ` Andrew Bresticker
2015-05-14  7:29           ` Lee Jones
2015-05-14  7:32             ` Jon Hunter
2015-05-14  7:45               ` Lee Jones [this message]
2015-05-14  7:20     ` Jon Hunter
2015-05-14  7:40       ` Lee Jones
2015-05-14  9:14         ` Jon Hunter
2015-05-14  9:30           ` Lee Jones
2015-05-14 10:09             ` Jon Hunter
2015-05-14 10:23               ` Lee Jones
2015-05-14 11:21                 ` Jon Hunter
2015-05-14 17:38         ` Andrew Bresticker
2015-05-19 18:36           ` Andrew Bresticker
2015-05-20  6:35             ` Lee Jones
2015-05-20 14:52               ` Thierry Reding
2015-05-21  7:19                 ` Linus Walleij
2015-05-21  8:40                 ` Lee Jones
2015-05-21 10:12                   ` Thierry Reding
2015-05-26 15:18                     ` Lee Jones
2015-06-30 18:22                       ` Grant Likely
2015-05-04 17:36 ` [PATCH v8 5/9] mfd: Add driver " Andrew Bresticker
2015-05-13 14:37   ` Lee Jones
2015-05-13 16:31     ` Andrew Bresticker
2015-05-04 17:36 ` [PATCH v8 6/9] mailbox: Add NVIDIA Tegra XUSB mailbox binding Andrew Bresticker
2015-05-08 20:42   ` Benson Leung
2015-05-08 20:53     ` Andrew Bresticker
2015-05-08 21:03       ` Benson Leung
2015-05-04 17:36 ` [PATCH v8 7/9] mailbox: Add NVIDIA Tegra XUSB mailbox driver Andrew Bresticker
2015-05-04 17:36 ` [PATCH v8 8/9] usb: Add NVIDIA Tegra xHCI controller binding Andrew Bresticker
2015-05-04 17:36 ` [PATCH v8 9/9] usb: xhci: Add NVIDIA Tegra xHCI host-controller driver Andrew Bresticker
2015-05-05 14:28 ` [PATCH v8 0/9] Tegra xHCI support Jon Hunter
2015-05-05 14:42   ` Thierry Reding
2015-05-05 14:57     ` Jon Hunter
2015-05-12  3:56 ` Jassi Brar
2015-05-26 16:27   ` Andrew Bresticker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150514074504.GB22418@x1 \
    --to=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).