From: Jon Hunter <jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>, Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>, Alexandre Courbot <gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, Jon Hunter <jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> Subject: [PATCH 1/3] dt-bindings: phy: Fix description of Tegra210 PHY nodes Date: Wed, 29 Jun 2016 12:07:31 +0100 [thread overview] Message-ID: <1467198453-23406-2-git-send-email-jonathanh@nvidia.com> (raw) In-Reply-To: <1467198453-23406-1-git-send-email-jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> 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-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> --- Documentation/devicetree/bindings/phy/nvidia,tegra124-xusb-padctl.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/phy/nvidia,tegra124-xusb-padctl.txt b/Documentation/devicetree/bindings/phy/nvidia,tegra124-xusb-padctl.txt index 0bf1ae243552..3742c152c467 100644 --- a/Documentation/devicetree/bindings/phy/nvidia,tegra124-xusb-padctl.txt +++ b/Documentation/devicetree/bindings/phy/nvidia,tegra124-xusb-padctl.txt @@ -124,7 +124,7 @@ For Tegra124 and Tegra132, the list of valid PHY nodes is given below: - functions: "usb3-ss", "sata" For Tegra210, the list of valid PHY nodes is given below: -- utmi: utmi-0, utmi-1, utmi-2, utmi-3 +- usb2: usb2-0, usb2-1, usb2-2, usb2-3 - functions: "snps", "xusb", "uart" - hsic: hsic-0, hsic-1 - functions: "snps", "xusb" -- 2.1.4
WARNING: multiple messages have this Message-ID (diff)
From: jonathanh@nvidia.com (Jon Hunter) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 1/3] dt-bindings: phy: Fix description of Tegra210 PHY nodes Date: Wed, 29 Jun 2016 12:07:31 +0100 [thread overview] Message-ID: <1467198453-23406-2-git-send-email-jonathanh@nvidia.com> (raw) In-Reply-To: <1467198453-23406-1-git-send-email-jonathanh@nvidia.com> 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(-) diff --git a/Documentation/devicetree/bindings/phy/nvidia,tegra124-xusb-padctl.txt b/Documentation/devicetree/bindings/phy/nvidia,tegra124-xusb-padctl.txt index 0bf1ae243552..3742c152c467 100644 --- a/Documentation/devicetree/bindings/phy/nvidia,tegra124-xusb-padctl.txt +++ b/Documentation/devicetree/bindings/phy/nvidia,tegra124-xusb-padctl.txt @@ -124,7 +124,7 @@ For Tegra124 and Tegra132, the list of valid PHY nodes is given below: - functions: "usb3-ss", "sata" For Tegra210, the list of valid PHY nodes is given below: -- utmi: utmi-0, utmi-1, utmi-2, utmi-3 +- usb2: usb2-0, usb2-1, usb2-2, usb2-3 - functions: "snps", "xusb", "uart" - hsic: hsic-0, hsic-1 - functions: "snps", "xusb" -- 2.1.4
next prev parent reply other threads:[~2016-06-29 11:07 UTC|newest] Thread overview: 12+ 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 ` Jon Hunter [not found] ` <1467198453-23406-1-git-send-email-jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> 2016-06-29 11:07 ` Jon Hunter [this message] 2016-06-29 11:07 ` [PATCH 1/3] dt-bindings: phy: Fix description of Tegra210 PHY nodes Jon Hunter [not found] ` <1467198453-23406-2-git-send-email-jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> 2016-07-01 1:41 ` Rob Herring 2016-07-01 1:41 ` Rob Herring 2016-06-29 11:07 ` [PATCH 2/3] dt-bindings: usb: Fix Tegra XUSB example Jon Hunter 2016-06-29 11:07 ` Jon Hunter 2016-06-29 11:07 ` [PATCH 3/3] arm64: tegra: Correct Tegra210 XUSB mailbox interrupt Jon Hunter 2016-06-29 11:07 ` Jon Hunter 2016-06-30 9:30 ` [PATCH 0/3] Fixes for Tegra XUSB Thierry Reding 2016-06-30 9:30 ` 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=1467198453-23406-2-git-send-email-jonathanh@nvidia.com \ --to=jonathanh-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \ --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \ --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \ --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \ --cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.