aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/phy/broadcom/phy-bcm-ns-usb3.c
diff options
context:
space:
mode:
authorRafał Miłecki <rafal@milecki.pl>2017-06-08 22:04:27 +0200
committerKishon Vijay Abraham I <kishon@ti.com>2017-06-16 13:22:26 +0530
commit91699e98f19a392dc59defd0731a0434f842f9d4 (patch)
tree25c8d5a072aab85032914bfe1e2a75982cef8a97 /drivers/phy/broadcom/phy-bcm-ns-usb3.c
parentphy: bcm-ns-usb3: enable MDIO in the platform specific code (diff)
downloadlinux-dev-91699e98f19a392dc59defd0731a0434f842f9d4.tar.xz
linux-dev-91699e98f19a392dc59defd0731a0434f842f9d4.zip
dt-bindings: phy: Modify Broadcom NS USB 3.0 PHY binding to use MDIO
Thanks to work done by Broadcom explaining their USB 3.0 PHY details we know it's attached to the MDIO bus. Use this knowledge to update the binding: make it a subnode to the MDIO bus and rework way of specifying required registers. This will describe hardware more precisely and will allow to support (describe) more devices attached to the MDIO. While compatibility strings remain the same there isn't a direct conflict (compatibility breakage) for the binding. Originally it wasn't supposed to be used for MDIO subnode so this change should be safe unless some operating system was probing MDIO subnodes as standalone devices. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> Acked-by: Rob Herring <robh@kernel.org> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
Diffstat (limited to 'drivers/phy/broadcom/phy-bcm-ns-usb3.c')
0 files changed, 0 insertions, 0 deletions