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
Date: Thu, 15 Nov 2018 10:09:05 +0200 [thread overview]
Message-ID: <87efbm92zi.fsf@linux.intel.com> (raw)
In-Reply-To: <606dbc68-2014-8590-ce47-83c175d4cd41@linaro.org>
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
next prev parent reply other threads:[~2018-11-15 8:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 10:38 [PATCH v2] usb: dwc3: core: Fix ULPI PHYs and prevent phy_get/ulpi_init during suspend/resume Roger Quadros
2018-02-12 8:45 ` Felipe Balbi
2018-02-12 13:30 ` [PATCH v2 RESEND] " Roger Quadros
2018-11-14 16:11 ` Todor Tomov
2018-11-15 8:09 ` Felipe Balbi [this message]
2018-11-16 17:01 ` Todor Tomov
2018-11-26 8:27 ` Todor Tomov
2018-11-26 17:14 ` Todor Tomov
2018-11-27 8:59 ` Felipe Balbi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87efbm92zi.fsf@linux.intel.com \
--to=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rogerq@ti.com \
--cc=stable@vger.kernel.org \
--cc=todor.tomov@linaro.org \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).