[PATCH] drm/exynos/fimc: fix runtime pm support

2015-08-06 Thread Inki Dae
On 2015년 08월 06일 19:13, Marek Szyprowski wrote: > Hello, > > On 2015-04-09 10:46, Marek Szyprowski wrote: >> Once pm_runtime_set_active() gets called, the kernel assumes that given >> device has already enabled runtime pm and will call pm_runtime_suspend() >> without matching

[PATCH] drm/exynos/fimc: fix runtime pm support

2015-08-06 Thread Marek Szyprowski
Hello, On 2015-04-09 10:46, Marek Szyprowski wrote: > Once pm_runtime_set_active() gets called, the kernel assumes that given > device has already enabled runtime pm and will call pm_runtime_suspend() > without matching pm_runtime_resume(). In case of DRM FIMC IPP driver, > this will result in

[PATCH] drm/exynos/fimc: fix runtime pm support

2015-07-12 Thread Tobias Jakobi
Hello, looks like this patch was forgotten. At least I can't find it in 4.2-rc1. With best wishes, Tobias Marek Szyprowski wrote: > Once pm_runtime_set_active() gets called, the kernel assumes that given > device has already enabled runtime pm and will call pm_runtime_suspend() > without

[PATCH] drm/exynos/fimc: fix runtime pm support

2015-04-09 Thread Marek Szyprowski
Once pm_runtime_set_active() gets called, the kernel assumes that given device has already enabled runtime pm and will call pm_runtime_suspend() without matching pm_runtime_resume(). In case of DRM FIMC IPP driver, this will result in calling clk_disable() without respective call to clk_enable().