You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note for myself / @mripard so I don't forget this.
Testing on Pi4 with HDMI-0 and DPI (HyperPixel4 800x480@60 using #4812) works fine. Plug in HDMI-1 and it fails with flip done timeouts.
2xHDMI + DSI1 (7" touch panel) works fine. DSI1 can be fed from any of the HVS channels though, whereas DPI is channel 0 / output 0 only.
Steps to reproduce the behaviour
Build with 4812.
Add dtoverlay=vc4-kms-dpi-hyperpixel4.
Boot with just HDMI-0 connected and all OK.
Boot with both HDMIs connected and get no display.
Boot with just HDMI-0 and then connect HDMI-1, and HDMI-1 does not come up. At next update it will produce flip timeout.
Device (s)
Raspberry Pi 4 Mod. B
System
Checked on both 5.10.90 and 5.15.15, 32bit kernels.
Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Should be resolved now through #5121. I've certainly had dual DSI and single HDMI0 working.
There was insufficient COB assigned to HVS channel 2, and the interrupt masking was wrong for 2711 leading to the interrupt being disabled by the core.
Describe the bug
Note for myself / @mripard so I don't forget this.
Testing on Pi4 with HDMI-0 and DPI (HyperPixel4 800x480@60 using #4812) works fine. Plug in HDMI-1 and it fails with flip done timeouts.
2xHDMI + DSI1 (7" touch panel) works fine. DSI1 can be fed from any of the HVS channels though, whereas DPI is channel 0 / output 0 only.
Steps to reproduce the behaviour
Build with 4812.
Add dtoverlay=vc4-kms-dpi-hyperpixel4.
Boot with just HDMI-0 connected and all OK.
Boot with both HDMIs connected and get no display.
Boot with just HDMI-0 and then connect HDMI-1, and HDMI-1 does not come up. At next update it will produce flip timeout.
Device (s)
Raspberry Pi 4 Mod. B
System
Checked on both 5.10.90 and 5.15.15, 32bit kernels.
Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: