Commit 6b57560e authored Jun 06, 2016 by Mayank Rana

ARM: dts: mdm: Use qcom,qusb-phy-init-seq with QUSB PHY on mdm9640



QUSB PHY driver only has support to use qcom,qusb-phy-init-seq based
initialization sequence on msm-3.18 kernel whereas current mdm9640
dtsi is using qcom,qusb-tune which is only supported on msm-3.10 kernel.
Due to this, QUSB PHY is not initialized as expected. This results into
multiple USB enumeration and data stall issues in USB high-speed mode.
Fix those issues by using qcom,qusb-phy-init-seq with required
<value, offset> pairs as initialization sequence.

CRs-Fixed: 1025088
Change-Id: I339ceeb4d484abf261012549e0b04d56cac3ffd3
Signed-off-by: Mayank Rana <mrana@codeaurora.org>

parent 64e14aa3

arch/arm/boot/dts/qcom/mdm9640.dtsi

+6 −1

Original line number	Diff line number	Diff line
		@@ -1130,7 +1130,12 @@
		vdda18-supply = <&pmd9635_l8>;
		vdda33-supply = <&pmd9635_l10>;
		qcom,vdd-voltage-level = <0 1000000 1000000>;
		qcom,qusb-tune = <0xa06393d5>;
		qcom,qusb-phy-init-seq =
		/* <value reg_offset> */
		<0xa0 0x80 /* Tune1 */
		0x63 0x84 /* Tune2 */
		0x93 0x88 /* Tune3 */
		0xd5 0x8c>; /* Tune4 */
		phy_type = "utmi";

		clocks = <&clock_gcc clk_ln_bb_clk>,