From: Felipe Balbi <balbi@kernel.org>
To: bugzilla-daemon@bugzilla.kernel.org, linux-usb@vger.kernel.org,
Alexandre Torgue <alexandre.torgue@st.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>
Subject: Re: [Bug 206435] dwc3 dwc3.3.auto: no usb2 phy configured
Date: Thu, 06 Feb 2020 20:33:16 +0200 [thread overview]
Message-ID: <87a75v5zwz.fsf@kernel.org> (raw)
In-Reply-To: <87d0ar5zyq.fsf@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 803 bytes --]
+ Heikki, since this is, apparently, Bay Trail
Felipe Balbi <balbi@kernel.org> writes:
> Hi,
>
> bugzilla-daemon@bugzilla.kernel.org writes:
>> https://bugzilla.kernel.org/show_bug.cgi?id=206435
>>
>> --- Comment #3 from youling257@gmail.com ---
>> Revert 987351e1ea7772cf2f0795e917fb33b2e282e1c1 phy: core: Add consumer device
>> link support, dwc3 work for my z3735f device.
>>
>> android_x86:/ $ su
>> android_x86:/ # dmesg | grep dwc
>> [ 9.724606] dwc3 dwc3.3.auto: changing max_speed on rev 5533210a
>> [ 47.488501] udc dwc3.3.auto: registering UDC driver [g1]
>
> reverting that commit makes dwc3 work? Then you don't have a bug on
> dwc3. You have a regression caused by another commit.
>
> Alexandre, any idea what's going on?
Heikki, any ideas?
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-02-06 18:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 20:09 [Bug 206435] New: dwc3 dwc3.3.auto: no usb2 phy configured bugzilla-daemon
2020-02-05 20:16 ` [Bug 206435] " bugzilla-daemon
2020-02-06 6:24 ` Felipe Balbi
2020-02-06 6:25 ` bugzilla-daemon
2020-02-06 12:47 ` bugzilla-daemon
2020-02-06 18:32 ` Felipe Balbi
2020-02-06 18:33 ` Felipe Balbi [this message]
2020-02-07 8:52 ` Alexandre Torgue
2020-02-06 18:32 ` bugzilla-daemon
2020-02-06 18:33 ` bugzilla-daemon
2020-02-06 19:25 ` bugzilla-daemon
2020-02-07 8:52 ` bugzilla-daemon
2020-02-07 12:19 ` bugzilla-daemon
2020-02-13 22:15 ` bugzilla-daemon
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=87a75v5zwz.fsf@kernel.org \
--to=balbi@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-usb@vger.kernel.org \
/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).