Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Felipe Balbi <balbi@kernel.org>
To:     Todor Tomov <todor.tomov@linaro.org>,
        Roger Quadros <rogerq@ti.com>, linux-usb@vger.kernel.org
Cc:     vigneshr@ti.com, gregkh@linuxfoundation.org,
        linux-kernel@vger.kernel.org,
        "linux-stable # \= v4 . 13" <stable@vger.kernel.org>
Subject: Re: [PATCH v2 RESEND] usb: dwc3: core: Fix ULPI PHYs and prevent phy_get/ulpi_init during suspend/resume
In-Reply-To: <606dbc68-2014-8590-ce47-83c175d4cd41@linaro.org>
References: <1515667087-4110-1-git-send-email-rogerq@ti.com> <ee73347b-e996-4052-6a9d-dd94edd4a61a@ti.com> <606dbc68-2014-8590-ce47-83c175d4cd41@linaro.org>
Date:   Thu, 15 Nov 2018 10:09:05 +0200
Message-ID: <87efbm92zi.fsf@linux.intel.com>
MIME-Version: 1.0
Content-Type: text/plain
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


Hi,

Todor Tomov <todor.tomov@linaro.org> writes:

> Hello,
>
> After I apply this patch on 4.14 (or receive it with 4.14.70) I see a regression with
> the Qualcomm QUSB2 phy driver. I'm testing on a Dragonboard 820c.
> In boot log I get:
>
> [    4.525502] phy phy-7412000.phy.6: QUSB2PHY pll lock failed: status reg = 0
> [    4.529232] phy phy-7412000.phy.6: phy init failed --> -16
> [    4.536170] dwc3 7600000.dwc3: failed to initialize core
> [    4.541743] dwc3: probe of 7600000.dwc3 failed with error -16
> [    4.549979] phy phy-7411000.phy.5: QUSB2PHY pll lock failed: status reg = 0
> [    4.552843] phy phy-7411000.phy.5: phy init failed --> -16
> [    4.559606] dwc3 6a00000.dwc3: failed to initialize core
> [    4.565181] dwc3: probe of 6a00000.dwc3 failed with error -16
>
> I can provide a full log if needed.

please do. Also, try mainline and let us know if the problem
persists. Why do you get -EBUSY from the PHY driver?

- 
balbi