[PATCH 19/38] drm/hisilicon: Implement some semblance of vblank event handling

2016-06-22 Thread Xinliang Liu
On 21 June 2016 at 15:19, Daniel Vetter wrote: > On Tue, Jun 21, 2016 at 3:32 AM, Xinliang Liu > wrote: >> My understanding is that drm_crtc_arm_vblank_event work together with >> drm_crtc_handle_vblank (called in vblank interrupt). >> Arm the event first in somewhere(like atomic_begin/flush) an

[PATCH 19/38] drm/hisilicon: Implement some semblance of vblank event handling

2016-06-21 Thread Xinliang Liu
On 17 June 2016 at 20:24, Daniel Vetter wrote: > On Fri, Jun 17, 2016 at 04:38:06PM +0800, Xinliang Liu wrote: >> Hi, >> >> On 17 June 2016 at 15:23, Daniel Vetter wrote: >> > On Fri, Jun 17, 2016 at 10:09:50AM +0800, Xinliang Liu wrote: >> >> Hi Daniel, >> >> >> >> I have tested your David's drm

[PATCH 19/38] drm/hisilicon: Implement some semblance of vblank event handling

2016-06-21 Thread Daniel Vetter
On Tue, Jun 21, 2016 at 3:32 AM, Xinliang Liu wrote: > My understanding is that drm_crtc_arm_vblank_event work together with > drm_crtc_handle_vblank (called in vblank interrupt). > Arm the event first in somewhere(like atomic_begin/flush) and then > send it out throuth drm_crtc_handle_vblank in

[PATCH 19/38] drm/hisilicon: Implement some semblance of vblank event handling

2016-06-17 Thread Xinliang Liu
Hi, On 17 June 2016 at 15:23, Daniel Vetter wrote: > On Fri, Jun 17, 2016 at 10:09:50AM +0800, Xinliang Liu wrote: >> Hi Daniel, >> >> I have tested your David's drm-next branch[1] which including this patch. >> In most time it is ok. But when switching modes or disable/re-enable >> mode, it will

[PATCH 19/38] drm/hisilicon: Implement some semblance of vblank event handling

2016-06-17 Thread Daniel Vetter
On Fri, Jun 17, 2016 at 04:38:06PM +0800, Xinliang Liu wrote: > Hi, > > On 17 June 2016 at 15:23, Daniel Vetter wrote: > > On Fri, Jun 17, 2016 at 10:09:50AM +0800, Xinliang Liu wrote: > >> Hi Daniel, > >> > >> I have tested your David's drm-next branch[1] which including this patch. > >> In most

[PATCH 19/38] drm/hisilicon: Implement some semblance of vblank event handling

2016-06-17 Thread Xinliang Liu
Hi Daniel, I have tested your David's drm-next branch[1] which including this patch. In most time it is ok. But when switching modes or disable/re-enable mode, it will encounter bellow error msg: -- [ 357.940728] [drm:drm_atomic_helper_commit_cleanup_done] *ERROR* [CRTC:24:crtc-0] flip_done timed

[PATCH 19/38] drm/hisilicon: Implement some semblance of vblank event handling

2016-06-17 Thread Daniel Vetter
On Fri, Jun 17, 2016 at 10:09:50AM +0800, Xinliang Liu wrote: > Hi Daniel, > > I have tested your David's drm-next branch[1] which including this patch. > In most time it is ok. But when switching modes or disable/re-enable > mode, it will encounter bellow error msg: > -- > [ 357.940728] [drm:drm

[PATCH 19/38] drm/hisilicon: Implement some semblance of vblank event handling

2016-06-02 Thread Daniel Vetter
atomic_flush seems to be the right place, but I'm not entirely sure whether this will catch them all. It could be that when disabling the crtc we'll miss the vblank. While at it nuke the dummy functions. v2: Be more robust and either arm, when the CRTC is on, or just send the event out right away