Thanks Inki,
One more thing. mixer_layer_update is only called on for mixer version;
MXR_VER_16_0_33_0, MXR_VER_128_0_0_184. This condition
should have taken care of Exynos4 scenarios. What you say?
Regards,
Rahul Sharma.
On 24 June 2014 20:20, Inki Dae inki@samsung.com wrote:
2014-06-24
On 2014년 06월 25일 19:42, Rahul Sharma wrote:
Thanks Inki,
One more thing. mixer_layer_update is only called on for mixer version;
MXR_VER_16_0_33_0, MXR_VER_128_0_0_184. This condition
should have taken care of Exynos4 scenarios. What you say?
There was my missing point. :) Already
Am 24.06.2014 07:21, schrieb Inki Dae:
On 2014년 06월 23일 14:32, Rahul Sharma wrote:
Allowing only one layer update per vsync can cause issues
while there are update available for both layers. There is
a good amount of possibility to loose updates if we allow
single update per vsync.
2014-06-24 20:38 GMT+09:00 Andreas Färber afaer...@suse.de:
Am 24.06.2014 07:21, schrieb Inki Dae:
On 2014년 06월 23일 14:32, Rahul Sharma wrote:
Allowing only one layer update per vsync can cause issues
while there are update available for both layers. There is
a good amount of possibility to
On 2014년 06월 23일 14:32, Rahul Sharma wrote:
Allowing only one layer update per vsync can cause issues
while there are update available for both layers. There is
a good amount of possibility to loose updates if we allow
single update per vsync.
Signed-off-by: Rahul Sharma
Allowing only one layer update per vsync can cause issues
while there are update available for both layers. There is
a good amount of possibility to loose updates if we allow
single update per vsync.
Signed-off-by: Rahul Sharma rahul.sha...@samsung.com
---
drivers/gpu/drm/exynos/exynos_mixer.c |
