https://bugzilla.kernel.org/show_bug.cgi?id=206435 --- Comment #7 from alexandre.torgue@xxxxxx --- Hi Felipe, On 2/6/20 7:33 PM, Felipe Balbi wrote: > > + Heikki, since this is, apparently, Bay Trail > > Felipe Balbi <balbi@xxxxxxxxxx> writes: > >> Hi, >> >> bugzilla-daemon@xxxxxxxxxxxxxxxxxxx writes: >>> https://bugzilla.kernel.org/show_bug.cgi?id=206435 >>> >>> --- Comment #3 from youling257@xxxxxxxxx --- >>> 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? > It's probably due to error returned by "device_link-add" function called in phy-get (phy-core.c). Maybe because phy dev is not present. I wonder if we should update device_link_add error management in phy-get (if link add fails it's maybe not a reason to make the consumer probe fail) regards Alex > Heikki, any ideas? > -- You are receiving this mail because: You are watching the assignee of the bug.
