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
When using eDP with orangepi-3b and orangepi-cm4 the board cannot shutdown or restart. The eDP panel works fantastic and without any issues when using the board. However, the board cannot shutdown or restart. Some config or driver is causing the board CPU to stall. I will include the logs and config I am using:
I tested on Ubuntu, Debian and OrangepiOS (arch) version images. I also tried with manually compiled legacy kernel myself but same issue. I tested with 3b and cm4 board also but same issue.
eDP dts overlay. for using boe,nv126b5m-n42 panel:
I am assuming that rockchip drm driver is requesting from analogix to read the hpd status pin before shutting down the display but it seems like the gpio for the hpd has been disabled by some other process causing the rockchip_gpio_irq error?
The text was updated successfully, but these errors were encountered:
When using eDP with orangepi-3b and orangepi-cm4 the board cannot shutdown or restart. The eDP panel works fantastic and without any issues when using the board. However, the board cannot shutdown or restart. Some config or driver is causing the board CPU to stall. I will include the logs and config I am using:
Board and OS information (uname -a):
I tested on Ubuntu, Debian and OrangepiOS (arch) version images. I also tried with manually compiled legacy kernel myself but same issue. I tested with 3b and cm4 board also but same issue.
eDP dts overlay. for using boe,nv126b5m-n42 panel:
After shutting down the board the error log is shown like below:
Based on the following errors:
I am assuming that rockchip drm driver is requesting from analogix to read the hpd status pin before shutting down the display but it seems like the gpio for the hpd has been disabled by some other process causing the rockchip_gpio_irq error?
The text was updated successfully, but these errors were encountered: