devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Andrew Bresticker <abrestic@chromium.org>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Jassi Brar <jassisinghbrar@gmail.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Mathias Nyman <mathias.nyman@intel.com>,
	Grant Likely <grant.likely@linaro.org>,
	Alan Stern <stern@rowland.harvard.edu>,
	Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	Felipe Balbi <balbi@ti.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org"
	<linux-kernel@vger.kernel.org>"linux-arm-kernel@lists.infradead.org"
	<linux>
Subject: Re: [PATCH V6 00/12] Tegra xHCI support
Date: Wed, 25 Feb 2015 22:15:45 +0100	[thread overview]
Message-ID: <20150225211539.GA7884@mithrandir> (raw)
In-Reply-To: <CAL1qeaEmSphLd=k3f6865OEO_rcwO3+Hv5KDvCN2_=7nDdZJzA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2233 bytes --]

On Wed, Feb 25, 2015 at 09:27:36AM -0800, Andrew Bresticker wrote:
> Hi Thierry,
> 
> > Sorry for taking so awfully long to look at this. I've spent some time
> > looking at various pieces of documentation and I concluded that
> > representing the port assignment as muxing options doesn't seem right
> > after all. Instead I've come up with an alternate proposal (attached).
> > Could you take a look and see if that sounds reasonable to you?
> 
> Thanks for taking a look at this.  I've been meaning to pick this
> series back up, but haven't had quite enough bandwidth lately.
> 
> This all looks good to me, just one comment below:
> 
> > +PHY nodes:
> > +----------
> > +
> > +An optional child node named "phys" can contain nodes describing additional
> > +properties of each PHY. Only USB3 and UTMI PHYs can be complemented in this
> > +way, in which case the name of each node must match one of the following:
> > +
> > +  usb3-0, usb3-1, utmi-0, utmi-1, utmi-2
> > +
> > +Required properties for USB3 PHYs:
> > +- nvidia,lanes: specifies the name of the lane that this USB3 PHY uses
> > +- nvidia,port: specifies the number of the USB2 port that is used for this
> > +  USB3 PHY
> > +
> > +Optional properties for UTMI PHYs:
> > +- vbus-supply: regulator providing the VBUS voltage for the UTMI pad
> 
> What about the HSIC PHYs?  Shouldn't they be represented as PHY nodes as well?

Yes, they could. The PCIe and SATA PHYs could as well. I haven't
included them because they currently don't take any properties. In
addition to that, perhaps some of the nvidia,hsic-* properties could be
moved into the PHY nodes, too. But they're also properties of the pin,
so keeping them in the pinmux nodes seems fine as well.

On a slightly different topic, I've been trying to wrap my head around
the use of the nvidia,port property and my conclusion was that in fact
one of the physical ports is shared between USB2 and USB3. That is the
utmi-2 PHY and usb3-0 PHY go to the very same port. The vbus-supply
specified in the Jetson TK1 DTS would support that (it's associated with
utmi-2 but named vdd_usb3_reg, and the USB3 port doesn't work without
it). Can you confirm that?

Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-02-25 21:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25  0:17 [PATCH V6 00/12] Tegra xHCI support Andrew Bresticker
2014-11-25  0:17 ` [PATCH V6 01/12] xhci: Set shared HCD's hcd_priv in xhci_gen_setup Andrew Bresticker
2014-11-25  0:17 ` [PATCH V6 02/12] mailbox: Make struct mbox_controller's ops field const Andrew Bresticker
2014-11-25  0:17 ` [PATCH V6 03/12] mailbox: Fix up error handling in mbox_request_channel() Andrew Bresticker
     [not found] ` <1416874644-12070-1-git-send-email-abrestic-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2014-11-25  0:17   ` [PATCH V6 04/12] of: Add NVIDIA Tegra XUSB mailbox binding Andrew Bresticker
2014-11-25  0:17   ` [PATCH V6 06/12] of: Update Tegra XUSB pad controller binding for USB Andrew Bresticker
2014-11-25  0:17   ` [PATCH V6 07/12] pinctrl: tegra-xusb: Add USB PHY support Andrew Bresticker
     [not found]     ` <1416874644-12070-8-git-send-email-abrestic-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2014-11-25 13:49       ` Kishon Vijay Abraham I
     [not found]         ` <547488EB.2040507-l0cyMroinI0@public.gmane.org>
2014-11-26 19:41           ` Andrew Bresticker
2014-11-25  0:17   ` [PATCH V6 08/12] of: Add NVIDIA Tegra xHCI controller binding Andrew Bresticker
2014-11-25 13:32   ` [PATCH V6 00/12] Tegra xHCI support Jassi Brar
     [not found]     ` <CAJe_Zhcz=WOLy0_98xRj6=i2+5MFeXQGPmYJhnpy1NfUEPJ-0w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-26 19:31       ` Andrew Bresticker
2014-11-25  0:17 ` [PATCH V6 05/12] mailbox: Add NVIDIA Tegra XUSB mailbox driver Andrew Bresticker
     [not found]   ` <1416874644-12070-6-git-send-email-abrestic-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2014-12-02  9:47     ` Thierry Reding
2014-12-02 19:06       ` Andrew Bresticker
2014-11-25  0:17 ` [PATCH V6 09/12] usb: xhci: Add NVIDIA Tegra xHCI host-controller driver Andrew Bresticker
2014-11-25  0:17 ` [PATCH V6 10/12] ARM: tegra: jetson-tk1: Add xHCI support Andrew Bresticker
2014-11-25  0:17 ` [PATCH V6 11/12] ARM: tegra: Add Tegra124 XUSB mailbox and xHCI controller Andrew Bresticker
2014-11-25  0:17 ` [PATCH V6 12/12] ARM: tegra: venice2: Add xHCI support Andrew Bresticker
2015-02-25 16:01 ` [PATCH V6 00/12] Tegra " Thierry Reding
2015-02-25 17:27   ` Andrew Bresticker
2015-02-25 21:15     ` Thierry Reding [this message]
2015-02-25 21:20       ` 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=20150225211539.GA7884@mithrandir \
    --to=thierry.reding@gmail.com \
    --cc=abrestic@chromium.org \
    --cc=arnd@arndb.de \
    --cc=balbi@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=gnurou@gmail.com \
    --cc=grant.likely@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=jassisinghbrar@gmail.com \
    --cc=kishon@ti.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathias.nyman@intel.com \
    --cc=olof@lixom.net \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=swarren@wwwdotorg.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).