-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CM4 Lite freeze during s2idle (USB pmdomain powered down) #6537
Comments
Okay, it seems that i solved the mystery behind this issue. I added more debug messages in order to see what's going on:
So the issue occurs during resume and it seems the VC4 firmware crashes, because all firmware tags run into a timeout. After a lot of trial and error, i had the idea to use the bcm2835-power instead of raspberrypi-power:
and this works :-)
Would still be nice to get a confirmation about the solution. |
During s2idle tests on the CM4 the VPU firmware always crashes on xHCI power-domain resume: root@raspberrypi:/sys/power# echo freeze > state [ 70.724347] xhci_suspend finished [ 70.727730] xhci_plat_suspend finished [ 70.755624] bcm2835-power bcm2835-power: Power grafx off [ 70.761127] USB: Set power to 0 [ 74.653040] USB: Failed to set power to 1 (-110) This seems to be caused because of the mixed usage of raspberrypi-power and bcm2835-power at the same time. So avoid the usage of the VPU firmware power-domain driver, which prevents the crash. Fixes: 522c35e ("ARM: dts: bcm2711: Add BCM2711 xHCI support") Link: raspberrypi/linux#6537 Signed-off-by: Stefan Wahren <[email protected]>
During s2idle tests on the CM4 the VPU firmware always crashes on xHCI power-domain resume: root@raspberrypi:/sys/power# echo freeze > state [ 70.724347] xhci_suspend finished [ 70.727730] xhci_plat_suspend finished [ 70.755624] bcm2835-power bcm2835-power: Power grafx off [ 70.761127] USB: Set power to 0 [ 74.653040] USB: Failed to set power to 1 (-110) This seems to be caused because of the mixed usage of raspberrypi-power and bcm2835-power at the same time. So avoid the usage of the VPU firmware power-domain driver, which prevents the crash. Fixes: 522c35e ("ARM: dts: bcm2711: Add BCM2711 xHCI support") Link: raspberrypi/linux#6537 Signed-off-by: Stefan Wahren <[email protected]>
Describe the bug
Hi,
I took the first steps of s2idle support on CM4 lite (decided against RPi 4 B because of PCIe/VL805 complexity). I got it working for the most critical interfaces so far (Debug UART, USB, HDMI, emmc2, genet). But I needed to make a ugly hack, otherwise the full system freeze/never wake up.
Can you make any sense of it?
Do dwc2 and xhci on BCM2711 share the same power domain?
Here is my current working branch: https://github.com/lategoodbye/linux-dev/commits/v6.13-pm/
Steps to reproduce the behaviour
alternative with PM_TEST enabled:
Device (s)
Raspberry Pi CM4 Lite
System
This is a Mainline kernel 6.13-rc1 with arm64/defconfig as kernel config.
Logs
No response
Additional context
settings in config.txt:
device_tree=bcm2711-rpi-cm4-io.dtb
enable_uart=1
arm_64bit=1
[cm4]
otg_mode=1
The text was updated successfully, but these errors were encountered: