summaryrefslogtreecommitdiffstats
path: root/Documentation/devicetree/bindings/phy/rockchip-usb-phy.txt
diff options
context:
space:
mode:
authorRafał Miłecki <rafal@milecki.pl>2017-04-02 18:55:22 +0200
committerKishon Vijay Abraham I <kishon@ti.com>2017-04-10 16:43:41 +0530
commitfff3364a637796611c06f59a6f2be61685d99bfe (patch)
treeec19ad14ab015035fbcba0049f2e013300e6f539 /Documentation/devicetree/bindings/phy/rockchip-usb-phy.txt
parente78f3d15e115e8e764d4b1562b4fa538f2e22f6b (diff)
downloadop-kernel-dev-fff3364a637796611c06f59a6f2be61685d99bfe.zip
op-kernel-dev-fff3364a637796611c06f59a6f2be61685d99bfe.tar.gz
phy: bcm-ns-usb3: split all writes into reg & val pairs
So far all the PHY initialization was implemented using some totally magic values. There was some pattern there but it wasn't clear what is it about. Thanks to the patch submitted by Broadcom: [PATCH 5/6] phy: Add USB3 PHY support for Broadcom NSP SoC and the upstream "iproc-mdio" driver we now know there is a MDIO bus underneath with PHY(s) and their registers. It allows us to clean the driver a bit by making all these values less magical. The next step is switching to using a proper MDIO layer. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> Acked-by: Jon Mason <jon.mason@broadcom.com> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
Diffstat (limited to 'Documentation/devicetree/bindings/phy/rockchip-usb-phy.txt')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud