Skip to contentSkip to conversation

New: dwc3 dwc3.3.auto: no usb2 phy configured

Bug 206435 [email protected] 3 participants 14 messages Feb 5, 2020 – Feb 13, 2020 USB

lore
Share & tools
lore

[email protected]

author
#0 lore raw

https://bugzilla.kernel.org/show_bug.cgi?id=206435

            Bug ID: 206435
           Summary: dwc3 dwc3.3.auto: no usb2 phy configured
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.6
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: USB
          Assignee: [email protected]
          Reporter: [email protected]
        Regression: No

android_x86:/ $ dmesg | grep dwc

[    8.956913] dwc3 dwc3.3.auto: failed to create device link to
dwc3.3.auto.ulpi
[    8.979682] dwc3 dwc3.3.auto: no usb2 phy configured
[    8.986984] dwc3 dwc3.3.auto: failed to initialize core: -22
[    8.993597] dwc3: probe of dwc3.3.auto failed with error -22

android_x86:/ $

some Bay trail device has a phy_tusb1210 used for dwc3.

Signature · 2 lines
You are receiving this mail because:
You are watching the assignee of the bug.
author
#3 lore raw

[Bug 206435] dwc3 dwc3.3.auto: no usb2 phy configured

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=206435

--- Comment #2 from Felipe Balbi ([email protected]) --- Hi,

Quoted 5 lines · [email protected] writes:

https://bugzilla.kernel.org/show_bug.cgi?id=206435

--- Comment #1 from [email protected] ---
kernel 5.6 coming soon, test the master branch, dwc3 not work on my z3735f, work on z8350.

What is z3735f and z8350? Are these platforms supported upstream? Who maintains those platforms?

Signature · 2 lines
You are receiving this mail because:
You are watching the assignee of the bug.
author
#4 lore raw

[Bug 206435] dwc3 dwc3.3.auto: no usb2 phy configured

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=206435

--- Comment #3 from [email protected] ---
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]
Signature · 2 lines
You are receiving this mail because:
You are watching the assignee of the bug.
#5 lore raw

Re: [Bug 206435] dwc3 dwc3.3.auto: no usb2 phy configured

Hi,

Quoted 10 lines · [email protected] writes:

https://bugzilla.kernel.org/show_bug.cgi?id=206435

--- Comment #3 from [email protected] ---
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?

Signature · 1 line
balbi
#6 lore raw

Re: [Bug 206435] dwc3 dwc3.3.auto: no usb2 phy configured

+ Heikki, since this is, apparently, Bay Trail

Quoted 14 lines · Felipe Balbi

Hi,

Quoted 10 lines · [email protected] writes:

https://bugzilla.kernel.org/show_bug.cgi?id=206435

--- Comment #3 from [email protected] ---
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]
Quoted 4 lines

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?

Signature · 1 line
balbi
#7 lore raw

Re: [Bug 206435] dwc3 dwc3.3.auto: no usb2 phy configured

Hi Felipe,

Quoted 24 lines · Felipe Balbi

+ Heikki, since this is, apparently, Bay Trail

Quoted 18 lines · Felipe Balbi

Hi,

Quoted 10 lines · [email protected] writes:

https://bugzilla.kernel.org/show_bug.cgi?id=206435

--- Comment #3 from [email protected] ---
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

Quoted 2 lines

Heikki, any ideas?

author
#8 lore raw

[Bug 206435] dwc3 dwc3.3.auto: no usb2 phy configured

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=206435

--- Comment #4 from Felipe Balbi ([email protected]) --- Hi,

Quoted 11 lines · [email protected] writes:

https://bugzilla.kernel.org/show_bug.cgi?id=206435

--- Comment #3 from [email protected] ---
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?

Signature · 2 lines
You are receiving this mail because:
You are watching the assignee of the bug.
author
#9 lore raw

[Bug 206435] dwc3 dwc3.3.auto: no usb2 phy configured

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=206435

--- Comment #5 from Felipe Balbi ([email protected]) ---
+ Heikki, since this is, apparently, Bay Trail

Quoted 15 lines · Felipe Balbi

Hi,

Quoted 11 lines · [email protected] writes:

https://bugzilla.kernel.org/show_bug.cgi?id=206435

--- Comment #3 from [email protected] ---
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]
Quoted 4 lines

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?

Signature · 2 lines
You are receiving this mail because:
You are watching the assignee of the bug.
author
#10 lore raw

[Bug 206435] dwc3 dwc3.3.auto: no usb2 phy configured

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=206435

--- Comment #6 from [email protected] --- /sys/module/dwc3/drivers/platform:dwc3/dwc3.3.auto/dwc3.3.auto.ulpi/driver Symbolic link /sys/module/bus/ulpi/drivers/tusb1210

“phy: core: Add consumer device link support” cause failed to create link.

Signature · 2 lines
You are receiving this mail because:
You are watching the assignee of the bug.
author
#11 lore raw

[Bug 206435] dwc3 dwc3.3.auto: no usb2 phy configured

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=206435

--- Comment #7 from [email protected] ---
Hi Felipe,

Quoted 25 lines · Felipe Balbi

+ Heikki, since this is, apparently, Bay Trail

Quoted 19 lines · Felipe Balbi

Hi,

Quoted 11 lines · [email protected] writes:

https://bugzilla.kernel.org/show_bug.cgi?id=206435

--- Comment #3 from [email protected] ---
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

Quoted 2 lines

Heikki, any ideas?

Signature · 2 lines
You are receiving this mail because:
You are watching the assignee of the bug.
author
#13 lore raw

[Bug 206435] dwc3 dwc3.3.auto: no usb2 phy configured

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=206435

Luca Weiss ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #9 from Luca Weiss ([email protected]) ---
Also happening on msm8974, see e.g.
https://storage.kernelci.org/next/master/next-20200213/arm/qcom_defconfig/gcc-8/lab-bjorn/boot-qcom-msm8974-sony-xperia-castor.html
(msm_hsusb f9a55000.usb: failed to create device link to ci_hdrc.0.ulpi)

Signature · 2 lines
You are receiving this mail because:
You are watching the assignee of the bug.