On 01/26/2017 07:34 AM, Kishon Vijay Abraham I wrote: > > > On Tuesday 17 January 2017 09:44 PM, Yendapally Reddy Dhananjaya Reddy wrote: >> This patch set contains the usb support for Broadcom NSP SoC. The >> usb3 phy is internal to the SoC and is accessed through mdio interface. >> The mdio interface can be used to access either internal usb3 phy or >> external ethernet phy using a multiplexer. >> >> The first patch provides the documentation details for usb3 phy. The >> second patch provides the changes to the mdio bus driver. The third >> patch provides the phy driver and fourth patch provides the enable >> method for usb. > > merged the 1st and 4th patch to linux-phy. You mean 1st and 3rd here, right? 4th is a Device Tree change that I should take, and Patch 2 should be merged by David. What branch in your tree should we be looking at? > > Thanks > Kishon > >> >> This patch series has been tested on NSP bcm958625HR board. >> This patch series is based on v4.10.0-rc3 and is available from >> github-repo: https://github.com/Broadcom/cygnus-linux.git >> branch:nsp-usb-v2 >> >> Changes in v2: >> * Remove separate nsp mux driver as suggested by Andrew Lunn >> * Addressed comments from Scott and Rob >> >> Yendapally Reddy Dhananjaya Reddy (4): >> dt-bindings: phy: Add documentation for NSP USB3 PHY >> net: phy: Initialize mdio clock at probe function >> phy: Add USB3 PHY support for Broadcom NSP SoC >> arm: dts: nsp: Add USB nodes to device tree >> >> .../devicetree/bindings/phy/brcm,nsp-usb3-phy.txt | 39 +++++ >> arch/arm/boot/dts/bcm-nsp.dtsi | 56 +++++++ >> arch/arm/boot/dts/bcm958625k.dts | 16 ++ >> drivers/net/phy/mdio-bcm-iproc.c | 6 +- >> drivers/phy/Kconfig | 8 + >> drivers/phy/Makefile | 1 + >> drivers/phy/phy-bcm-nsp-usb3.c | 176 +++++++++++++++++++++ >> 7 files changed, 298 insertions(+), 4 deletions(-) >> create mode 100644 Documentation/devicetree/bindings/phy/brcm,nsp-usb3-phy.txt >> create mode 100644 drivers/phy/phy-bcm-nsp-usb3.c >> -- Florian -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
