From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] dt-bindings: phy: Fix description of Tegra210 PHY nodes
Date: Thu, 30 Jun 2016 20:41:34 -0500 [thread overview]
Message-ID: <20160701014134.GA26253@rob-hp-laptop> (raw)
In-Reply-To: <1467198453-23406-2-git-send-email-jonathanh@nvidia.com>
On Wed, Jun 29, 2016 at 12:07:31PM +0100, Jon Hunter wrote:
> The dt-binding document for the Tegra XUSB pad controller states that
> 'utmi' is one of the valid choices for the Tegra210 PHY node names and
> has child lanes named, 'utmi-0', 'utmi-1', 'utmi-2' and 'utmi-3'.
> However, neither the XUSB pad controller PHY driver or the actual
> Tegra210 binding for the XUSB pad controller use these names. Instead
> both the driver and binding use the node name 'usb2' and for the child
> lanes use the names 'usb2-0', 'usb2-1', 'usb2-2' and 'usb2-3'. Given
> that the driver and binding are consistent with the naming, up date the
> dt-binding documentation to match.
>
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> ---
> Documentation/devicetree/bindings/phy/nvidia,tegra124-xusb-padctl.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2016-07-01 1:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 11:07 [PATCH 0/3] Fixes for Tegra XUSB Jon Hunter
2016-06-29 11:07 ` [PATCH 1/3] dt-bindings: phy: Fix description of Tegra210 PHY nodes Jon Hunter
2016-07-01 1:41 ` Rob Herring [this message]
2016-06-29 11:07 ` [PATCH 2/3] dt-bindings: usb: Fix Tegra XUSB example Jon Hunter
2016-06-29 11:07 ` [PATCH 3/3] arm64: tegra: Correct Tegra210 XUSB mailbox interrupt Jon Hunter
2016-06-30 9:30 ` [PATCH 0/3] Fixes for Tegra XUSB Thierry Reding
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=20160701014134.GA26253@rob-hp-laptop \
--to=robh@kernel.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