diff options
author | Jon Hunter <jonathanh@nvidia.com> | 2016-06-29 12:07:31 +0100 |
---|---|---|
committer | Thierry Reding <treding@nvidia.com> | 2016-07-01 14:48:19 +0200 |
commit | 6a6898f6e9486a908ee4481fdb55983945fdbd92 (patch) | |
tree | dc0dbd9e24909ed0203a934beadaf1a39449d6bd /net/openvswitch | |
parent | 1a695a905c18548062509178b98bc91e67510864 (diff) | |
download | talos-obmc-linux-6a6898f6e9486a908ee4481fdb55983945fdbd92.tar.gz talos-obmc-linux-6a6898f6e9486a908ee4481fdb55983945fdbd92.zip |
dt-bindings: phy: Fix description of Tegra210 PHY nodes
The DT bindings 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 bindings 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, update the
DT bindings documentation to match.
Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
Acked-by: Rob Herring <robh@kernel.org>
Signed-off-by: Thierry Reding <treding@nvidia.com>
Diffstat (limited to 'net/openvswitch')
0 files changed, 0 insertions, 0 deletions