Hello Inki,
On 11/20/2015 07:59 AM, Inki Dae wrote:
Hi Javier,
2015년 11월 20일 00:51에 Javier Martinez Canillas 이(가) 쓴 글:
On 11/19/2015 11:55 AM, Javier Martinez Canillas wrote:
This series causes a boot failure on at least an Exynos5800 Peach Pi Chromebook (tested myself) and seems to be the cause of other Exynos boards failing to boot: http://kernelci.org/boot/?exynos&fail
[snip]
drm/exynos: add pm_runtime to Mixer drm/exynos: add pm_runtime to FIMD
I had to revert these patches in order to get the machine in a bootable state again, the sha1 hash for these patches in next-20151119 are:
045febd5f813 drm/exynos: add pm_runtime to FIMD
On a closer look, only reverting the FIMD patch is enough to make at least the Exynos5800 Peach Pi to boot again.
Thanks for report.
Thanks to you for the quick answer and providing a fix.
I assume that the issue is because above patch removed 'suspended' variable for checking the suspend status in runtime so I revived it.
It seems your assumption was correct...
I'm not sure that the change could resolve the issue. Could you test it with the change again? I have no Exynos5800 Peach Pi board. :(
For this, I pushed it to below exynos-drm/for-next branch, https://git.kernel.org/cgit/linux/kernel/git/daeinki/drm-exynos.git/commit/?...
If the issue is resolved by the change then I will modify other patches for DECON series. And if really so, there may be a corner case we missed.
... since I reverted the offending commit and cherry-picked the one in your for-next branch and the machine booted again.
Thanks, Inki Dae
Best regards,